wiki: sync 2026-09-12 03:18 UTC — 8 file(s) updated

This commit is contained in:
2026-09-12 03:18:03 +00:00
parent a7292a9681
commit d1d54ea679
8 changed files with 132 additions and 11 deletions
+4 -4
View File
@@ -1,6 +1,6 @@
# Channel Wiki: #jarvis-jr-knowledge-wiki
_Channel ID: 1519069810166599764_
_Last sync: 2026-09-11 03:09 UTC_
_Last sync: 2026-09-12 03:15 UTC_
## Purpose
Operate and audit Hermes's persistent Discord knowledge system: channel inventory, monitored-channel coverage, per-channel context, recurring syncs, and Gitea mirroring.
@@ -22,8 +22,8 @@ Operate and audit Hermes's persistent Discord knowledge system: channel inventor
- Keep the channel inventory synchronized when channels are created, renamed, moved, or deleted.
- Ensure every new channel gets a real-history wiki seed where history exists.
- Verify config refresh and Gitea push independently after monitoring changes.
- The authoritative sync mapping now contains 28 text channels, including the newly provisioned `#emplonet-v1-general` and `#emplonet-v1-ingrida` channels; one retained legacy ID (`#jarvis-jr-test-001`) remains inaccessible with Discord error `10003 Unknown Channel`.
- ⚠️ The pre-run health check failed again on 2026-09-11 (after the same failure on 2026-09-10): its Discord count became the invalid multiline value `0\n0`, and its gateway-log heuristic reported no Discord connection. The subsequent authenticated Discord REST scan succeeded for 27/28 monitored channels with zero new human messages, so this remains a health-check/log-signal defect rather than proof that Discord API access is down.
- The authoritative sync mapping now contains 32 text-channel IDs, including the recently provisioned `#cogarch-v1-iac`, `#cogarch-v1-shorts`, `#cogarch-v1-argo-workflows`, and `#jarvis-jr-v1-storm` channels; one retained legacy ID (`#jarvis-jr-test-001`) remains inaccessible with Discord error `10003 Unknown Channel`.
- ⚠️ The pre-run health check failed for a third consecutive daily run on 2026-09-12: its Discord count again became the invalid multiline value `0\n0`, and its gateway-log heuristic reported no Discord connection. The subsequent authenticated Discord REST scan succeeded for 31/32 monitored channels, so this remains a health-check/log-signal defect rather than proof that Discord API access is down.
## Channel Workspace
- Channel-owned working files belong under `/opt/data/channels/jarvis-jr-knowledge-wiki/`, grouped by purpose.
@@ -35,4 +35,4 @@ Operate and audit Hermes's persistent Discord knowledge system: channel inventor
- Repair `/opt/data/scripts/health-check.sh` so a zero-match `grep -c` result remains one integer and reassess its gateway-log connection heuristic; the current check can fail even while authenticated Discord REST reads succeed.
## Source anchor
- Latest processed human message: `1546637410702729246` (2026-09-07 21:44 UTC; requested a dedicated channel folder and placement of the July 16 wiki bootstrap exports/parser there; the resulting workspace and archive locations are recorded above).
- Latest processed human message: `1547935398355927141` (2026-09-11 11:42 UTC; asked whether this channel has a local directory; the existing canonical workspace is recorded above).