Guildhall 0.12.0

Guildhall 0.12.0 gives projects one durable state model and gives users one honest answer about the release or bounded scope they are looking at.

What changed

• Unified project state: project structure, release scope, task hierarchy, execution state, proof, readiness, and closure now resolve through one shared state boundary.
• Bounded project loading: fleet cards and project surfaces use compact saved projections instead of assembling full task queues, transcripts, threads, proofs, Git history, and debug records on every read.
• Honest release lifecycle: releases remain optional. A selected release has its own included and deferred work, can ship without pulling later work into scope, and stays shipped after later-scope selection or restart.
• Cross-surface agreement: Overview, Map, Work, Activity, Release, Thread, task detail, APIs, and the new guildhall status command read the same release summary and counts.
• Narrative Harness proof: the headless drafting and evaluation release was taken through a complete bounded cycle: 15 included items done, 24 later items deferred, no selected-scope blockers, and a durable shipped result.
• Compact process history: operational process output is retained through bounded summaries rather than becoming permanent project-state payload.

Why it matters

The old project view made users reconstruct progress from scattered pages and ephemeral agent activity. 0.12.0 makes the release boundary visible: what is included, what is deferred, what is finished, and what the next action is. A project can keep growing; a named release is the thing that can become ready and ship.

Proof

The release acceptance audit passed 42 installed checks across API, CLI, desktop, mobile, restart, release lifecycle, and cross-surface agreement. The isolated source suite passed 381 test files and 5,296 tests, with only designed skips and todo tests remaining.