docs: rewrite analytics pages for eagle-analytics
Penguin retained only for Engage and GC Notify. Documents the
reverse proxy split.
docs: document the /demi-projects/ route
docs: DEMI push key is DEMI_APIM_KEY
Claude-Session: https://claude.ai/code/session_015FCYoxrqNfUraeMnHdwChf
docs: eagle-api push contract for eagle-notify
Claude-Session: https://claude.ai/code/session_01Eit2YBNjMNF1e4MuXBfbzY
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: 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: 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.
docs: fix eagle-demi repo org (digitalspace, not bcgov)
docs: rename Eagle-Docling to Eagle-DEMI
DEMI = Document Extraction & Machine Intelligence.
Rename decouples service identity from docling implementation detail.
All references updated: sidebar, architecture overview, helm charts page.
Upstream docling-serve software references preserved unchanged.
docs: add eagle-docling architecture and deployment docs
Add documentation for eagle-docling (docling-serve document intelligence):
- Architecture-Overview.md: add eagle-docling subgraph to mermaid diagram,
add component details section with ClusterIP/NetworkPolicy notes
- Eagle-Docling.md: new page — architecture, API, config, deployment,
troubleshooting guide
- Helm-Charts.md: add eagle-docling chart section covering key differences
from other Eagle charts, config values, startup probe, NetworkPolicy
- _Sidebar.md: add Eagle-Docling link under Architecture and repo link
docs: update typesense references for standalone eagle-typesense repo
- Architecture diagram: typesense-sync now lives in eagle-typesense
- Helm section: point to digitalspace/eagle-typesense
- Sidebar: add eagle-typesense to repository list
- Architecture overview: update eagle-api search description
docs: update Engage integration — commenting tab unified list
docs: document Engage banner integration
- Configuration-Management: add ENGAGE_API_URL variable + Helm values example
- Architecture-Overview: add EPIC Engage to diagram, routing table, eagle-public description
- Angular-Patterns: update constructor pattern to use takeUntilDestroyed;
add Input-Reactive Loading pattern (toObservable+switchMap)
docs: document server-side Typesense proxy architecture
- Typesense-Search: rewrite for eagle-api proxy pattern; remove
direct-browser key docs; add security model, role filtering,
endpoint reference, filter injection defence
- Architecture-Overview: update search flow (no browser key)
- Reverse-Proxy-Configuration: remove search-api routing section
- Local-Development: update typesense dev setup for proxy
- Angular-Patterns: remove scopedKey/getApiKey, document proxyBase
- Document-Content-Search: new page for document full-text search
- _Sidebar: add Document-Content-Search link
docs: add Typesense search architecture and update platform docs
docs: clean up architecture diagrams for better readability
docs: add Keycloak auth, rproxy details, penguin-analytics to architecture diagram
docs: fix technical inaccuracies from audit
- Fix penguin-analytics port: 3001 → 3000 (verified against Helm charts)
- Correct eagle-admin Node version: 24.x → 22.x (matches CI/CD)
- Update eagle-api package manager: npm → Yarn 4.12.0
- Add Node version specifications to Architecture-Overview.md
- Clarify test framework differences (Vitest/Karma/Mocha) per repo
- Add penguin-analytics to sidebar navigation
All changes verified against actual codebase configuration.
Fix database architecture diagrams
- Analytics now correctly connects to TimescaleDB/PostgreSQL (not MongoDB)
- Updated Home.md, Architecture-Overview.md diagrams
- Removed user emojis from Architecture-Overview.md
- All application components correctly documented
Add deployment pipeline wiki documentation
- Home page with system architecture diagram
- Architecture Overview with component details and request flow
- Deployment Pipeline documentation for CI/CD workflows
- Helm Charts reference guide
- Rollback Procedures for version redeploy and Helm rollback
- Troubleshooting guide for common issues
- Local Development setup guide
- Sidebar navigation
Documents the modernized CI/CD pipeline with:
- Trivy container scanning
- Version-based deployments
- GitHub releases integration
- Helm chart adoption