azcomputerguru/claudetools
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

sync: auto-sync from GURU-5070 at 2026-06-18 12:49:38

Browse Source 
Author: Mike Swanson
Machine: GURU-5070
Timestamp: 2026-06-18 12:49:38
This commit is contained in:
Mike Swanson
2026-06-18 12:49:57 -07:00
parent 9d2d233f1e
commit 6f4cadb16f
4 changed files with 143 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
.claude/memory/MEMORY.md
View File

@@ -34,6 +34,7 @@
- [reference_sqlx_migrations_immutable](reference_sqlx_migrations_immutable.md) -- NEVER edit an already-applied sqlx migration file — even a comment. sqlx::migrate! checksums each file at compile time and validates against _sqlx_migrations at startup; a changed checksum crash-loops the server with "migration N was previously applied but has been modified". Code review MUST flag any edit to an applied migration.
- [AD2 SSH MTU blackhole](ad2-ssh-mtu-blackhole.md) — AD2 SSH "lockouts"/mid-session read-errors over the Dataforth OpenVPN were a PMTU blackhole (tunnel PMTU ~1424 vs adapter MTU 1500), NOT a ban/account-lockout/flaky tunnel. Fix: pin the OpenVPN adapter MTU to 1400 (done on GURU-5070 via its SYSTEM RMM agent); permanent = `mssfix 1360` on the OpenVPN server. Diagnose over RMM, not SSH.
- [DSCA33/45 resolved via Hoffman](project_dsca33_45_resolved_via_hoffman.md) — The "lost" DSCA33/45 spec files are recoverable from the Hoffman API (original certs survived the wipe); do NOT ask John. 56/58 models mined into projects/dataforth-dos/dsca33-45-templates.json; only DSCA33-1948 + DSCA45-1746 (24 units) lack an original. AD2 handoff: DSCA33-45-HOFFMAN-RECOVERY-2026-06-18.md.
- [AD2 comms via sync only](ad2-comms-via-sync-only.md) — The AD2 Dataforth-box Claude session is coord-API-isolated (Gitea only); coord msg/lock/todo never reach it. Coordinate with AD2 ONLY via git /sync (committed docs + ## Note blocks).
## Users
- [Howard Enos](user_howard.md) — Mike's brother, technician, full access. Machines: ACG-TECH03L, Howard-Home (authoritative in users.json).

21
.claude/memory/ad2-comms-via-sync-only.md Normal file
View File

@@ -0,0 +1,21 @@
---
name: ad2-comms-via-sync-only
description: The AD2 (Dataforth) Claude session is coord-API-isolated — reach it ONLY via git /sync (committed notes/docs), never coord messages/locks
metadata:
type: feedback
---
The AD2 Dataforth-box Claude session is **network-isolated from the ACG coord API** (172.16.3.30 —
the Dataforth network can't reach it); it only has Gitea/git access. So coord-API **messages, locks,
and todos NEVER reach AD2**. ALL inter-session coordination with AD2 must go through git **`/sync`**:
committed handoff docs and `## Note for <user>` blocks in synced session logs, which AD2 reads when
it pulls. A coord lock on an AD2-only file (e.g. `datasheet-exact.js`) is also meaningless — only the
AD2 session edits that box.
**Why:** burned a round of `coord msg send AD2` + lock that were silent no-ops (Mike: "You can't
coord with AD2 — all comms needs to be via sync").
**How to apply:** to hand work to or coordinate with the AD2 session, write it into a committed doc
(e.g. `projects/dataforth-dos/*HANDOFF*.md`) and/or a `## Note for <user>` block in a session log,
then `/sync`. Do NOT use the coord skill for AD2. (Coord API is still fine for non-isolated ACG
machines.) [[prefer-ssh-over-rmm]]