wiki: sync 2026-08-12 04:41 UTC — 4 file(s) updated

This commit is contained in:
2026-08-12 04:41:56 +00:00
parent 4ebe08daae
commit 69fcf12b56
4 changed files with 60 additions and 3 deletions
+4 -2
View File
@@ -1,6 +1,6 @@
# vssa-storm
_Last sync: 2026-08-12 00:37 UTC_
_Last sync: 2026-08-12 04:40 UTC_
## Purpose
@@ -12,7 +12,7 @@ VSSA client investigation and evidence gathering.
- Repository: <https://gitea.lego-cloud.eu/vssa-v1/documentation>
- Repository worktree: `/opt/data/vssa-documentation`
- Published Docusaurus site: <https://pages.apps.lego-cloud.eu/vssa-v1/documentation/>
- Client Dossiers use one flat 290-item sidebar. Systems Dossiers are generated from canonical client system-table rows; the latest validated registry contains 419 unique systems from 620 observations, with conservative alias rules in `data/system-aliases.json` and machine-readable output at `/data/systems-registry.json`.
- Client Dossiers use one flat 290-item sidebar. Systems Dossiers are generated from canonical client system-table rows; the latest validated registry contains 419 unique systems from 610 observations, with conservative alias rules in `data/system-aliases.json` and machine-readable output at `/data/systems-registry.json`.
- Gitea Actions workflow: `.gitea/workflows/pages.yml`; successful `main` builds publish through the mounted LEGO Cloud Pages root.
- Source registry: `source/message.txt`, containing 290 numbered clients.
- Required output: one concise Markdown dossier per client with exact name, one-sentence purpose, systems/clouds, plain-language system meaning, precise client relationship, identified contractor/company and role, direct evidence, confidence, and short gaps.
@@ -28,6 +28,7 @@ VSSA client investigation and evidence gathering.
## Availability continuity
- On 2026-08-12, commit `1542674` reorganized the portal around researched user tasks after reviewing GOV.UK content-design/writing guidance, W3C WAI design guidance, and USWDS card/table guidance. Global navigation is now Overview, Clients, Systems, Methodology, and Data; the homepage prioritizes client browsing, system exploration, and evidence search; scope metrics distinguish clients, systems, and observations; generated overview/directory/system-registry guidance explains ordering, statuses, counts, and safe interpretation; provenance documents the machine-readable registry. The rationale is recorded in `docs/content-organization-research.md`. Validation/build passed, desktop visual and browser checks found no clipping/JS errors, Gitea Actions run `2335` succeeded, and the Pages backend returned HTTP 200 for all representative routes and search. Public access remains Keycloak-protected (`302`).
- The first scheduled continuous-research invocation at 22:00 UTC failed because the model provider reported overload. The next invocation completed at 00:12 UTC, validated all 290 clients plus 419 system routes/620 observations, pushed commit `b34670484501f0ddd27154c19b7605bf00f3efdd`, and verified successful Gitea Actions run `2333`. Public Pages correctly redirected unauthenticated traffic to Keycloak (`302`), while direct backend checks returned HTTP 200 for representative client/system routes and the registry.
- On 2026-08-11, the visible navbar/site label was changed from `VSSA Documentation` to `VSSA - Clients & Systems` in commit `d062598`. Gitea Actions run `2332` succeeded and the Pages backend returned HTTP 200 with the new label.
- On 2026-08-11, commit `e0efc31` flattened the Client Dossiers sidebar and added Systems Dossiers: 621 canonical evidence observations consolidated into 421 conservative unique-system records, 421 generated system routes, client/system provenance links, reviewed alias rules, machine-readable JSON, search indexing, and build validation. Gitea Actions run `2331` succeeded. The Pages backend returned HTTP 200 for the homepage, client 001, systems registry, representative centralized-government-IT dossier, registry JSON, and search index. Public Pages became Keycloak-protected concurrently and now correctly returns HTTP 302 to `/oauth2/start` for unauthenticated requests; this is infrastructure authentication, not a deployment failure.
@@ -43,6 +44,7 @@ VSSA client investigation and evidence gathering.
## Source anchor
- Latest processed human message: `1536934392302141461` (2026-08-12). Lego requested an immediate research-led overall page improvement cycle focused on best practices for content organization; the deployed result is recorded above.
- Latest processed human message: `1536859431533281312` (2026-08-11). Lego requested the site label `VSSA - Clients & Systems`; it was published and verified as recorded above.
- Latest processed human message: `1536847412382015629` (2026-08-11). Lego requested a flat Client Dossiers sidebar, a unique Systems Dossiers registry, and continuous documentation/research automation; all three were implemented and published as recorded above.
- Latest processed human message: `1536845732613591160` (2026-08-11). Lego reported that the new landing page and search were not visible; inspection confirmed the changes had only existed locally. Hermes committed and pushed them, verified successful Actions run `2330`, and confirmed the public deployment and search behavior.