This is the record of an abcd-managed repository

abcdBetav0.16.2 · 2026-11-06

Development record

itd-7 has disembark write the RepoPrompt workspace file into the repository; the glossary defines disembark as reading the source repository without writing to it

issuewontfixmajoriss-2610262041227792

itd-7 has disembark write the RepoPrompt workspace file into the repository; the glossary defines disembark as reading the source repository without writing to it

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

  • End A: .abcd/development/intents/planned/itd-7-rp-workspace-portability.md:20 — "When dev-sync runs (and as part of /abcd:disembark), abcd reads the project's RepoPrompt workspace definition from ~/Library/Application Support/RepoPrompt/Workspaces/ and writes it into .abcd/rp/workspace.json in the repo."
  • End B: .abcd/development/brief/glossary/core/disembark.md:4 — "reads a source repository without writing to it"

itd-7 has abcd write .abcd/rp/workspace.json into the repository "as part of /abcd:disembark", with dev-sync run as a pre-pack step. The canonical glossary entry defines disembark as packing that reads a source repository without writing to it, which is the read-only guarantee the lifeboat surface rests on. A disembark run cannot both write a file into the source tree and leave it unwritten, so itd-7 cannot be built as written without breaking that guarantee.

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

Grounds

  • declined: Closed in the 2026-10-27 triage (dcn-2610271112330536) as a duplicate of iss-2610262031532231. Same End A (itd-7 line 20); the glossary defines disembark as reading the source without writing to it.

Frontmatter

idiss-2610262041227792
typeissue
lifecyclewontfix
severitymajor

References1

mentions2