wiki: sync 2026-09-17 03:16 UTC — 4 file(s) updated

This commit is contained in:
2026-09-17 03:16:13 +00:00
parent 9334eb99d5
commit a954b28345
4 changed files with 23 additions and 4 deletions
+2 -2
View File
@@ -1,6 +1,6 @@
# Channel Wiki: #jarvis-jr-knowledge-wiki
_Channel ID: 1519069810166599764_
_Last sync: 2026-09-16 03:11 UTC_
_Last sync: 2026-09-17 03:13 UTC_
## Purpose
Operate and audit Hermes's persistent Discord knowledge system: channel inventory, monitored-channel coverage, per-channel context, recurring syncs, and Gitea mirroring.
@@ -24,7 +24,7 @@ Operate and audit Hermes's persistent Discord knowledge system: channel inventor
- Verify config refresh and Gitea push independently after monitoring changes.
- The authoritative sync mapping now contains 33 text-channel IDs, including the recently provisioned `#cogarch-v1-iac`, `#cogarch-v1-shorts`, `#cogarch-v1-argo-workflows`, `#jarvis-jr-v1-storm`, and `#lego-v1-cv` channels; one retained legacy ID (`#jarvis-jr-test-001`) remains inaccessible with Discord error `10003 Unknown Channel`.
- ✅ On 2026-09-13 the recurring health-check defect was repaired: zero-match `grep -c` output can no longer become the invalid multiline value `0\n0`, and the Discord check now recognizes the gateway's actual inbound/send activity log forms. A syntax check and complete rerun passed all four checks; the same run's authenticated Discord REST scan succeeded for 31/32 monitored channels.
- ⚠️ Run #155 on 2026-09-16 scanned 32/33 monitored IDs; `#jarvis-jr-test-001` remains inaccessible with Discord `10003 Unknown Channel`. Six human messages in `#cogarch-v1-argo-workflows` advanced its anchor through `1549399634302992447` and established that the failed run's fail-open Redis warning did not recur in the read-only-verified rerun pod; the overwritten detailed agent log reportedly contained operation timeout/retry-limit errors.
- ⚠️ Run #156 on 2026-09-17 scanned 32/33 monitored IDs; `#jarvis-jr-test-001` remains inaccessible with Discord `10003 Unknown Channel`. Nine human messages in `#cogarch-v1-argo-workflows` advanced its anchor through `1549783805877813279` and established the BYOT MVP decision: one persistent OpenShift Secret per user, managed by the existing backend with write-only Secret RBAC plus admission restriction, rather than IBM Secrets Manager or a new internal service.
## Channel Workspace
- Channel-owned working files belong under `/opt/data/channels/jarvis-jr-knowledge-wiki/`, grouped by purpose.