Guildhall app

The app has two useful scales: the /projects service home for scanning registered projects, and the project shell where setup, tasks, live runs, reviewer calls, and release readiness actually play out.

Use it for the everyday loop:

1. Open the service home or jump straight into a project shell.
2. Pick or configure a provider.
3. Add tasks.
4. Start and stop the orchestrator.
5. Inspect transcripts, reviews, gates, and provenance.
6. Resolve escalations and tune settings.

The app is still transparent: the shared project contract lands in ./guildhall.yaml, shared Guildhall metadata can live in checked-in ./.guildhall/*.yaml files, project memory lands in ./memory/*, and local/private checkout overrides stay in ./.guildhall/config.yaml. Machine-scoped state such as the project registry, provider credentials, and default provider choice live under ~/.guildhall/.

Pages

• Setup wizard — first-run onboarding.
• Projects home — Projects & Workspaces, service-level work mix, attention, running-now, and project launcher.
• Project view — main per-project shell.
• Task drawer — task detail pane.
• Providers page — credential management.

If the UI does something weird, the receipts are usually sitting in plain files that can be inspected directly.