Add the implementation-ready task contract and typed-shape enforcement
Status: closed/done · Impact: high · Complexity: large
The base task contract is a presence-floor; the implementation-ready bar wants
typed body shapes. Add a TaskReadyContract that enforces the implementation-ready
shapes — typed Today / Files-to-touch tables and checkbox acceptance criteria —
and wire the readiness tooling to enforce those shapes instead of only presence.
Acceptance criteria
Section titled “Acceptance criteria”- A
TaskReadyContractenforces typed Today / Files-to-touch tables and checkbox-style acceptance criteria perimplementation-ready.md. -
gap-reportandensure-readyenforce the typed shapes (e.g. column-missing, non-checkbox AC findings). - Contract definitions are de-duplicated via a shared
TASK_BODYso the base and ready contracts do not drift. -
bunx tsc --noEmitis clean and the readiness gate suites pass.
Out of scope
Section titled “Out of scope”- Migrating
parse-touchpoints/resolve-touchpointsrow consumption — that is the tree-based consumption follow-on (partial by design here).