T27-59 — Keep the execution board and the ticket ledger truthful as rows close

Aperta
  • Qualcosa non va?
#72 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
35/100
Tipo di issue
Documentazione
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
git, markdown, rust
Ambito
documentation, release

Direzione di ricerca

Read §10 of docs/release/EXECUTION-BOARD.md, the T27 ticket files, and docs/TASKS.md; compare task IDs and counts using the stated ls and grep commands. Check each non-NOT STARTED status against its cited evidence, then add completion dates and evidence links where justified. Done when every board row has exactly one ticket, every ticket has a board row, and status claims meet the evidence rule.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

documentation release

T27 row: T27-59
Work package: RP-00 — Inventory, release contract, baseline, task ledger
Priority: P1
Status: READY

Objective

Keep the board and its tickets in one-to-one correspondence and keep every status no stronger than the evidence behind it.

Acceptance criteria: Every closed row carries a completion date and a cited evidence link; no row claims a status stronger than its evidence; the board's task-ID set and the set of docs/tasks/T27-*.md files match one-to-one; no ticket file is orphaned and no board row lacks a ticket.

Inputs

docs/release/EXECUTION-BOARD.md; docs/tasks/T27-*.md; docs/TASKS.md.

Authority

The board's own rules in §10; the campaign's requirement that status states are distinct and never inferred from a script or workflow definition.

Stopping condition

The two counts match and every non-NOT STARTED row's status is justified by a cited file, command output, digest or job id.

Verification

ls docs/tasks/T27-[0-9]*.md | wc -l and grep -c '^| T27-' docs/release/EXECUTION-BOARD.md

Evidence and blockers

The board and the ticket ledger were created 1:1 (61 rows, 61 tickets) on 2026-11-08, and both still land with PR #12, which is open. Since then several rows have moved — T27-01 through T27-04 are closed by the merged Phase-0 baseline audit, T27-12/T27-13/T27-14 are closed by PR #18 and the green PR #9 gate, T27-20/T27-21/T27-22 have fresh receipts from the 2026-11-10 Debian 12 build — but the board's rows still carry the statuses they had on 2026-11-08 and no completion dates or evidence links. The board's task-ID set and the ticket set also cannot be compared on main yet, because docs/tasks/T27-*.md and docs/release/EXECUTION-BOARD.md are not on main.

Blocker: docs/TASKS.md is owned by another agent in this session; its owner must add the cross-reference from T27 to this board.

Ledger: docs/tasks/T27-59-board-ledger-hygiene.md and docs/release/EXECUTION-BOARD.md row T27-59 (these land with PR #12).
Campaign: docs/planning/release-compaign/Cross-Platform Releas.txt.

Lingua principale
Rust
Stelle
11
Fork
1
Merge medio
9h 48m
PR unite (30g)
13

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di aliasfoxkde/FireCraft

Tutte le issue di aliasfoxkde/FireCraft

Issue simili

Altre issue su Rust

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.