wiki: sync 2026-08-27 03:04 UTC — 7 file(s) updated

channels/1519072621130547220.md

@@ -1,11 +1,19 @@
 # Channel Wiki: #jarvis-jr-truenas
 _Channel ID: 1519072621130547220_
-_Last sync: 2026-08-26 03:03 UTC_
+_Last sync: 2026-08-27 03:03 UTC_
 
 ## Purpose
 TrueNAS, self-hosted infrastructure, registry, proxy, and platform setup discussions.
 
 ## Key Context
+- Dedicated channel skill: `home-v1--truenas`.
+- Authoritative private Gitea repository: https://gitea.lego-cloud.eu/home-v1-skills-code-agent/home-v1--truenas (`test` default branch).
+- Hermes loads the skill directly from `/opt/data/home-v1-skills-code-agent/home-v1--truenas` through `skills.external_dirs`, so repository updates and runtime behavior share one source tree.
+- TrueNAS WebSocket access expects runtime variables `HL_V1_TRUENAS_URL` and `HL_V1_TRUENAS_API_KEY`; values must remain in memory and must never be printed or committed.
+- The skill owns reusable `scripts/truenas_rpc.py` JSON-RPC logic and `scripts/truenas_health.py` read-only health summaries, with offline tests and Gitea Actions validation.
+- **CONFIRMED delivery (2026-08-26):** initial skill commit `634e0e63290cb4a8c44b961c89d0583cc2e7612f` is on the private repository's `test` branch; authenticated remote-SHA/artifact readback passed, all 10 offline tests passed, and Gitea Actions task `1398` passed. A fresh Hermes loader reported the skill available and discovered both scripts.
+- **CONFIRMED access check (2026-08-26):** both expected keys exist in Bitwarden Secrets Manager and a short-lived authenticated WebSocket health query succeeded without changing TrueNAS. Strict TLS verification failed because the configured URL uses an IP address whose identity does not match the certificate; diagnostic-only `--insecure` access succeeded. The durable fix is a certificate-matching DNS URL or correct CA/hostname path—not permanent TLS disablement.
+- **Live read-only observation, not yet investigated:** TrueNAS reported `26.0.0-BETA.2`; pool `lego-cloud-v1-2025-11-28` was `ONLINE` and `healthy: true` but also reported `status_code: CORRUPT_DATA`, with 3 active alerts. The setup request did not authorize investigation or remediation, and no action was taken.
 - Keycloak hostname: `keycloak.lego-cloud.eu`; historical discussion referenced the `master` realm.
 - Gitea organization URL: https://gitea.lego-cloud.eu/home-v1
 - Repository referenced for shared access: https://gitea.lego-cloud.eu/home-v1/arda-v1-code-agent
@@ -16,6 +24,7 @@ TrueNAS, self-hosted infrastructure, registry, proxy, and platform setup discuss
 ## Behavioral Decisions
 - Teach and train without negativity or pointing out what others lack.
 - Operate autonomously enough that RootAtSkic does not need to micromanage routine investigation.
+- Keep `home-v1--truenas` continuously updated when durable TrueNAS methods, safeguards, API quirks, or reusable procedures are confirmed; maintain logic as tested scripts in its Gitea repository rather than accumulating one-off inline commands.
 
 ## Active Topics
 - TrueNAS application deployment patterns.
@@ -37,7 +46,7 @@ TrueNAS, self-hosted infrastructure, registry, proxy, and platform setup discuss
 - SMBIOS does not expose module manufacturing week/year. Determining production date requires readable SPD EEPROM data or inspection of the physical DIMM labels; neither was available from the container during this check.
 
 ### Source anchor
-- Latest processed human message: `1541875756626354266` (2026-08-25 18:23 UTC).
+- Latest processed human message: `1542256118284157158` (2026-08-26 19:35 UTC).
 
 ## TrueNAS Stability Incident — 2026-08-17
 - TrueNAS `26.0.0-BETA.2` on `nas.lego-cloud.eu` underwent full-host boots at 11:02:52, 12:16:18, 12:32:13, and 13:52:25 Europe/Vilnius time. Docker/containerd restarts were consequences, not the initial cause.