trilha-spec v0.4.0

trilha-spec v0.4.0

Install: go install github.com/emersonjoe/trilha-spec/cmd/trilha-spec@v0.4.0, or download the binary for your platform below and check it against sha256sums.txt.

0.4.0 — protocol 0.4 (spec 016)

What the trilha-cloud plan drawn from dev-3.0 needed on the wire (trilha-cloud/docs/PLANO-DEV3.md,
item DV-00): agent state from hooks, an attention badge, a run that stops to ask (needs_input)
and the answer that resumes its session, task memory between runs (overview and quoted notes),
diff counts, review and hunt runs with anchored findings and no code, human review comments and
the agent's replies, variant groups and report artifacts. One breaking change: the status
needs_input.

Full roadmap: https://github.com/emersonjoe/trilha-spec/blob/v0.4.0/docs/roadmap.md

trilha-spec v0.3.1

trilha-spec v0.3.1

Install: go install github.com/emersonjoe/trilha-spec/cmd/trilha-spec@v0.3.1, or download the binary for your platform below and check it against sha256sums.txt.

0.3.1 — 2026-10-25

The first release with binaries (linux and macOS, amd64 and arm64, with sha256sums.txt); the
protocol is still 0.3, no field or transition changed.

• Failure taxonomy (spec 014, #15): §10 documents a recommended vocabulary for
  failure_class and error_code (environment_missing_tool, test_failure, lint_failure,
  timeout, provider_transient, agent_error), not yet a closed enum.
• doctor warns spec-tasks-done when an approved spec has every task done (spec 015).
• One source of truth (ADR 003): .trilha/ is authoritative in trilha-spec, trilha-runner
  and trilha-cloud; Spec Kit folders are frozen history.
• CI formats the whole module and checks the execution contract against trilha-runner.

0.3.0

These came from planning a public-sector delivery programme that spans four repositories — the
product app, the framework, the runner and the control plane — and has to be auditable by the
buyer at every milestone. Each one is a spec under specs/ and
a done task with evidence.

Task	Gap	Why it mattered
TASK-016 · spec 009 · #10	When the source of scope is an external document — a tender's requirement list, a law, a KPI in a contract — nothing links tasks to it.	"Which requirements are covered, by which task, with what evidence" was a spreadsheet kept by hand, and it is the question a public buyer asks at every milestone.
TASK-018 · spec 010 · #12	The protocol had statuses and dependencies but no calendar: no way to say "this task belongs to M2, due 2027-04-30".	A contract with paid milestones reported its physical-financial schedule outside the protocol.
TASK-014 · spec 011 · #8	Quality is measured with numbers, and the only way to record one was a check whose exit code hid it.	The reviewer could not see the value, nothing could trend it, and a control plane could not gate on it.
TASK-015 · spec 012 · #9	review → done was one person's decision, and nothing distinguished "someone typed a note" from "this person, in this role, attests this — signed".	Public-sector delivery ends with named human acceptance, sometimes by a committee.
TASK-017 · spec 013 · #11	depends_on was local only, so a programme spanning repositories wrote its real dependencies as prose.	next offered work that could not start, and nobody could draw the graph.

Full roadmap: https://github.com/emersonjoe/trilha-spec/blob/v0.3.1/docs/roadmap.md