docs: describe ENGAGE to DEMI to Eagle comment period flow
Replace 'nothing writes back into Eagle' with the rule that only DEMI's
sync-out writes into Eagle, through eagle-api. Add the EPIC_SYNC_TARGET
switch and the backfill job to the ENGAGE integration page.
docs: describe the read-only public site on DEMI
The Angular public site reads from DEMI only and takes no comments. Remove the rproxy and pod steps that no longer apply, and point the local proxy and config examples at /demi-search/config.
docs: rewrite wiki to current state
Drop history, diaries, future plans and unverified claims. Delete
Search-Cutover (diary) and API-Deployment (DeploymentConfig era).
Every page verified against repos and live clusters, under 15 KB.
Claude-Session: https://claude.ai/code/session_012J1PYLGauUNovjJ1MMoKy5
docs: add the Azure migration strategy, retire dead pages, fix stale search references
Adds Azure-Migration-Strategy, which sequences eagle-public and eagle-admin
ahead of any API work and records the fact that decides that order: rg-demi-prod
holds a search service and nothing else, while the 20 resources DEMI needs to be
an API exist only in c4b0a8-test. The corollary is that eagle-api should not be
ported to Azure at all, since DEMI is meant to replace it.
Deletes two pages documenting systems that do not exist. Typesense-Search
described operating an estate deleted on 2026-08-21. GitOps-ArgoCD-Deployment
described a deployment model that was never adopted: the argocd/ directory it
points at is absent from eagle-helper-pods, no workflow references it, and there
are no Application resources in the namespace.
Fixes the references those pages left behind, and others that survived the
cutover asserting Typesense was still live — a proxy controller, an Angular
service and an nginx location that have all been deleted, plus two Mermaid
diagrams. The one that would have caused real harm is in Project-Data-Models: it
instructed a lng/lat swap on sync, which was a Typesense requirement. Azure AI
Search takes GeoJSON order unchanged, so following it would corrupt every
centroid.
All wiki links resolve.
docs: revert GHCR references in deployment documentation to reflect direct OpenShift registry usage
docs: add ENGAGE-EAGLE integration page; update architecture overview
Moves ENGAGE→EAGLE push sync content from Architecture-Overview into its
own dedicated page (ENGAGE-EAGLE-Integration.md). Covers push flow, sync
triggers, payload fields, visibility gate, auth, and Typesense side-effect.
Architecture-Overview.md updated: stale live-ENGAGE-API references removed,
/engage-api rproxy route removed, isMet CP read-only note added to eagle-admin.