docs: Eagle read ladder and re-push page
Roles table drops staff from the privileged read set and adds the admin set. Visibility section lists the read ladder and the Eagle read cap. New how-to page covers demi-repush, the reverse ladder backfill and the parity check.
docs: note optional project lead and EPD
docs: add extended pages and Act registry
- Extended-Project-Pages: content model, blocks, tab rules,
validation, recipe for giving a project an extended page.
- Project-Data-Models: legislation registry, locked Acts, steps
for adding an Act.
- Configuration-Management: EXTENDED_PROJECT_PAGES key and how to
turn a page off.
docs: drop external model diagram links
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: eagle-search architecture, retire typesense pages
Document-Content-Search described a Typesense collection filled by a nightly
content-extract.js CronJob in eagle-typesense. That script was deleted when
extraction moved to eagle-demi and Typesense has been replaced outright, so
the page documented a pipeline that no longer exists.
New Eagle-Search page carries the architecture, the twice-denormalised ACL
cascade, content grouping, fuzzy matching and the eagle-public preview.
Typesense-Search keeps a superseded banner rather than being deleted — its
dev cronjobs are still running and eagle-api still carries the proxy code.
Also includes the Project-Data-Models page and the Keycloak / Local-Development
additions that were sitting uncommitted.