Reconcile Build

Hold the closeout procedures a multi-session build runs after its tickets land — so they live in one place with their templates and checkers, and the tail REC.* tickets just say "invoke reconcile-build mode=…" (the way the docs tickets say "invoke refresh-repo-docs"). Folding these into orchestrate-build would push that SKILL past the line ceiling and mix sequencing with content; this skill is the content.

Precedent. agent-docs / refresh-repo-docs own the docs procedures the DOC.* tickets invoke; reconcile-build owns the reconciliation procedures the REC.* tickets invoke. It reads and writes the committed build memory defined in skills/build-memory/layout.md (it cites that file, does not restate it): DEFERRALS.md, docs/adr/, the ledger's OPEN FINDINGS, COVERAGE_MATRIX.csv, BUILD_INDEX.md, and the BACKLOG.* / *_PLAN.md / OPERATIONAL_READINESS.md outputs under docs/build/.

Orient

Resolve the memory root (build-memory memory-root.sh); confirm docs/build/ exists and the validator is green (check-build-memory.sh .) before reconciling — reconciliation over an inconsistent layout is noise. Then follow the mode.

The modes

The one discipline that matters

Every owed thing lands in exactly one backlog row. The failure mode of build closeout is debt that is "tracked" in five places and therefore nowhere. backlog gathers every source — each OPEN/PARTIAL deferral, each ADR revisit trigger, each OPEN FINDINGS entry, each spec-mandated register's deferred row, each non-MET coverage-matrix row — into a single sources cell, and scripts/check-backlog.sh fails if any source appears zero times or more than once. That is the backlog's contract: complete and non-duplicating.

Scripts (bash 3.2+, read-only)

What this skill does NOT do

• No sequencing — orchestrate-build runs the REC.* tickets; this skill is what they invoke.
• No merging, no CI fixing, no release — CI state is read (read-only) and reported; merge-dryrun.sh is read-only; the actual merge/release is the operator's, from the copy-pasteable procedure integration writes.
• No silent spec edits — spec writes proposals; it applies an amendment only where the plan is ticked and apply_amendments=true, always through spec_src when it exists, with a manifest amendment line + an ADR.