2 commits

Author	SHA1	Message	Date
Eric Garcia	daaaea5c82	feat(realm): Implement RFC 0001 cross-repo coordination and RFC 0002 Phase 1 MCP tools ... RFC 0001 - Cross-Repo Coordination with Realms: - Daemon architecture with HTTP server on localhost:7865 - SQLite persistence for sessions, realms, notifications - Realm service with git-based storage and caching - CLI commands: realm status/sync/check/worktree/pr/admin - Session coordination for multi-repo work RFC 0002 Phase 1 - Realm MCP Integration: - realm_status: Get realm overview (repos, domains, contracts) - realm_check: Validate contracts/bindings with errors/warnings - contract_get: Get contract details with bindings - Context detection from .blue/config.yaml - 98% expert panel alignment via 12-expert dialogue Also includes: - CLI documentation in docs/cli/ - Spike for Forgejo tunnelless access - 86 tests passing Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>	2026-01-24 07:14:35 -05:00
Eric Garcia	7e9a466329	docs: RFC 0001 - Cross-repo coordination with realms ... Add comprehensive design for cross-repo coordination: - Spike: Initial problem exploration - Dialogue: 12-expert, 6-round alignment session - RFC: Full implementation spec Key design decisions: - Realm = git repo (auditable, no new infrastructure) - Index → Realm → Domain → Repo hierarchy - Export/import contracts with semver - Pull-based sync with GitHub issue notifications - Different orgs can coordinate without shared write access 7-week MVP: init, join, export, import, sync, check, status integration Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>	2026-01-24 05:01:08 -05:00