amadan
Readiness and handoff: the design branch's tenth code review answered (3678b940) and Part C's fifth slice, the gate and the fleet, landed after it (358b25ee); eleventh review and a gate running; the gate on f11464ec passed
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2 files changed,
+2
−2
.claude/HANDOFF.md+1 −1implementation/carloku-paid-launch/READINESS.md+1 −1
CI passed — run details
diff --git a/.claude/HANDOFF.md b/.claude/HANDOFF.md| index dec39f5db..08f20f702 100644 |
| --- a/.claude/HANDOFF.md |
| +++ b/.claude/HANDOFF.md |
| @@ -45,6 +45,6 @@ Branches (all on the forge, none merged; the local gate is not CI): |
| - Then, each on its own branch: quantity reduction at renewal, the evidence door for a box's first minutes, the AWS principal inventory and the bucket ownership attestation door, Free-tier enforcement, dormancy and pool accounting. |
| **SESSION:** |
| -Running at 12:51: the tenth code review (Opus and Astra) and the gate on the design branch at `f11464ec`, two commits over `c824ed81`: `a579d845` answers the ninth review (Opus accept with fixes with one P1, Astra reject with three P1: holds, the latch and settlements must dirty and republish their days; the snapshot across a replay; the latch's lost bound; plus the P2s) with design revision 15, and `f11464ec` lands plan Task 4's fourth slice (the fleet journal, backfill, acknowledgement) after them, as the owner asked. The gate on `c824ed81` failed on `TestMaintenanceFenceSerializesSidecarSweepReplacement` in `internal/activator`, which this branch does not touch (filed as amadan #206). Reports land in `logs/{opus,astra}-replroot-review10.md`, the gate in `logs/gate-replroot-f11464ec.log`. |
| +Running at 13:29: the eleventh code review (Opus and Astra) and the gate on the design branch at `358b25ee`, two commits over `f11464ec`: `3678b940` answers the tenth review (Opus accept with fixes, three P2; Astra reject, one P1 and five P2) with design revision 16, and `358b25ee` lands plan Task 4's fifth slice (the gate and the fleet: the request gate returns an admission, the fleet registers, commits, rechecks, discovers into the ledger, and journals) after them. The gate on `f11464ec` passed (exit 0, three cross builds). Reports land in `logs/{opus,astra}-replroot-review11.md`, the gate in `logs/gate-replroot-358b25ee.log`. Next: slices 6 (the fence and recovery) and 7 (the C2 reader marker) in a tree copy. |
| Scratch on the box: `~/.cache/tmp/claude-1001/{currency-wt,replicator-wt,fencing-wt,evidence-wt,opcli-wt,inventory-wt,flush-wt,reduction-wt}` (git worktrees), the demo binaries, `/var/tmp/ck`, `~/.cache/carloku-gate`. The void gate logs are named `*VOID*`. |
diff --git a/implementation/carloku-paid-launch/READINESS.md b/implementation/carloku-paid-launch/READINESS.md| index acd16f912..5afb8d650 100644 |
| --- a/implementation/carloku-paid-launch/READINESS.md |
| +++ b/implementation/carloku-paid-launch/READINESS.md |
| @@ -25,7 +25,7 @@ Log files are under `/home/paulca/.local/share/carloku-paid-launch-20260930/logs |
| | `feat/carloku-billing-operator-cli-20261002` | `fc7daebd` (a merge of the currency tip `2b0abef1`); before it `6d4c2912` (the fourth review's P3s answered: `account_deleted` always on the wire and printed; the console's own 5xx on a write; the moved console after the offer; the help's two facts); before it `4e9cac43` (`f9683fbe`: the third review's twelve P3s answered: a write names its console or is refused; refusals from in front of the console; the moved console through the interactive offer; the whole command tested through `runBillingWith`; then the currency tip `e152df30` merged in); before it `31731fdd` (Astra's second review answered in `f155e543`: ambiguous flag values refused, the keep wording, strict listing envelopes, write advice that fits the write, the console's note predicate, `billingRun` tested; then the currency tip `05ccec07` merged in); before it `51ef27ac` (the first review answered in `57f70c16`, then the currency tip `b260ac8e` merged in): `carlos billing reviews\|resolve\|rejected\|house`, a client for the four operator doors | `fc7daebd`: **passed** (01:04Z, `gate-opcli-fc7daebd.txt`, exit 0, three cross builds, alone). `40ea61b1`: **passed** (00:08Z, `gate-opcli-40ea61b1.txt`, exit 0, three cross builds, alone). `6d4c2912` was not gated on its own (superseded by the merge). `4e9cac43`: **passed** (23:09Z, `gate-opcli-4e9cac43.txt`, exit 0, three cross builds, alone). `51ef27ac`: **passed** (21:29Z, exit 0, three cross builds); `31731fdd`: **passed** (22:16Z, `gate-opcli-31731fdd.txt`, exit 0, three cross builds). `0f507bff` **failed** (exit 2, `gate-opcli-0f507bff.txt`): one test, the docs gate, which requires a `carlos billing` heading in the public CLI reference. `51ef27ac`: started 21:18Z, run alone (`gate-opcli-51ef27ac.txt`) | passed on `6d4c2912`, `40ea61b1` and `fc7daebd`; `0f507bff` failed (the docs gate) | 4 at `4e9cac43`: **both accept with fixes, all P3**, answered in `6d4c2912` (CI passed); no fifth review unless the client changes. 3 at `31731fdd`: **both accept with fixes** (six P3 each), answered in `f9683fbe`; a fourth reading not started. 2 at `51ef27ac`: Astra accept with fixes (three P2, six P3), answered in `f155e543`; Opus's second reading and Astra's third running on `31731fdd`. 1 at `0f507bff`: Opus accept with fixes (P1 the docs gate, four P2), Astra reject (five P2). Answered in `57f70c16`: arguments are one unambiguous request or refused before anything is sent; writes are reported only on the door's acknowledgement and name the console; one wire-contract file both sides' tests read. Second review not started | **merged into this branch at `1cd5a0d8` (02:12, a merge commit) after the gate and CI on `fc7daebd`; its `docs/site/cli.md` section is unreviewed public copy and must be read before anything publishes the site's CLI page (merging publishes nothing)**; before: not merged (it is built on the currency branch, which merges first). **Its `docs/site/cli.md` section is new public copy and is unreviewed**: it does not merge before Paul reads it |
| | `feat/carloku-principal-inventory-20261002` | `4a1a92d9` (the sixth review answered: an S3 action on an Object Lambda resource is a possible reach, the "possibly" label and the legend extended, the mutation paragraph as the logs have it); before it `36e5ff2d` (the fifth review answered: the possible reach decided by one text test on the pattern and its padded form, decision 14 names what the host role can mint through a store user, the legend's other spellings, a nil page an error); before it `403384c2` (the fourth review answered: a resource pattern read as text and, when it is an incomplete ARN, as padded fields too, a reach under either reported; nothing S3 names excluded, Storage Lens included; an empty condition, an operator with no key and an empty value list are errors; the `AssumableBy` legend and the "does not read" lists reworded for same-account trust, control of compute and IAM writes; counts tagged; the CUR plan and OUTSTANDING item 2 no longer name an inventory in the provisioner as the mechanism); before it `434cdf48` (the third review answered: every S3 resource that is not the bucket a possible reach; incomplete ARNs as IAM reads them; version ids unique; condition values checked; a group's possible reach carried to its members; the label renamed `named_by_deployment`; the attestation plan marked superseded in part); before it `0e1bc298` (the second review answered: a repeated JSON member is an error; a managed policy's default-version id must agree with the version marked default; every trust-policy statement read in full; a grant on an access point, a multi-region access point or an Object Lambda access point reported as a possible reach, marked; the two proposals stated with what they lack); before it `199a9736`: **a report for a person** (`PrincipalReport.BucketPrincipals`: who reaches a name, through which policies, and who each role's trust policy lets assume it), **not a `GranteeProber`** and a test says so; before it `d61f4f27`, which offered itself as the ledger's proof | `4a1a92d9`: **passed** (00:36Z, `gate-inventory-4a1a92d9.txt`, exit 0, three cross builds, alone). `36e5ff2d`: **passed** (00:26Z, alone). `403384c2`: **passed** (00:14Z, alone). `434cdf48`: **passed** (23:44Z, alone). Mutants in git-less tree copies with the killing tests logged from round five on: `inventory-mutants-round{1..6}.txt` | passed on `0e1bc298`, `434cdf48`, `403384c2`, `36e5ff2d` and `4a1a92d9` | **7 at `4a1a92d9`: both accept** (Opus: every sixth-round finding closed, two P3 bookkeeping items, neither required; Astra: accept, no new finding). 6 at `36e5ff2d`: Opus accept (three P3), Astra accept with fixes (one P2: Object Lambda's management actions in the s3 namespace on an Object Lambda resource), answered in `4a1a92d9`. 5 at `403384c2`: both accept with fixes (one P2 each: the possible-reach rule's text reading skipped for a complete pattern with a question mark across a colon; decision 14 understating the host role), answered in `36e5ff2d`. 5 at `403384c2`: running since 00:57 (Opus's third reading and Astra). 4 at `434cdf48`: Opus accept with fixes (two P2 required: an incomplete ARN read only as padded fields dropped grants the text reading reported; the legend wrong in the under-reporting direction), Astra reject (three P2: the Storage Lens exclusion dropped a write path; empty condition shapes read as a report; the legend), all answered in `403384c2`. 3 at `0e1bc298`: Opus accept with fixes (two P2 required: other S3 resource types dropped; the attestation plan still claiming an IAM read proves completeness), Astra reject (four P2, two P3). Answered; gate not yet run; never run against AWS. 1 at `d61f4f27`: Astra reject (three P1). Answered in `199a9736` by making it a report. 2 at `199a9736`: Astra reject (six P2: access-point grants under-reported; duplicate JSON members; default-version metadata not checked; trust-policy grammar; the two proposals overstated). Opus not yet read. Answered in `0e1bc298`; the third review (Astra) and Opus's first reading running on it | **merged into this branch at `c4ee8807` (01:40, a merge commit) after round seven's two acceptances, the gate and CI on `4a1a92d9`; the gate on the merged tip `c4ee8807` is queued behind the currency gate**; a report for a person, unwired; what a completeness claim needs is now decision 14 (an enforced rule; minted bucket names); the report can be run by an operator with their own credentials; never run against AWS |
| | `design-per-line-tax-codes` | `12590e3a` (per-line tax codes for a month in which the plan changed, OUTSTANDING item 17: the mechanics either answer to decision 16 needs, built behind the hold; design revision 6 after three Astra design rounds; Tasks 0 to 4, the activation glue uncalled, three mutant batches) | `12590e3a`: **passed** (05:08Z, `gate-taxcodes-12590e3a.txt`, exit 0, three cross builds, alone); also `6488c198`, `8715e4cd`, `61313bec`, each alone; each commit had the full console, plans and billingstripe run | passed on `61313bec`, `8715e4cd`, `6488c198` and `12590e3a` | 1 at `61313bec`: both accept with fixes (Opus one P2, Astra three P2); 2 at `8715e4cd`: both accept with fixes (P3s only); 3 at `6488c198`, confirming: both accept with fixes (P3s only, no further round required), the fixes in `12590e3a` | **merged into this branch at `e2adf26f` (06:10, a merge commit) with Task 5's records; a two-code month still holds; decision 16 and 16a to 16d are Paul's; every one-code month is byte-identical (pinned); one behaviour changes for every month: a resumed finalize validates the draft it read** | |
| -| `design-replicator-pinned-root` | `f11464ec` (the design at **revision 15**; review nine answered at `a579d845`: a hold, a latched discovery, an admission and its settlement are publication events and publication enumerates the latch's days (a Publish-level test), the snapshot reads again across a replay, a failed discovery keeps its computed bound or latches unresolved, the replay closes on the settlement's test, the discovery instant floors closure, the handoff compares the identity of the listing chain, the roots' recheck aggregates, the configuration reader takes hand-written YAML; plan Task 4's fourth slice landed at `f11464ec`: the fleet journal, construction backfill and root-first acknowledgement; plan Task 4's second and third slices landed: the barrier (`DurabilityContent.Barred`, counted in the snapshot's read transaction) and discovery, the uncertainty and the latch in the durability ledger (`Discover` with the fixed bound and the counted set, box-wide holds, the settlement hook, the in-memory latch and `Replay`, `DurabilityContent.Held`); review eight answered: the ledger's transitions follow the table's edges, the token allocated before the write, idempotent repeats, backdated instants refused, the settlement no earlier than now; the inventory carries the strict walk's listed facts into the ownership checks, the recheck visits everything, required coverage is ownership, `Hold` returns an error, `carlos ops inventory` opens the registry read-only and compares the live configuration; plan Task 4's first slice landed: the durability ledger's admissions, fleets, uncertainties, inherited and holds tables and the admission row's transitions, tests mirroring the model; plan Task 3, required coverage, landed: `RequiredDatabases`, the inventory's `Required` with why each is unreachable, the options' `Hold` at a fleet build, `carlos ops inventory` read-only; plan Task 2 complete in three slices: the inventory's tree walk, `checkOwnedFile` and the fleet's retained chains on descriptors, the pathname helpers retired, every link class named, the root rule where the platform's authority ends, every look rechecking what the fleet holds; **gates on `ccfd331a` and `cc1500a9` passed (exit 0, three cross builds each)**; revision 8 `8a877936` was accepted; revisions 9 and 10 correct the uncertainty's lower bound after the admission model's code reviews found an in-flight request across a change, settled clean before the discovery, outside it, and then a witness change known only to be after the proof; the step-1 task plan `docs/superpowers/plans/2026-10-03-replicator-authority-plan.md`; plan step 0's admission model and step 1's `internal/authority` on it, reviews one and two answered; nothing wired, imported by nothing in `internal/ops`) (revision 8: the replicator's authority, answering review twenty's eleven deferred findings: retained descriptors with a stack, anchors and named-edge rechecks; the litestream fork and a SQLite VFS owning every file method in a helper process per fleet; a durable admission before every send, settled by the last participant, with a temporary barrier, a permanent uncertainty linked at construction and inherited transitively, a pending-discovery latch, and a producer fence for recovery; owner holds as a specified ledger change with box-wide the default; claims by owner and identity with one replication authority and a durable lineage record; a uid lifecycle and a sleeping route's binding from the unit observer; decisions 10-13 and approval H kept as parameters; off the replicator branch at `e1280811`) | not applicable (a document) | not applicable | design reviews 1 to 6 (Astra): reject (five, three, five, four, two, one P1), each answered; **review 7 (Astra): accept with fixes, no P1** (one P2: a cancellation was not conclusive while the admission writer could still commit, and the pending set had three definitions; one P3: the restore wording), both applied in revision 8 (a cancellation waits for the writer to return, a read-back only after its handle is closed, one pending-set contract, the restore sentence limited to what the fork's verification chooses); **review 8 (Astra): accept, no finding** (both fixes meet the smallest acceptable fix; the design stands at `8a877936`); revision 7 reconciles a failed discovery's replay with the settlements that landed meanwhile, registers the recorder at Start and closes a never-started one as unrecorded after proven helper exit, completes the transition table's abort edges and pending-set cleanup, and gives the lineage record its own crash-durable write protocol; revision 6 separates ownership proof from request admission, gives the admission one ordering point against discovery under the fleet's mutex, backfills a new fleet's owners with its ancestry's intervals, makes the transition table authoritative with a dead helper's transport lost and its recorder never synthesised, and names the sleeping binding's invalidators; plan step 0's admission model committed (`f331b55a`: thirteen named sequences, 30000 random schedules under barrier, hazard, reach and liveness invariants, fourteen mutants killed, one equivalent; the spike note records it); plan step 1's `internal/authority` committed (`5bfcc7ba`: Dir, Root, Walk, the Part A tests; cross-builds for darwin and windows; two findings while building: Linux answers ENOTDIR for a link under O_DIRECTORY, so a link is named by one look; the walk's grammar is refused before any syscall); **code review 1 (Opus: accept with fixes, no P1; Astra: reject, five P2 two P3, the same points) answered at `50a6f056`** (Confine, Equal in Recheck, slash as a pin, descriptor accounting, the model's boundaries as separate actions and the ancestry barrier; `DISPOSITIONS-replicator-pinned-root.md` names each); **code review 2 (Opus and Astra: both accept with fixes, no P1) answered at `0a527924`**, with design revision 9's bound; **code review 3 (both accept with fixes, no P1) answered at `7ba5fc72`** with revision 10; **code review 4 (both accept with fixes, no P1) answered at `a26cba8e`** with revision 11 (the historical term counts every settlement whose transport sent; the cutoff is the fixed bound); **code review 5 (both accept with fixes, no P1: the root rule refused legal platform links; the inventory tests did not distinguish the slice) answered at `cc1500a9`** with the second slice; **code review 6 (both accept with fixes, no P1: a later platform link needing a higher root; the platform-directory claim's terminal-link refusal lost; an absolute tenant link through the tree's own root) answered at `28e7f4d6`** with the third slice; **gates on `28e7f4d6` and `f0ed32b7` passed (exit 0, three cross builds each); code review 7 (both accept with fixes, no P1: the descriptor count under links; a non-change recheck error staling; a relative ascent after an absolute link) answered at `47efe06f`; gate on `47efe06f` passed (exit 0, three cross builds); code review 8 (both accept with fixes, no P1) answered at `c824ed81`; **code review 9 (Opus: accept with fixes, one P1; Astra: reject, three P1: holds and the latch never reached a published day; a snapshot could read neither the latch nor the replayed rows; a latch whose re-read failed lost its bound) answered at `a579d845`, slice 4 landed after it at `f11464ec`; the gate on `c824ed81` failed on an activator test this branch does not touch (amadan #206, a 15 ms deadline under load, five of five alone); code review 10 and a gate on `f11464ec` running since 12:51** | nothing wired; next the inventory on `internal/authority` (the rest of step 1), then required coverage (Part D); the VFS spike needs a box with both architectures | |
| +| `design-replicator-pinned-root` | `358b25ee` (the design at **revision 16**; review ten answered at `3678b940`: the listing directory retained across the handoff, one open uncertainty per fleet, closure closes what nothing else will, the latch's days dirtied when it clears, publication from the ledger's earliest day with explicit bounds, the configuration reader refuses what it cannot take; plan Task 4's fifth slice landed at `358b25ee`: the gate and the fleet, `lease.RequestGate` returning an admission whose participants the middleware completes, the fleet's registration under the discovery mutex, the row within a budget, the recheck, discovery into the ledger, the journal's rows at build, close and open; review nine answered at `a579d845`: a hold, a latched discovery, an admission and its settlement are publication events and publication enumerates the latch's days (a Publish-level test), the snapshot reads again across a replay, a failed discovery keeps its computed bound or latches unresolved, the replay closes on the settlement's test, the discovery instant floors closure, the handoff compares the identity of the listing chain, the roots' recheck aggregates, the configuration reader takes hand-written YAML; plan Task 4's fourth slice landed at `f11464ec`: the fleet journal, construction backfill and root-first acknowledgement; plan Task 4's second and third slices landed: the barrier (`DurabilityContent.Barred`, counted in the snapshot's read transaction) and discovery, the uncertainty and the latch in the durability ledger (`Discover` with the fixed bound and the counted set, box-wide holds, the settlement hook, the in-memory latch and `Replay`, `DurabilityContent.Held`); review eight answered: the ledger's transitions follow the table's edges, the token allocated before the write, idempotent repeats, backdated instants refused, the settlement no earlier than now; the inventory carries the strict walk's listed facts into the ownership checks, the recheck visits everything, required coverage is ownership, `Hold` returns an error, `carlos ops inventory` opens the registry read-only and compares the live configuration; plan Task 4's first slice landed: the durability ledger's admissions, fleets, uncertainties, inherited and holds tables and the admission row's transitions, tests mirroring the model; plan Task 3, required coverage, landed: `RequiredDatabases`, the inventory's `Required` with why each is unreachable, the options' `Hold` at a fleet build, `carlos ops inventory` read-only; plan Task 2 complete in three slices: the inventory's tree walk, `checkOwnedFile` and the fleet's retained chains on descriptors, the pathname helpers retired, every link class named, the root rule where the platform's authority ends, every look rechecking what the fleet holds; **gates on `ccfd331a` and `cc1500a9` passed (exit 0, three cross builds each)**; revision 8 `8a877936` was accepted; revisions 9 and 10 correct the uncertainty's lower bound after the admission model's code reviews found an in-flight request across a change, settled clean before the discovery, outside it, and then a witness change known only to be after the proof; the step-1 task plan `docs/superpowers/plans/2026-10-03-replicator-authority-plan.md`; plan step 0's admission model and step 1's `internal/authority` on it, reviews one and two answered; nothing wired, imported by nothing in `internal/ops`) (revision 8: the replicator's authority, answering review twenty's eleven deferred findings: retained descriptors with a stack, anchors and named-edge rechecks; the litestream fork and a SQLite VFS owning every file method in a helper process per fleet; a durable admission before every send, settled by the last participant, with a temporary barrier, a permanent uncertainty linked at construction and inherited transitively, a pending-discovery latch, and a producer fence for recovery; owner holds as a specified ledger change with box-wide the default; claims by owner and identity with one replication authority and a durable lineage record; a uid lifecycle and a sleeping route's binding from the unit observer; decisions 10-13 and approval H kept as parameters; off the replicator branch at `e1280811`) | not applicable (a document) | not applicable | design reviews 1 to 6 (Astra): reject (five, three, five, four, two, one P1), each answered; **review 7 (Astra): accept with fixes, no P1** (one P2: a cancellation was not conclusive while the admission writer could still commit, and the pending set had three definitions; one P3: the restore wording), both applied in revision 8 (a cancellation waits for the writer to return, a read-back only after its handle is closed, one pending-set contract, the restore sentence limited to what the fork's verification chooses); **review 8 (Astra): accept, no finding** (both fixes meet the smallest acceptable fix; the design stands at `8a877936`); revision 7 reconciles a failed discovery's replay with the settlements that landed meanwhile, registers the recorder at Start and closes a never-started one as unrecorded after proven helper exit, completes the transition table's abort edges and pending-set cleanup, and gives the lineage record its own crash-durable write protocol; revision 6 separates ownership proof from request admission, gives the admission one ordering point against discovery under the fleet's mutex, backfills a new fleet's owners with its ancestry's intervals, makes the transition table authoritative with a dead helper's transport lost and its recorder never synthesised, and names the sleeping binding's invalidators; plan step 0's admission model committed (`f331b55a`: thirteen named sequences, 30000 random schedules under barrier, hazard, reach and liveness invariants, fourteen mutants killed, one equivalent; the spike note records it); plan step 1's `internal/authority` committed (`5bfcc7ba`: Dir, Root, Walk, the Part A tests; cross-builds for darwin and windows; two findings while building: Linux answers ENOTDIR for a link under O_DIRECTORY, so a link is named by one look; the walk's grammar is refused before any syscall); **code review 1 (Opus: accept with fixes, no P1; Astra: reject, five P2 two P3, the same points) answered at `50a6f056`** (Confine, Equal in Recheck, slash as a pin, descriptor accounting, the model's boundaries as separate actions and the ancestry barrier; `DISPOSITIONS-replicator-pinned-root.md` names each); **code review 2 (Opus and Astra: both accept with fixes, no P1) answered at `0a527924`**, with design revision 9's bound; **code review 3 (both accept with fixes, no P1) answered at `7ba5fc72`** with revision 10; **code review 4 (both accept with fixes, no P1) answered at `a26cba8e`** with revision 11 (the historical term counts every settlement whose transport sent; the cutoff is the fixed bound); **code review 5 (both accept with fixes, no P1: the root rule refused legal platform links; the inventory tests did not distinguish the slice) answered at `cc1500a9`** with the second slice; **code review 6 (both accept with fixes, no P1: a later platform link needing a higher root; the platform-directory claim's terminal-link refusal lost; an absolute tenant link through the tree's own root) answered at `28e7f4d6`** with the third slice; **gates on `28e7f4d6` and `f0ed32b7` passed (exit 0, three cross builds each); code review 7 (both accept with fixes, no P1: the descriptor count under links; a non-change recheck error staling; a relative ascent after an absolute link) answered at `47efe06f`; gate on `47efe06f` passed (exit 0, three cross builds); code review 8 (both accept with fixes, no P1) answered at `c824ed81`; code review 9 (Opus: accept with fixes, one P1; Astra: reject, three P1) answered at `a579d845`, slice 4 landed after it at `f11464ec`; the gate on `c824ed81` failed on an activator test this branch does not touch (amadan #206); **the gate on `f11464ec` passed (exit 0, three cross builds); code review 10 (Opus: accept with fixes, no P1, three P2; Astra: reject, one P1: the unresolved latch's publication floor; five P2: replay serialization, the overlay's inverse, the retained-directory handoff, unsupported YAML read as empty, closure outrunning an empty settlement) answered at `3678b940`, slice 5 landed after it at `358b25ee`; code review 11 and a gate on `358b25ee` running since 13:29** | nothing wired; next the inventory on `internal/authority` (the rest of step 1), then required coverage (Part D); the VFS spike needs a box with both architectures | |
| | site `feat/paid-pricing-20260916` (GitHub) | `01b62f7` (the money renderer a module the test calls); before it `4026231` (`build` and `check` render from the export before the draft check, so a stale page cannot be published past a newer export; a floor that is not whole cents is refused by the renderer rather than shown as `$1.20.5`; after `c12318d`: `bands.p3` replaced by the approved explanation, every priced slot, inclusion band and figure token pinned exactly) | `node --test test/*.test.mjs`: 21 pass (09:1xZ) | n/a | read-only by the currency reviews (section K); rounds four, five, ten, twelve to seventeen's site findings fixed | preview served at `http://100.119.180.57:38009` from the tree (rebuilt with the `bands.p3` change) | |
| ## The flow, behaviour the tests establish (2026-10-02) |