Archilyzer · Source

archilyzer

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

commit 7ba83e6b6dd64b7245f4a9a40ac822d0e8cb6125
parent d223c0e20c7e6da333178232c42e1acf5be76bb9
Author: I Mean I'm Just Saying <imeanimjustsaying@kiwifarms.st>
Date:   Wed, 30 Sep 2026 10:17:45 -0400

plans: slice SG — the re-review's row: a withdrawal never fails over the render cache

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

Diffstat:
Mplans/release-15.md | 1+
1 file changed, 1 insertion(+), 0 deletions(-)

diff --git a/plans/release-15.md b/plans/release-15.md @@ -1544,6 +1544,7 @@ parent's, for the runbook. | L5: stale records | Fix | this commit (the cache path, `total`, the link sentence); PUBLISH.md's timings say which is stagit's and which the step's (`2f02cc7e`); `source publish`'s usage names the history (`8a960a0b`) | | L6: the file-count drop was untested | Test | `8a960a0b`: a `historyFileLimit` seam; the test drops nine history files with the WARNING, and publishes the rest | | L8: a reused pid could hold the lock forever | Stale by pid or age | `8a960a0b`: a lock whose pid is not running, or over an hour old (`HISTORY_LOCK_STALE_MS`), is replaced with one line | +| Re-review (SHIP): a withdrawal could throw over the render cache (`dropHistoryCache` on a read-only cache) and lose the refusal's exit | Catch it | `2aa0d7c3`: one masked line ("the history's render cache <dir> could not be removed (<code>); remove it by hand"); the exit 1 and the withdrawal stand; a test refuses with a read-only cache dir (`source` 22 tests, tsc clean) | | Commit | What | |---|---|