This is the record of an abcd-managed repository

abcdBetav0.16.2 · 2026-11-06

Development record

The configuration chapter says abcd never configures RepoPrompt or writes its route keys; itd-6 has ahoy find RP's server config and write it into .abcd/config.json

issuewontfixminoriss-2610262040125215

The configuration chapter says abcd never configures RepoPrompt or writes its route keys; itd-6 has ahoy find RP's server config and write it into .abcd/config.json

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

  • End A: .abcd/development/brief/05-internals/03-configuration.md:339 — "abcd never starts, installs or configures RepoPrompt, and never writes either key."
  • End B: .abcd/development/intents/shipped/itd-6-rp-mcp-only-integration.md:43 — "notes it in .abcd/config.json → oracle.rp.mcp_config_path, and tests reachability"

03-configuration's reviewer-route section says abcd never starts, installs or configures RepoPrompt and never writes either key (oracle.review, oracle.rp). itd-6 has ahoy find the RP MCP server's configuration, write its path into .abcd/config.json as oracle.rp.mcp_config_path, test reachability and lock oracle.backend. These cannot both be true of abcd's setup.

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

Grounds

  • declined: Closed in the 2026-10-27 triage (dcn-2610271112330536): a later record already settles which end holds. The intent's header says the shipped route is the re-filed spc-2609211950427074 and that the earlier scope text belongs to a different lineage, so the configuration chapter describes what shipped.

Frontmatter

idiss-2610262040125215
typeissue
lifecyclewontfix
severityminor

References1

mentions2