feat: Guildhouse MCP server + multi-agent governed dev pipeline
MCP server connecting Claude Code to the Guildhouse ecosystem.
Tools (23):
Forgejo: repos, files, branches, PRs, CI status
Chronicle: events, epochs, verify, emit
GSAP proxy: request_ac, check_operation, get_posture, delegate
Capstone: agents, tenants
Tasks: list, get, create, update_status, submit_for_review, submit_review
Multi-agent topology:
Lead Agent — plans work, delegates, reviews proposals
Worker Agents — implement in parallel, submit PRs with confidence
Reviewer Agent — QA's worker output, submits review confidence
Confidence Gate — auto-merge/flag/propose/reject based on combined score
Confidence thresholds (configurable):
>= 85: auto-merge (no human needed)
>= 70: flag-merge (merged, flagged for post-review)
>= 50: proposal (Tyler reviews)
< 50: reject (worker revises)
Reviewer can override: 'reject' always rejects, 'request_changes'
caps at propose.
Task definitions (TOML) with phased prompts, success criteria,
and delegation scopes.
Every tool call emits Chronicle MCP_TOOL_CALL (0x3020).
Every gate decision emits Chronicle events (0x4010-0x4013).
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Tyler King
dffa821c38