Guildhall 0.5.1

Summary

Guildhall 0.5.1 is a cleanup release after the 0.5.0 service-over-projects pivot.

The goal is to make the public surface easier to understand:

• the browser UI remains the primary product path
• the CLI is reduced to service, project registration, config, and headless run operations
• docs now walk a new user through one project, first tasks, existing projects, and many-project operation before dropping into deeper reference material

What changed

Smaller CLI surface

Removed the old task-mutation commands from the shipped CLI:

• guildhall intake
• guildhall approve-spec
• guildhall resume
• guildhall meta-intake
• guildhall approve-meta-intake

Task creation, shaping, approval, and setup now belong in the web UI. The CLI is still useful for starting the service, opening the UI, registering initialized projects, inspecting config, and running Guildhall headlessly for automation.

Reworked docs journey

The docs now lead with task-oriented walkthroughs instead of sending new users straight into subsystem detail:

• quick start
• new project walkthrough
• existing project walkthrough
• first task set
• managing multiple projects

The deeper guides, CLI reference, HTTP reference, and subsystem pages are still available, but they are no longer the first thing a new user has to understand.

Route and setup documentation cleanup

The setup, task drawer, and project settings docs now describe the project scoped UI paths and API shape used by the current service runtime. Project settings calls in the app also route through the project-aware fetch helper so settings changes stay tied to the active project context.

Supported claim

For 0.5.1, the honest supported claim is:

Guildhall has a clearer first-run story and a smaller operator CLI, while preserving the 0.5.0 local service over projects release path.

Still not the claim

This release still does not claim broad unattended completion for every task shape. That remains the work of the next autonomy and planning improvements.