wiki: sync 2026-08-11 20:34 UTC — 5 file(s) updated

This commit is contained in:
2026-08-11 20:34:53 +00:00
parent 26c221085d
commit 6c8ffdf1b0
5 changed files with 68 additions and 11 deletions
+21 -7
View File
@@ -1,22 +1,36 @@
# Channel Wiki: #skic-v1-playground
_Channel ID: 1527398768608284703_
_Created: 2026-07-23 18:22 UTC_
_Last sync: 2026-07-23 18:22 UTC_
_Last sync: 2026-08-11 20:33 UTC_
## Purpose
<!-- What this channel is about -->
SKIC playground projects and their Gitea-hosted build/publishing workflows.
## Key Decisions
<!-- Important decisions made in this channel -->
- **CONFIRMED (2026-08-11):** the Gitea Actions runner—not Hermes locally—must install dependencies and build the `skic-v1-playground/documentation` Docusaurus site after repository changes are pushed.
- **CONFIRMED publication contract:** generated files for a repository are published under `/gondor-v1-gitea-pages/<organization>/<repository>/`; the corresponding public URL is `https://pages.apps.lego-cloud.eu/<organization>/<repository>/`.
- **CONFIRMED runner mount:** the Pages dataset source `/mnt/lego-cloud-v1-2025-11-28/gondor-v1-gitea-pages` is mounted into job containers at `/gondor-v1-gitea-pages`. The source must also be allowed by the runner's `container.valid_volumes`; only the mount destination changed during troubleshooting.
## Active Topics
<!-- Currently active discussions/threads -->
- **Documentation Pages deployment — COMPLETE/VERIFIED:** repository <https://gitea.lego-cloud.eu/skic-v1-playground/documentation> now builds and publishes through Gitea Actions.
- Docusaurus is configured for URL `https://pages.apps.lego-cloud.eu` and base path `/skic-v1-playground/documentation/`.
- Final successful run: <https://gitea.lego-cloud.eu/skic-v1-playground/documentation/actions/runs/2326> at commit `acbc8f75a6eb9c3d28427a7d248111415c9ceda6`.
- Live site: <https://pages.apps.lego-cloud.eu/skic-v1-playground/documentation/> — HTTP 200 for the page and a static asset; browser rendering of “SKIC Playground” was verified.
## Key Context
<!-- Important context that persists across conversations -->
- Initial runner failures established three reusable constraints: `pnpm-workspace.yaml` must contain a valid `packages` field; job images cannot be assumed to contain `rsync`; and a path visible only inside an ephemeral job container is not a publication target.
- The workflow now validates the repository path and persistent Pages mount so missing infrastructure fails explicitly instead of reporting false publication success.
- The working publish destination for this repository is `/gondor-v1-gitea-pages/skic-v1-playground/documentation/`.
## People & Roles
<!-- Key people who participate and their roles -->
- Lego (`root_at_skic`) — specified the Pages path/URL contract, corrected ownership of build execution to the Gitea runner, and applied the runner mount destination change.
- Hermes — updated and pushed the Docusaurus/workflow configuration, triggered actual Gitea Actions runs, diagnosed runner failures, and verified final publication.
## Action Items
<!-- Open action items from this channel -->
- No open deployment action from this exchange. Revalidate Gitea Actions and the public URL after future runner mount or Pages infrastructure changes.
## Source anchor
- Latest processed human message: `1536834135262503083` (2026-08-11 20:30 UTC), requesting an immediate rebuild and publish; run 2326 subsequently completed successfully.
- Initial directive: `1536821956744188027` (2026-08-11 19:41 UTC).
- Runner-execution correction: `1536822550615691284` (2026-08-11 19:44 UTC).
- Mount-destination instruction: `1536832761896378448` (2026-08-11 20:24 UTC).
+6 -2
View File
@@ -1,6 +1,6 @@
# vssa-storm
_Last sync: 2026-08-11 04:15 UTC_
_Last sync: 2026-08-11 20:33 UTC_
## Purpose
@@ -23,6 +23,8 @@ VSSA client investigation and evidence gathering.
## Availability continuity
- 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`.
## Terminology
@@ -31,6 +33,8 @@ VSSA client investigation and evidence gathering.
## Source anchor
- Latest processed human message: `1534300468530905170` (2026-08-04 20:42 UTC). Lego asked whether Hermes was alive; no VSSA project scope or status changed.
- 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.
- 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”.
- Previous durable directive: `1532810727847624884` (2026-07-31 18:02 UTC), confirming the concise one-file-per-client format, plain-language system meaning, contractor/company research, deep public investigation, and iterative improvement of `client-investigator`.