Guildhall 0.8.0
Guildhall 0.8.0 is about the two moments where agent work most often goes wobbly: the beginning, when a request is still too broad to build safely, and the ending, when the task looks done but Git still has opinions.
The release adds Pressure-Test Intake, Git Story Closure, cleaner task files, Commit Story messages, and clearer provider-default visibility.
What changed
- Pressure-Test Intake: every task carries a pressure-test requirement, and broad release or feature requests can route into a one-question-at-a-time intake. Guildhall keeps the target, domains, evidence, answers, assumptions, decisions, deferrals, and language-map candidates so the eventual spec has bones instead of vibes.
- New Request routing: requests are classified before work is created. A small task, question, settings change, practice proposal, repair ask, clarification, or pressure-test request can take the right lane. Multi-intent requests are split into reviewable actions.
- Request shape and component stacks: ambiguous asks such as "set this policy" can be recorded as spec-vs-implementation questions instead of becoming one accidental mega-task. Guildhall names the linked pieces, asks the scope question, and can keep the result as a parent feature with child tasks.
- Task sizing and split recommendations: shaped tasks get a size signal. Small work can proceed; large and epic work gets nudged toward linked child tasks so implementation and review stay human-sized.
- Buildable specs from messy asks: a completed intake can render domain coverage, assumptions, deferrals, and acceptance criteria. The useful promise is not that Guildhall knows everything. It is that missing things are named.
- Project Overview: the project shell now opens on an Overview that pulls together next action, work mix, health, blocked work, recent activity, and Git closure signals before you choose a deeper lane.
- Cleaner project notes: shared project state keeps the compact task story, while transcripts, worktree paths, gate output, review notes, Git snapshots, and bulky receipts stay in local history.
- Versioned project migrations:
guildhall migrate status|plan|applyshows which migrations a project needs, records applied work in./.guildhall/migrations.json, blocks runtimes that cannot safely read the old shape, and keeps prompt-required changes explicit so Git writes are never surprising. - 0.8.0 project cleanup migrations: older projects can move provider credentials to machine storage, split legacy
memory/state, clean up bulky task evidence, and installAGENTS.mdbridge instructions through the migration flow. - Done-task summaries: completed tasks can show a compact journey, decision, evidence, learning candidates, and transcript-retention status. Transcript remains available as source evidence, but it no longer has to be the first thing you read after work is done.
- Inspectable Journey evidence: changed files in Journey are real file entries, not directory guesses, and can be opened inline from the task drawer.
- Git Story Closure: project and task surfaces can show whether work is dirty, committed locally, missing an upstream, pushed, in an open PR, merged, local-only, deferred, conflicted, or unknown.
- Release-readiness Git blockers: dirty repos, local commits, no-upstream branches, pending PRs, skipped merges, stale task worktrees, and unknown Git inspection failures no longer get to hide behind a cheerful
done. - Policy-gated Git actions: Guildhall can inspect diffs, commit, push, open or show PRs, mark work local-only, and defer Git closure according to project policy. The default posture is ask-first.
- Auto-commit when the project asks for it: if the copied project policy says
commit: auto, completed dirty task work can be committed automatically. Projects can still opt out even when the global default is more automatic. - Commit Story messages: generated commit messages are concise, outcome-first, and free of AI attribution. Weak task titles fall back to changed-path context instead of becoming
WIPsoup. - Provider defaults on Projects Home: the home view shows the machine-default provider and active worker model group before you open a project, with a direct route to global Providers.
- Provider mismatch warnings: fallback and provider/model-family mismatch warnings stay visible until you fix the lane or accept the mismatch. Paid fallback stays opt-in.
Why it matters
The beginning of work needs enough pressure to become real. The ending needs enough honesty to stay real.
Pressure-Test Intake keeps work from depending on the worker guessing your taste, risk tolerance, and non-goals. Small tasks get proportional automatic pressure; broad asks get deeper questions. Git Story Closure keeps completed work from quietly ending as a dirty tree, lonely local commit, or "there is probably a PR somewhere" shrug.
Together, they make Guildhall more useful as a project room: better questions before work starts, smaller shared task files while work is moving, and better receipts before work is called closed.
The edges
Guildhall still does not take over your whole GitHub life. It does not force-push, rebase shared branches, resolve review threads, poll every GitHub check, or merge PRs for you by default.