timothy
fba5233caf
PR Gates / CI image pin matches docker/ci (pull_request) Successful in 11s
PR Gates / Docs update reminder (pull_request) Successful in 16s
PR Gates / decisions lifecycle (pull_request) Failing after 23s
Build ErsatzTV Image / Formatting (changed .cs conform to .editorconfig) (pull_request) Successful in 1m17s
Build ErsatzTV Image / API docs in sync (OpenAPI + endpoint index) (pull_request) Successful in 1m29s
Build ErsatzTV Image / Build & test (.NET) (pull_request) Successful in 8m5s
Build ErsatzTV Image / EF migration integrity (SQLite + MySql) (pull_request) Successful in 16m5s
Build ErsatzTV Image / Functional E2E (curl + UI contracts) (pull_request) Successful in 17m6s
Build ErsatzTV Image / Build & push image (amd64) (pull_request) Has been skipped
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
38 lines
3.0 KiB
Markdown
38 lines
3.0 KiB
Markdown
---
|
|
key: docs.queue-state-gitea-tracker
|
|
title: 2026-07-11 — Queue state lives in the pinned Gitea tracker (#237), not in the handoff file
|
|
status: superseded
|
|
since: '2026-07-11'
|
|
supersedes: none
|
|
superseded-by: startup.parallel-orientation@2026-07-21
|
|
rule: '(superseded) Volatile session/queue state lives in pinned Gitea tracker issue #237 (goal + arc in the body, append-only session-comment log, in-progress/review labels), not in a wholesale-rewritten handoff file; the handoff file keeps only the static kickoff prompt and append-only lore.'
|
|
signals: 'last-writer-wins race, claim/`in-progress` label, triage verdict · paths: `docs/handoffs/chicorytv-issue-queue.md` · issues: #237, #520'
|
|
mechanics: superseded by `scripts/select-queue.sh` (ersatztv#520); see `docs/decisions.md` → `startup.parallel-orientation`
|
|
---
|
|
|
|
With multiple sessions/agents working the repo in parallel, the old protocol — every session
|
|
wholesale-rewrites `docs/handoffs/chicorytv-issue-queue.md` on main (session state + queue +
|
|
next-session prompt) — became a last-writer-wins race. New protocol: **volatile queue state
|
|
moved to Gitea**, which is concurrency-safe by construction. Pinned tracker issue **#237**
|
|
holds the goal + ordered arc in its body (edited rarely, only on arc changes, re-read before
|
|
edit) and an append-only session-comment log (fixed template: Closed / Filed / Triage /
|
|
Arc change / Recommended next). Milestone `Blazor removal (#91 phase b)` + the `review` and
|
|
`in-progress` labels are the machine-queryable view. Sessions **claim** an issue before working
|
|
it (`in-progress` label + claim comment; the tiny read→claim race window is accepted, later
|
|
claimant backs off; stale claims — no commits/comments ~48h — may be taken over with a comment).
|
|
Every new issue gets an explicit end-of-session triage verdict — gate-blocker (milestone + arc
|
|
slot) or backlog (label only) — so review findings adjust the queue only through that step and
|
|
the arc doesn't drift. The handoff file keeps only the **static kickoff prompt** and the
|
|
**append-only Lessons lore** (per-session prompts are gone; task context lives in issue bodies).
|
|
|
|
**Why superseded (#520, 2026-07-21):** the arc completed and #237 closed (2026-07-13); a closed
|
|
tracker cannot serve as live queue state, and continuing to read it as such was a live regression
|
|
risk (an agent skimming an old comment or this very record could re-treat #237's prose as current).
|
|
`scripts/select-queue.sh` (2026-07-19) already replaced the mechanical parts of this rule with a
|
|
deterministic, live-Gitea-only query — this record's job was really "queue state lives in Gitea,
|
|
not in the handoff file," and that half is still true; what's superseded is the *specific store*
|
|
(#237's body/comments) now that maintenance/backlog mode has no arc to narrate. See
|
|
`startup.parallel-orientation` for the replacement: two concurrent session-start tracks
|
|
(orientation via the docs/decisions catalog + `docs/README.md` map, and selection via the script),
|
|
with #237 reduced to a single archival breadcrumb.
|