5. Multi-part history board

kerfmaster pin list · Big capabilities

recordmixedclosed d12States what the code does today. Auditable against the code — this is the only type that can go stale.

Content last changed 2026-08-02 — computed from the item itself, not typed.

Contract — Report stage

This contract describes the code as it runs today.

takes delivery

makes delivery

fails if A new build overwriting the previous part's result.

Contract last changed 2026-08-06 — computed, not typed. Dated separately from the text above, so neither date can speak for the other.

1 open question blocks this pin

Q19 Which files in the viewer root are still wanted and which are debris?
Aristide — Numbered builds live under viewer/builds/; roughly two dozen loose files predate that and nothing links to most of them.

⚠ Known defects

This item's subject has a known defect in the code. Source: cadmaster/defects.json → cadmaster/KNOWN_DEFECTS.md, not this page — the text below is generated from the register so the two can never disagree.

D12 — The eagle board was published with nothing linking to it (CLOSED)
The audit found the eagle vector board live on disk and unreachable -- grep -c eagle viewer/index.html was 0.
Cost today: None. Kept on the page so A9 is not re-opened from the audit text alone.
Verified: 2026-08-03 at 36a55a3. grep -c eagle viewer/index.html == 1; the link target exists; builds.json carries the entry.

Built 2026-08-02, commit 910df00. The board site root is no longer a single board that the next run overwrites — it is a numbered build history, newest on top.

How it works

boards.py keeps the manifest viewer/builds.json — {"next": n, "builds": […]}, each entry carrying n, label, kind, source, date, summary, status, dir, note.
boards.open_build(label, kind) claims the next number and its own directory; boards.record(…) appends the entry and regenerates the index. Numbering is a single sequence across DXF and vector builds, so "build 14" is unambiguous whatever it was made from.
Each build is written to viewer/builds/NNN-<label>/ with its own index.html and its own artifacts. Nothing is ever overwritten — rebuilding the same label takes a new number, which is what makes a board someone is marking up safe to leave alone.
viewer/index.html is generated by boards.write_index() and lists every build newest first, each card linking to its own page.

Three builds are recorded today: #1 novi-sign (DXF), #2 eagle (vector), #3 ex9-smoke (a wiring smoke test, labelled as such on the history so it is not read as a result).

Still open

Retention — keep everything, or prune old builds? Nothing prunes today.
Grouping — flat list, or grouped by part / customer? It is flat.
The index card shows label, source, date, summary and status; fidelity is not a field of its own.
Files from before the history (viewer/eagle/, and loose .dxf/.nc in viewer/) still sit in the site root, unreferenced by the index.