malice b5079fd192 fix: include navi-offroute (8428) in navi-admin fleet list ... navi-offroute (:8428, extraction #8) was missing from fleet.py's SERVICES list, so it never appeared in /api/admin/fleet. Add the one (name, port) row — the single source of truth that build_fleet, dependency_summaries, and the self-info fanned_services all derive from. 8427/navi-admin is the aggregator itself (self-poll), correctly not in its own fan-out. Co-authored-by: Matt Johnson <mj@k7zvx.com> Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>		2026-05-23 23:17:23 -06:00
..
tests	decouple: add /api/auth/whoami to navi-admin (preparing recon migration)	2026-05-23 13:23:55 -06:00
__init__.py	Add navi-admin service (extraction #7) (#7)	2026-05-22 21:21:00 -06:00
admin_route.py	decouple: drop navi-admin → recon /api/health coupling	2026-05-23 13:14:09 -06:00
app.py	decouple: add /api/auth/whoami to navi-admin (preparing recon migration)	2026-05-23 13:23:55 -06:00
auth_route.py	decouple: add /api/auth/whoami to navi-admin (preparing recon migration)	2026-05-23 13:23:55 -06:00
fleet.py	fix: include navi-offroute (8428) in navi-admin fleet list	2026-05-23 23:17:23 -06:00