timothy/ersatztv
1
0
Fork 0
Code Issues 51 Pull Requests 5 Actions Packages Projects Releases 9 Wiki Activity
Files
35a8ea8aefc1066e92d6b534e6ac360cb359d438
ersatztv/docs/decisions/release-ci-governance.md
T
timothy fba5233caf
PR Gates / CI image pin matches docker/ci (pull_request) Successful in 11s
Details
PR Gates / Docs update reminder (pull_request) Successful in 16s
Details
PR Gates / decisions lifecycle (pull_request) Failing after 23s
Details
Build ErsatzTV Image / Formatting (changed .cs conform to .editorconfig) (pull_request) Successful in 1m17s
Details
Build ErsatzTV Image / API docs in sync (OpenAPI + endpoint index) (pull_request) Successful in 1m29s
Details
Build ErsatzTV Image / Build & test (.NET) (pull_request) Successful in 8m5s
Details
Build ErsatzTV Image / EF migration integrity (SQLite + MySql) (pull_request) Successful in 16m5s
Details
Build ErsatzTV Image / Functional E2E (curl + UI contracts) (pull_request) Successful in 17m6s
Details
Build ErsatzTV Image / Build & push image (amd64) (pull_request) Has been skipped
Details
feat(610): split the decision corpus into one YAML-frontmatter file per record 
168 records -> docs/decisions/records/<area>/<topic>.md (163 active, 23 dirs) and
docs/decisions/archive/<area>/<topic>.md (5 archived). The filename IS the key,
so one-active-record-per-key becomes a filesystem property rather than a
validator check, and supersession becomes a `git mv`.

WHY: the monolith was a concurrency problem before an aesthetic one. A
3,900-line append target made parallel sessions collide -- PR #605 and PR #614
both hit append-vs-append conflicts during routine rebases, and hand-resolving
those inside the corpus is exactly the operation the rationale-rewrite guard
exists to police.

HOW IT IS VERIFIED: a ~170-file diff cannot be meaningfully read, so correctness
does not rest on reading it. The parser was taught BOTH formats first, so the
body-diff guard parses the old form at the merge-base and the new form at head --
the migration validates itself, no bypass. The proof is a field-level equivalence
harness: 168 records before and after, zero lost, zero gained, zero field
mismatches, zero rationale bodies differing. Reviewers should scrutinise the
harness; it is the actual evidence.

What measuring caught that reading would not have:

- ~500 lines sit OUTSIDE any record -- decisions.md's lifecycle schema and each
  topic file's preamble, mostly the only copy. Source files are kept and
  stripped, never deleted. They also cannot be filed per-area: topic files hold
  several areas and 4 of 23 areas span several files.
- Archive discovery was a non-recursive glob; after the split it found ZERO
  archived records, surfacing as four bogus "supersedes points to unknown key"
  errors rather than an obvious failure.
- ~32 live docs point into the corpus BY DATE, which the split dangles. Each
  stripped file now ends with a generated "Records formerly in this file" index,
  which also rescues the identical breadcrumbs in old issue comments.
- decisions.md's "In this file:" list was 97 same-file anchor bullets that the
  split makes WRONG, not merely stale. Dropped; the generated index replaces
  them with links that resolve.

The equivalence harness now runs against a checked-in FIXTURE, not the live
corpus. The earlier version migrated the real tree, which made it a one-shot:
the moment the migration landed there was nothing left to move and the tests
failed for reasons unrelated to the code. A fixture keeps them testing the
SCRIPT rather than the repo's current state.

Keys preserved verbatim, warts included: `sched` (12) and `scheduling` (1) remain
two directories for one concept. Renaming a key is not a move -- it changes
identity, breaks the equivalence proof, and invalidates MemPalace's per-key
drawers. Taxonomy normalisation is separate work.

refs #610
2026-07-25 19:45:09 +02:00

3.2 KiB
Raw Blame History

Release, CI & merge-governance decisions (#303, #311, #314, #315, #335)

Why the merge/release process is enforced by hooks and CI gates rather than prose: the #303 methodology-hardening waves (state-derived merge-consent, API-contract CI gate, append-only decisions log, review-verdict gate), formatting-as-you-touch + rebase discipline, the auto-grant fix, migration rehearsal on a prod-DB copy, and release promotion. Rationale relocated from the append-only docs/decisions.md at the v26.9.0 consolidation; operational detail cross-links to docs/ci-cd.md and CLAUDE.md → Task Completion Protocol.

Issue trail: #303 (H4/H5 api-docs gate, H6 Done-when, H9 append-only (archived), H3 root-png (active), H10 review-verdict), #311 (H11 formatting/rebase), #314 (merge-gate auto-grant), #315 (migration rehearsal), #335 (release promotion). The whole hook program's throughline: make each process rule a derivation/hook, not prose to remember (#303 methodology review).

Contents

  • (archived 2026-07-21) 2026-07-12 — decisions.md is append-only, enforced; root-screenshot guard (#303 H9/H3) — docs.append-only-guard is status: superseded by docs.decision-lifecycle (see docs/decisions.md); relocated to archive/release-ci-governance.md (heading kept identical to the pre-split original so the lifecycle validator's relocation check matches it by heading). The bundled companion root-screenshot guard (H3) was split out into its own active record, below.

Records formerly in this file

Each record below moved to its own file under records/ (ersatztv#610); the rationale is unchanged. Resolve by key — that is the stable identity. A date-based pointer from another doc or an old issue comment should land here and then follow the link.

Reference in New Issue View Git Blame Copy Permalink