This is the record of an abcd-managed repository

abcdBetav0.16.2 · 2026-11-06

Development record

itd-7 packs the RepoPrompt workspace by running dev-sync, which writes into the repo, as a disembark pre-pack step 'already in brief'; the configuration chapter says disembark never writes to the source repository

issuewontfixmajoriss-2610262039347531

itd-7 packs the RepoPrompt workspace by running dev-sync, which writes into the repo, as a disembark pre-pack step 'already in brief'; the configuration chapter says disembark never writes to the source repository

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

  • End A: .abcd/development/intents/planned/itd-7-rp-workspace-portability.md:38 — "dev-sync runs as a pre-pack step (already in brief)"
  • End B: .abcd/development/brief/05-internals/03-configuration.md:505 — "disembark never writes to the source repository."

itd-7 relies on dev-sync running as a pre-pack step of /abcd:disembark and writing .abcd/rp/workspace.json into the repository, and it says the step is already in the brief. The configuration chapter makes it load-bearing that disembark never writes to the source repository. It stages dev-sync in full, and it records as an unsettled open question whether a writing sweep can be part of disembark at all. Both cannot hold: the intent's pack mechanism needs a write that the brief rules out.

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

Grounds

  • declined: Closed in the 2026-10-27 triage (dcn-2610271112330536) as a duplicate of iss-2610262031532231. Same contradiction: disembark never writes to the source repository (03-configuration.md), against itd-7's pre-pack write; its dev-sync clause is the other record's.

Frontmatter

idiss-2610262039347531
typeissue
lifecyclewontfix
severitymajor

References1

mentions2