Matt Johnson f0da1554f0 Add deployment profiles to navi-backend (extraction #2 — decouple from /opt/recon) ... Vendors the three deployment profile YAMLs (home, minimal_pi, regional_pi) into navi-backend's own repo at config/profiles/. Copied verbatim from /opt/recon/config/profiles/ post-PR-A, so home.yaml carries the auth block and the two Pi profiles carry the TODO(matt) logout-host note. Architectural reason: services in this monorepo should depend on each other only through their HTTP APIs, never each other's filesystem. navi-config currently defaults to reading /opt/recon/config/profiles/ — a cross-service filesystem coupling. With the profiles vendored here, navi-config will be pointed at this repo's copy via NAVI_CONFIG_PROFILES_DIR in /etc/navi-backend/navi-config.env at deploy time, so it no longer reaches into recon's tree. recon keeps its own /opt/recon/config/profiles/ for its internal use; the two copies are independent for now. Reconciling them — ideally by having recon HTTP-fetch /api/config from navi-config rather than re-parsing YAML — is a tracked follow-up, out of scope for extraction #2. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>		2026-05-22 09:23:12 -06:00
..
home.yaml	Add deployment profiles to navi-backend (extraction #2 — decouple from /opt/recon)	2026-05-22 09:23:12 -06:00
minimal_pi.yaml	Add deployment profiles to navi-backend (extraction #2 — decouple from /opt/recon)	2026-05-22 09:23:12 -06:00
regional_pi.yaml	Add deployment profiles to navi-backend (extraction #2 — decouple from /opt/recon)	2026-05-22 09:23:12 -06:00