Initial release: MCP server enforcing Worker-Reviewer loop

Diligence prevents AI agents from shipping quick fixes that break things
by enforcing a research-propose-verify loop before any code changes.

Key features:
- Worker sub-agent researches and proposes with file:line citations
- Reviewer sub-agent independently verifies claims by searching codebase
- Iterates until approved (max 5 rounds)
- Loads project-specific context from .claude/CODEBASE_CONTEXT.md
- State persisted across sessions

Validated on production codebase: caught architectural mistake (broker
subscriptions on client-side code) that naive agent would have shipped.
This commit is contained in:
2026-01-22 06:22:59 +01:00
commit bd178fcaf0
23 changed files with 4001 additions and 0 deletions

21
test/scenarios/index.json Normal file
View File

@@ -0,0 +1,21 @@
{
"scenarios": [
{
"id": "blocking-voice",
"file": "blocking-voice.json",
"difficulty": "medium",
"tags": ["blocking", "voice", "broker-events"]
},
{
"id": "permission-cache",
"file": "permission-cache.json",
"difficulty": "medium",
"tags": ["cache", "permissions", "broker-events"]
}
],
"metadata": {
"version": "1.0.0",
"fixture_path": "../fixture",
"description": "Test scenarios for diligence MCP server"
}
}