esh-pfi-infrastructure/persistent-memory.d/2026-07-14-soong-lab-webhook-auto-deploy-real-root-cause.md at cac381a114442be3d6611c1b6bac3c78f78b2bd4

Files

T

vh d710e56aca memory: migrate persistent-memory.md to two-tier index (53 detail files)

Split the 53 over-threshold dated log entries (Recent decisions, Tried
and abandoned) into per-entry persistent-memory.d/<slug>.md detail files,
leaving one-line pointers in the index; the 10 short entries stay inline.
Startup index drops 60,527 -> 25,256 bytes (492 -> 270 lines); entry
bodies move verbatim to on-demand detail files, so a fresh session loads
~25 KB instead of ~60 KB and pulls a detail file only when its pointer is
relevant. Top matter (Repo purpose, Tools & conventions, Current state)
is unchanged; both archival back-references preserved.

CLAUDE.md persistent-memory section now documents the index<->detail read
discipline (read the index, pull details on demand, never bulk-read the
dir, commit both together).

Auto-archival still held every dated entry back (all <30 days old); the
July burst begins aging past the 30-day guard ~2026-07-31.

2026-07-15 13:33:42 -07:00

443 B

Raw Blame History

[2026-07-14] soong-lab webhook auto-deploy real root cause = gitea webhook.ALLOWED_HOST_LIST (was external, 10.100.0.0/16 = NH3-only; blocked corviduo-dev's Anaheim 10.250.x → gitea refused to deliver, never opened the connection). Fixed to fleet-wide 10.0.0.0/8 (app.ini [webhook]) + gitea restart; listener now logs every delivery. The ufw 10/8 open (also this session) was a real-but-secondary gap. Committed 462d528.

443 B Raw Blame History

443 B

Raw Blame History