This is the record of an abcd-managed repository

abcdBetav0.16.2 · 2026-11-06

Development record

itd-6 says abcd makes no direct LLM API calls, only RP over MCP; 01-ahoy has delegating verbs send steps straight to a configured provider

issuewontfixminoriss-2610262033202441

itd-6 says abcd makes no direct LLM API calls, only RP over MCP; 01-ahoy has delegating verbs send steps straight to a configured provider

A premise contradiction (severity minor) found by the cross-document consistency pass.

  • End A: .abcd/development/intents/shipped/itd-6-rp-mcp-only-integration.md:38 — "abcd calls RP via mcp__RepoPrompt__* tools. Period. No subprocess spawning of claude -p, no direct LLM API calls"
  • End B: .abcd/development/brief/04-surfaces/01-ahoy.md:204 — "A delegating verb whose agent's oracle.roles entry points at a configured provider sends the step there itself"

itd-6 makes RepoPrompt over MCP abcd's single integration point, with no direct LLM API calls, and puts direct OpenAI, Google and Anthropic integrations out of scope. 01-ahoy describes an OpenAI-compatible provider adapter: a delegating verb whose oracle.roles entry points at a configured provider sends the step there itself, after the provider setup has checked the provider with a real call. abcd cannot both never call an LLM API directly and send steps to a provider it calls.

Evidence: .abcd/work/reviews/2026-10-26-consistency/00-summary.md, finding 392.

Grounds

  • declined: Closed in the 2026-10-27 triage (dcn-2610271112330536): a later record already settles which end holds. The no-direct-API line is itd-6's original framing, superseded by its own re-file note (RP is one opt-in reviewer route) and by adr-25; the provider adapter exists in code.

Frontmatter

idiss-2610262033202441
typeissue
lifecyclewontfix
severityminor

References1

mentions2