T-RJ2Z-ensure-ready-bulk-reformat-legacy-touchpoint-tables
Status: closed/done · Impact: medium · Complexity: small
The v3 /sdlc:task-ensure-ready gate is table-only: ## Today and
## Files to touch must be markdown tables, and bulleted-legacy
shapes are a hard fail. Tasks authored and stamped
readiness_verified_at under an earlier (v2, bullets-allowed)
verifier still carry bulleted sections, so each one fails the gate the
moment /sdlc:task-work picks it up — forcing a detour through
/sdlc:task-define to reformat the two sections before any
implementation can start. This was hit on
2026-05-19-engine-review-running-tick-decision (in
github.com:sksizer/pumice), and every other already-verified task
with bulleted touchpoints will re-discover it individually. A bulk
migration that finds all readiness_verified_at tasks whose
Today/Files-to-touch parse as bulleted-legacy and reformats them to
v3 tables in one pass would close the gap once instead of N times.
From the originating post-mortem: “The task shipped at
readiness_verified_atunder an older (v2, bullets-allowed) readiness verifier, but the current v3 gate is table-only … task-work had to detour through/sdlc:task-defineto reformat both sections into v3 tables before it could proceed — a verifier-generation drift, not a real spec gap. A bulk migration that re-runs the v3 table check across all already-verified tasks and reformats bulleted Today/Files-to-touch sections in batch would stop every Phase-5 cleanup task from re-discovering this individually.”
TBD — receiver to fill before promoting from planning/draft.
Proposed
Section titled “Proposed”TBD — receiver to fill before promoting from planning/draft.
Approach
Section titled “Approach”TBD — receiver to fill before promoting from planning/draft.
Files to touch
Section titled “Files to touch”TBD — receiver to fill before promoting from planning/draft.
Acceptance criteria
Section titled “Acceptance criteria”TBD — receiver to fill before promoting from planning/draft.
Out of scope
Section titled “Out of scope”- none
Dependencies
Section titled “Dependencies”- none
Discovery context
Section titled “Discovery context”Spawned by /sdlc:cross-repo-task-pr on 2026-05-24 UTC from
2026-05-19-engine-review-running-tick-decision in
git@github.com:sksizer/pumice.git. Classification: Upstream-plugin.