Archilyzer · Source

archilyzer

Archilyzer
git clone https://archilyzer.pages.dev/source/archilyzer.git
Log | Files | Refs | README | LICENSE

commit bdbaaa8995ce0ad349069ee551f9a201ed06b5f0
parent e2424587e9bf1b79b822207f673837268942fc5e
Author: I Mean I'm Just Saying <imeanimjustsaying@kiwifarms.st>
Date:   Fri, 25 Sep 2026 13:47:27 -0400

plans: release 7 rollout — the 13:33 state.json revert traced (sharedAutoQueueState caches the value, not the read); fix is release 8 slice S

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

Diffstat:
Mplans/release-7.md | 13+++++++++++++
1 file changed, 13 insertions(+), 0 deletions(-)

diff --git a/plans/release-7.md b/plans/release-7.md @@ -772,6 +772,19 @@ owed:** `grep -h 'deferred 6h' transcripts/.jobs/*.log` — each id at most once N` climbing only across distinct ids. The scan-error refresh proof (a second restart within 24 h logs no `legal-mindset` re-scan) is not provable today: there was one restart. +**And then the disk lost it (13:33:37).** `state.json` was rewritten with the boot-time values +(`fails: 12`, `until` 13:20:03, `videoDeferrals: {}`): the download runner's 13:20 persist was +clobbered by another lane's persist of ITS copy of the whole file. Traced the same afternoon +(`$T/q-state-revert.md`): `sharedAutoQueueState` (`autoRunner.ts:268-293`) caches the resolved +value, not the in-flight read, so the four lanes started together at boot each read the file +themselves and hold a private object for life; `writeAutoQueueState` writes all four lanes from +whichever copy persists. The rename at 13:29 recompiled the priority roots and gave a stale-holding +lane work, hence the 13:33 write. Pre-existing (the comment above that function describes this +exact bug as fixed), not introduced by Y; Y made it visible because a deferral is a value worth +keeping. The running download lane still holds its deferral in memory; a restart would lose it. +Fix = release 8 slice S (`one-core/r8-state-share`): cache the promise. The record above states +what was true at 13:21. + **Found and left.** - **The operator asked: "more 429s than ever — are there multiple YouTube downloads at once?"** No (`q-429-report.md`). Every YouTube-touching job kind lands on ONE `platform:youtube` queue,