vh
d710e56aca
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.
1.6 KiB
1.6 KiB
[2026-07-09]Two parked items closed: phantomqwen3.6-35b-a3balias VERIFIED already-gone; ana-docker docker log-cap SOLVED no-bounce. (1) Phantom: absent from/v1/models+/model/info(config+DB registry), zero litellm log refs — the parked "400s in /v1/models" note was STALE (already cleaned in the 2026-07-08 gen repoint to-heretic); bare token survives only in 2 config COMMENTS (lines 76/80). Nothing to remove. (2) Log-cap: running containers were UNCAPPED (182M json-logs, top offender 59M) because daemon.json'smax-size 10m/max-file 3only applies to containers CREATED AFTER a daemon restart — it never reaches already-running ones. No-bounce fix =/etc/logrotate.d/docker-containers(copytruncate — dockerd opens json-logsO_APPENDso truncate-in-place resets cleanly, no sparse-file corruption;size 10M,rotate 3,compress,su root root), auto-picked-up by the dailylogrotate.timer. Force-ran + gzipped the frozen.1archives → 182M → ~55M (44M active + 11M gz), every container kept its multi-week uptime (zero bounce, verified). LATENT FOOTGUN FLAGGED (not yet fixed, operator's call): daemon.json declareslive-restore:truebut the RUNNING daemon has it FALSE (daemon.json was edited after the last daemon start, never reloaded) → the NEXTsystemctl restart docker/ crash / pkg-upgrade bounces ALL ana-docker containers once. Fix WITHOUT a bounce =systemctl reload docker(SIGHUP loads live-restore into the running daemon; log-opts are NOT SIGHUP-reloadable, which is why logrotate — not the daemon cap — is the enforcer for running containers).