wiki: sync 2026-08-12 00:38 UTC — 6 file(s) updated

channels/1532415849762127902.md

@@ -1,6 +1,6 @@
 # vssa-storm
 
-_Last sync: 2026-08-11 20:33 UTC_
+_Last sync: 2026-08-12 00:37 UTC_
 
 ## Purpose
 
@@ -9,20 +9,30 @@ VSSA client investigation and evidence gathering.
 ## Current assets
 
 - Gitea organization: `vssa-v1`
-- Repository: <https://gitea.lego-cloud.eu/vssa-v1/vssa-clients>
-- Repository worktree: `/opt/data/vssa-clients`
+- 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`.
+- 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.
 - Investigation skill: `client-investigator`; recurring runs must deepen contractor research and patch the skill only with validated reusable practices.
 
 ## Automation
 
-- Cron job `88833e00b4a2` (`VSSA client cloud/system investigation`) runs at `0 */2 * * *` and reports to this channel.
-- Each run audits all 290 records, deeply researches up to 10 missing/weak/stale dossiers, updates the index, commits and pushes evidence-backed changes, and verifies remote state.
+- Cron job `88833e00b4a2` (`VSSA documentation continuous research`) runs at `0 */2 * * *` and reports to this channel.
+- Each run audits all 290 records, deeply researches up to 10 missing/weak/stale dossiers, continuously improves client/system/contractor evidence and documentation, reviews conservative system identity rules, validates the complete Docusaurus build, pushes evidence-backed changes, verifies Actions, and checks the deployed Pages backend.
 - Research must prefer primary sources and must not infer providers/systems without corroborating evidence.
+- The job workdir and remote now target `/opt/data/vssa-documentation` and `vssa-v1/documentation`; it must not edit generated Docusaurus output.
+- **Latest rotation (2026-08-12 00:12 UTC):** clients 089–098 were refreshed. Coverage is 79 researched, 189 partial, 22 no-public-evidence, and 0 pending. The next planned rotation is clients 099–108. Client 090's official site has an incomplete TLS chain; contract dates, payment providers, hosting, integrations, and current support ownership remain unknown for several services.
 
 ## Availability continuity
 
+- 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.
+- On 2026-08-11, the dedicated VSSA-styled Docusaurus landing page and native local search were published in commit `d43effe`. The design uses the official VSSA navy/blue visual language, locally bundled Public Sans, the official mark, square geometry, a separate `/overview/` documentation route, and live registry-derived metrics. Gitea Actions run `2330` completed successfully. The public homepage, overview, directory, local 3 MB search index, and logo returned HTTP 200; a browser query for `kanceliarija` returned multiple dossier results and opened client 001 successfully. Search is generated and executed inside the static site with no external search service.
+- On 2026-08-11, `vssa-v1/vssa-clients` was renamed to `vssa-v1/documentation` with history preserved. The main worktree and 20 linked-worktree pointers were repaired and verified. Docusaurus 3.10.2 now renders all 290 dossiers from generated MDX-safe copies, preserves canonical source artifacts, and publishes byte-identical raw artifacts with SHA-256 hashes. Gitea Actions run `2329` completed successfully for commit `0a2144f`, and the public LEGO Cloud Pages homepage, directory, representative dossier routes, and raw manifest returned HTTP 200.
 - On 2026-08-11, Gitea 1.27.0 initially left web/API healthy while all Git transport operations crashed in the Go runtime during `moduledataverify1`. Gitea was subsequently updated to `1.27.1`; SSH and Smart HTTP recovered. The queued VSSA commit `6fc42ab` was pushed and remotely verified, leaving local `main` synchronized with `origin/main`.
 - **CONFIRMED recovery decision/status (2026-08-11 19:05–19:06 UTC):** after Lego asked Hermes to recheck, live verification showed Gitea `1.27.1`, REST API, SSH Git, and HTTPS Git all healthy. The queued VSSA client-dossier commit `6fc42ab` was pushed, remote `INDEX.md` was read back, and local `main` matched `origin/main`. No VSSA delivery blocker remained from this incident.
 - On 2026-08-04 at 20:05–20:42 UTC, Lego (`root_at_skic`) repeatedly asked whether Hermes was alive. These messages are evidence of the broader Hermes availability incident, not a change to the VSSA investigation scope. The incident was subsequently investigated in `#jarvis-jr-v1-hermes-setup`.
@@ -33,7 +43,11 @@ VSSA client investigation and evidence gathering.
 
 ## Source anchor
 
-- Latest processed human message: `1536812738679021618` (2026-08-11 19:05 UTC). Lego asked Hermes to check Gitea after remediation; the subsequent verified 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.
+- Latest processed human message: `1536835494909055107` (2026-08-11). Lego directed Hermes to rename the repository to `documentation`, convert it to Docusaurus, add Gitea Actions, and publish through LEGO Cloud Pages; the completed state is recorded above.
+- Previous processed human message: `1536812738679021618` (2026-08-11 19:05 UTC). Lego asked Hermes to check Gitea after remediation; the subsequent verified result is recorded above.
 - Previous incident message: `1536807021674762261` (2026-08-11 18:42 UTC), asking what was wrong with Gitea and how to resolve it.
 - Previous availability message: `1534300468530905170` (2026-08-04 20:42 UTC). Lego asked whether Hermes was alive; no VSSA project scope or status changed.
 - Previous terminology message: `1533032343021813930` (2026-08-01 08:43 UTC), requesting clarification of “mutation”.