Development record
itd-88 calls the packer `disembark <repo> to <dest>`; the platform page calls it `disembark pack <source-repo> <dest>`
issuewontfixnitpickiss-2610262032172837
itd-88 calls the packer disembark <repo> to <dest>; the platform page calls it disembark pack <source-repo> <dest>
A naming conflict (severity nitpick) found by the cross-document consistency pass.
- End A:
.abcd/development/intents/shipped/itd-88-lifeboat-coverage-experiment.md:41— "The packer (disembark <repo> to <dest>), embark, and the round-trip" - End B:
.abcd/development/brief/02-constraints/01-platform.md:21— "disembark pack <source-repo> <dest>. There is no in-tree lifeboat home"
itd-88 refers to the packer as disembark <repo> to <dest>. 01-platform gives the lifeboat path as disembark pack <source-repo> <dest>: a pack sub-verb with no to keyword. The record holds two invocation shapes for one operation.
Evidence: .abcd/work/reviews/2026-10-26-consistency/00-summary.md, finding 248.
Grounds
Frontmatter
| id | iss-2610262032172837 |
|---|---|
| type | issue |
| lifecycle | wontfix |
| severity | nitpick |
.abcd/work/issues/wontfix/iss-2610262032172837-itd-88-calls-the-packer-disembark-repo.md
open on GitHub ↗ · commit history ↗
References1
- itd-88Know What a Repo Can and Cannot Tell You — Before You Trust the Lifeboatrelated
mentions1
- dcn-26102711123305362026-10-27 — The product thinker accepted on 2026-10-27 the triage of the 1301 records the 2026-10-26 consistency pass filed. The duplicates, the records a later record already settles, the ones that are no contradiction and the one already fixed are closed with each reader's reason. Every other record gets its fix as its remedy, the rulings' accepted answers included, so a drain can take it. The 45 major records left open are deferred past v0.15.1, because the brief's single-home rewrite rewrites or removes most of the passages they quote. The person ruled the major rulings one at a time; the minor rulings take their recommended answers.