This is the record of an abcd-managed repository

abcdBetav0.16.2 · 2026-11-06

Development record

itd-67 picks the bump tier by phase-completion detection and keeps the version in plugin.json; itd-73 derives it from shipped intents' impact on an unversioned tree

issuewontfixmajoriss-2610262045379282

itd-67 picks the bump tier by phase-completion detection and keeps the version in plugin.json; itd-73 derives it from shipped intents' impact on an unversioned tree

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

  • End A: .abcd/development/intents/shipped/itd-67-installable-versioned-plugin.md:47 — "auto-selects the bump tier (patch/minor/major) via the brief §4 phase-completion detection"
  • End B: .abcd/development/intents/shipped/itd-73-derived-versioning.md:30 — "take the highest-severity impact, and compute the next SemVer"

itd-67 has launch ship choose patch, minor or major through the brief's phase-completion detection, write the version into plugin.json as the single source of the installed version, and keep --version as an override. itd-73 derives the version from the highest impact among intents shipped since the last release, says the working tree stays unversioned and that no one types a version. The two shipped records give incompatible rules for how a release's number is chosen and where it lives.

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

Grounds

  • declined: Closed in the 2026-10-27 triage (dcn-2610271112330536): a later record already settles which end holds. Both intents shipped in the same release and the closed spec for itd-67 explicitly picks itd-73's rule; code follows itd-73.

Frontmatter

idiss-2610262045379282
typeissue
lifecyclewontfix
severitymajor

References2

mentions1