Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Documents-only copy of class-v6-adversary bb8cf8c30 over master 156f3f54e: the document whole, the batch adversary-20261008-placed-8lane recorded through tools/ci/test-record.mjs on master's registry copy, the two map cells added to master's map, the harness page regenerated; tools/chip-model/mf stays on the branch.
Rows: docs/analysis/review-2026-10-08-b/f10/rows.md with the pod rows (5090: steady
70.4 MH/s select against 63.7 full, 86.2 against 88.7 J per 2^24 batch; 3090 at the
card's clock 30.1 against 27.6, 184.6 against 197.9 J; the 3090 pod's power cap at
210 MHz named per run; ptxas 92 and 87 registers, no spills) beside the kernel timer,
the emulation and loader logs, the mini's geometry and serve logs. serve-bench.sh reads
a kit pack's seeds from program.h, execs the worker in its coproc (the recorded pid
and the CPU seconds are the worker's).
I05: every worker's found line carries a fifth field, the epoch the hash was computed
under (16 hex): CUDA and OpenCL from the pair, Metal from the job; select-check.sh and
serve-check.sh assert it, the swap case with pack B's epoch. The miner reads four or
more fields.
I06 (gate INT-10): one normative geometry rule. packfile.h reads the word count at
64 bits and refuses a count above 2^32 - 1 and a log2 that is not the floor of log2 of
the count; proto-metal/main.swift gains packGeometry with the same rules and refusal
words, sizes the day's dataset from the exact word count before any Metal work, and
--geometry-check <vectors> [pack dir...]. emu/geometry-vectors.txt is the shared
conformance file (ds55, ds85, ds115, the power-of-two sizes, wrong count or log2,
overflowing counts, missing leaves, leaves on a v2 pack): 19 vectors green in C on
build-7 (packfile-test.sh) and in Swift on the mini, with the two checked-in packs.
Record: cells harness:cuda-select-check (ROT-01, POW-01 partial) and
harness:pack-geometry (POW-02 partial); batch f10-worker-20261008.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Documents-only copy of counter-asic-4 248837578 over master f1c1fd9d1 (the 21:00 landing): the design and analysis documents, spec 05 and 06 (06 and the export list three-way merged), sim/economy/coexist (python, JSON, TSV), the map cell harness:economics-model added to master's map, the batch eco-d4-20261008-01 recorded through tools/ci/test-record.mjs on master's registry copy; nothing under igneum-pow, proto-cuda or the apps; the branch itself unmerged.
tools/ci/int-suite.mjs writes the INT suite from docs/plans/igneum-2.0-master/traceability.json's integration_gates (the requirement verbatim as title and accept, source R1, NOT RUN, the owner per the coordinator's crosswalk) and regenerates at the merge like REV; the master's counting note is a registry-level note ("128 original test cases, 18 additional integration gates, 44 updated-stack closure requirements. These sets overlap and are not 190 independent tests."); REC-01's closure evidence (rule v4 on 12424341's line, mode recovery by the founder's ruling, both real-node lines PASS, FIN-02 PASS at 4089e3d31) is a dated note on FIN and on INT for INT-05 and INT-06, RUNNING until the beyond-window healing case runs natively. INT-17 in test-record.mjs: a batch cell that declares prereqs with any oracle, pinned keys or real-proof fixture missing is written BLOCKED with the missing ones named, never PASS; self-tested both ways.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
The verification rows re-run on the 2.0 devnet with the lock-state code: VER-03, VER-04, VER-06, VER-08 pass (coverage names
the F04 cases), VER-01 and VER-02 FAIL by design, VER-05 FAIL on this run because the public read node now reports
startedFrom snapshot (the reader on build-1 is still from genesis); VER-05 moves to harness:reference-apps-ver-availability
so its verdict never drags the other rows. Recorded through test-record.mjs; the harness map page regenerated.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
tools/ci/review-suite.mjs writes the REV suite from docs/analysis/review-2026-10-08-b/findings.json and dispatch.md: one case per required regression (REV-F01-1 onward), the regression line verbatim as title and accept, status NOT RUN, the owner lane from the dispatch table, the finding id and priority carried as fields; every unmapped case gets a NOT RUN reason in tools/ci/test-map.json naming its owner lane; the gate's check refuses a registry whose REV suite drifts from the findings. The founder's 19:57 rulings on F04 (the recovery lock kept, always labelled recovery) and F14 (the public miner from 2.0.2 without remote jobs; the lab build for our fleet) are dated notes on the FIN, UX and OPS suites through test-record.mjs --note, and resolved fields in F0. The harness page is regenerated.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
