Commit Graph
7 Commits
Author SHA1 Message Date
donghyeon-kaandClaude Opus 5.5 4b0e44a92a build(recipes): ratchet the file-transfer bundle budget after lane R
The budget is a size ratchet set about 100 bytes above the measured
reference bundle. file-transfer 55582 -> 55623 gzip bytes: 01-07 moves
the vault release into one finally around put() and open(). Same
rounding rule: 55700.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-09-27 13:57:46 +09:00
donghyeon-kaandClaude Opus 5.5 2c5e268bad build(recipes): ratchet the realtime bundle budget after lanes D and F
The budget is a size ratchet set about 100 bytes above the measured
reference bundle. Measured after merging lanes B, D, F, G, H and J:
realtime 39903 -> 40886 gzip bytes (04-01..04-08 add reconnect rules and
SSE handling; 06-01, 06-02, 06-06, 06-09 add web-push fences and click
handling, and src/adapters/web-push is a realtime recipe source root).
Same rounding rule: 40900.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-09-27 13:30:22 +09:00
DongHyeonkaandClaude Opus 5.5 c8e4794860 docs(browser-files): dispose the file runtime on logout or account switch (02-03)
The runtime does not know the session, so File refs, preview leases and
downloads of the previous user outlived a logout. Section 3.5 and the recipe
lifecycle now say to dispose it, via a scope reset participant if needed.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-09-26 00:03:13 +09:00
DongHyeonkaandClaude Opus 5.5 6fe4aa9e30 build(recipes): ratchet file-transfer and offline-indexeddb bundle budgets
The budgets are size ratchets set about 100 bytes above the measured
reference bundle. Measured on 926f448 and after the wave-1 lanes:
file-transfer 54468 -> 55517 gzip bytes (01-01..01-11 add capability
reissue, size-aware timeouts, probe limiting) and offline-indexeddb
35856 -> 36822 (05-01..05-14 add per-transaction locks, purge sweep and
corrupt-row skipping). Same rounding rule: 55600 and 36900.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-09-25 23:51:35 +09:00
DongHyeonkaandClaude Opus 5 d5e7f4127a chore: derive the remediation closure claim instead of authoring it
The ledger declared "All 38 are now FIXED" while six of those rows were
reproducibly partial. A summary sentence is cheap and a reviewer reads it
as evidence, so the claim is now derived from a machine-readable record:
`docs/operations/adapter-remediation-dispositions.json` carries each
finding's disposition and the test paths that hold it, and
`check:remediation-ledger` joins that file to the prose, verifies every
evidence path exists, and refuses a blanket closure sentence while any row
is still open.

The shared-abort gate had the same weakness in miniature: it passed when
at least one production file imported the primitive, so an unrelated
import satisfied it while Image and Resumable kept their own diverging
copies. It now requires the four named consumers to resolve their import
to the primitive itself, and prints the exact importer set rather than a
count.

`check:optional-recipes:source` was already failing before this work
(52,078 against a 52,000 budget) and the correctness code above pushed it
further. Duplicate abort mechanics were consolidated first — Image and
Resumable onto the shared primitive, four decoders onto one snapshot
helper — and the remainder is code the review asked for, so the budget is
reset to 54,600 against a measured 53,810 with that reasoning recorded,
rather than the failure being carried forward as if it were green.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-15 01:26:27 +09:00
donghyeon-ka 6c52cdb916 feat: 기능 추가 과정중 2026-07-30 15:58:20 +09:00
donghyeon-ka 6c73b845bd feat: add optional frontend adapter recipes 2026-07-26 17:57:04 +09:00