mirror of
https://github.com/openglow-org/forgefirm.git
synced 2026-09-27 08:41:13 -07:00
ScottW514
05d68ba0a8
BRINGUP had grown to 3,122 lines in which the same subject was answered differently depending on where the reader stopped: GATE A "stays open, no live-fire" in the phase text and closed in the campaign record, the catalog at 24 tests in one section and 35 in another, several "bench validation pending" headings over bodies that recorded the pass. Split by kind rather than by age. BRINGUP (907 lines) is the present state only - status, bench runbook, laser, lid/interlock/button policy, homing, forgectrl, diagnostics, logging, release acceptance, the measured facts bank, and a Next work list of the 15 items that are actually open. CAMPAIGN-LOG (2,657 lines) takes the dated blocks verbatim, in chronological order, and is append-only: a correction is a later entry, not an edit. Its two reading rules are stated up front, since moved text keeps its original "above"/"below" and its pre-split item numbers. Facts corrected against the tree while rewriting: the liveness probe gates at p2p 800, not 500, with the real wedge, noise and jolt figures; the panel has seven tabs including Logs and is built from src/ui/, not ui.c; the devserver replaced tools/mock.py; /status reports real head presence; the estop_halts_motion opt-in is gone; core PR #999 is merged, leaving only the step_us_min commit fork-only; the update system stands at Phase 5, the uSDHC pads and the 2026-08-08 kernel batch have shipped, and 8 MP camera capture is tracked here for the first time. SAFETY and UPDATE-SYSTEM point their drill records at the log. ACCEPTANCE records that inheritance is local: there is no import of a published artifact, so a second bench starts from a full campaign - one of the four open items the retired tool plan held, the rest of which are now in BRINGUP's acceptance item. Documentation only, no behavior change and no catalog consequence: docs/ is outside every layer and .md is excluded from the layer content hash.