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: retire eagle-admin OpenShift hosting
Dev and test objects are removed; prod keeps a scaled-down Deployment for rollback. Drop dev-only admin troubleshooting and chart notes.
docs: eagle-admin on prod served from Azure storage
docs: eagle-admin on test served from Azure storage
Test serves /admin/ from storage behind Front Door; dev and prod stay
on OpenShift. Adds the admin origin switch, rule set, rollback and the
Azure deploy workflows.
docs: search served by DEMI in prod; eagle-search retired
Six pages corrected in place; diagrams and upstream tables now show the
sentinel for /eagle-search/.
docs: eagle-edge deploys from CI
Claude-Session: https://claude.ai/code/session_01Lv5nbmWMatCc8PzYmpupNb
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: eagle-admin stays on OpenShift — correct the migration scope
An earlier draft of this page listed eagle-admin as step 2 of the Azure
migration. It is not in scope at all: nothing in it is being ported and no Azure
estate is being built for it. The error came from reading "eventually the entire
eagle" as covering every frontend, which it does not.
Adds an explicit scope section — what "entire eagle in Azure" means and what it
does not — so the next reader does not re-derive the same wrong conclusion from
the same phrase. eagle-public moves; DEMI eventually becomes the API; eagle-admin
and eagle-api stay on OpenShift, the latter until DEMI replaces it.
Also drops the plural "static frontends", which implied both, and renumbers the
order plus the one step reference that pointed at it.
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.