docs(v0.11): candidate-selection — pick G standalone, queue E for v0.12

Per R-NEW-75 candidate-selection after v0.10.0 shipped (PUBLISHED npm
`latest` 2026-05-22T21:24:43Z; tag `v0.10.0` at `c9eceba`; release-prep
`36d705d..c9eceba`; post-publish loop closed at `5a63a4d`). SDK re-probe:
`@mondaydotcomorg/api` still at 14.0.0 — 5th-consecutive stall (v0.6 →
v0.10) — so M39/M40/M41 (SDK 15.x → API `2026-04`) + M44/M45 (SDK 16.x →
API `2026-07`) stay DEFERRED. 5-dimension scoping against the
C/D/E/G + R-v0.10-NEW-4 backlog at this session:

- C cross-board `item move` value-overrides — slipped 4× on Monday's
  `ColumnMappingInput` no-value-slot constraint at API `2026-01`.
  Stays-filed at this session per the user's Q2 binding (not closed
  permanently; Monday could surface the value slot in a future API
  version).
- D resumable cross-board cursor — design-blocked on per-board
  cursor-lifetime under aggregation. Stays-filed.
- E profile-scoped argument defaults — only feature candidate with
  zero external dependency (no Monday wire, no SDK gate); has a
  prerequisite §13 carve-out Decision at pre-flight kickoff
  distinguishing aliases-as-stored-command-strings (still non-goal)
  from defaults-as-stored-flag-values (carve-out). **Queued for v0.12.**
- G `Item.description` read-side — addresses the v0.9-M52 surfaced
  gap (`ITEM_FIELDS_FRAGMENT` doesn't select `description`; every
  item-read verb returns items without descriptions). MEDIUM novelty
  (OBJECT type at API `2026-04`; `2026-01` availability is an open
  empirical probe at pre-flight). Same SDK-drift class as
  `hierarchy_type` / `views` — M52-graduated `match_query`
  selection-pin guard applies. **PICKED for v0.11.**
- R-v0.10-NEW-4 — fold inline this session (`085e999`).

User binding at the 2-question AskUserQuestion round-trip then
re-shaped the initial E+G bundle into a sequential split: v0.11 = G
alone (no shared subsystem with E; G has no prerequisite Decision +
closes the visible read gap immediately), v0.12 = E (config surface
+ §13 carve-out Decision). Tradeoff accepted: 2× release-prep
overhead for two focused minors. The 2026-05-22-at-M52-close
pair-with-M40 user binding BROKEN at this candidate-selection (G
ships standalone; M40 stays SDK-15.x-gated — the two surfaces are
independent transport paths sharing only the `Item.description`
data shape).

R-class status flips:
- R-v0.9-NEW-8 OPEN — paired-pending → PROMOTED to v0.11
  (canonical entry v0.9-plan §22; carry-forward v0.10-plan §22).
- R-v0.10-NEW-4 OPEN → RESOLVED 2026-05-22 at `085e999`
  (v0.10-plan §22).

CLAUDE.md "Next session" flipped to v0.11-G pre-flight contract
diff. No `docs/v0.11-plan.md` opens this session per the v0.10
precedent (`5d89754`) — plan-doc opens at the first pre-flight
contract diff commit of the milestone. Gates green: typecheck +
lint + test (4270 + 4 skipped); coverage 95.89% branches
(re-verified at the maxWorkers fold).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: Nick Webster

CLAUDE.md

@@ -188,22 +188,41 @@ humans are second-class. Built incrementally via Claude Code on top of
     HEAVY single-sourced one (`boardMetadataSchema` + `views`).
     Both correct per the runtime read; rule documents both valid
     choices.
-- **Next session:** **v0.10.x / v0.11 candidate-selection** per
-  R-NEW-75. ≥2 backlog candidates remain at v0.10 close: C cross-
-  board `item move` value-overrides; E profile-scoped argument
-  defaults; G `Item.description` read-side paired with v0.7-M40
-  reopen; D resumable cross-board cursor (design-blocked on
-  per-board cursor-lifetime under aggregation, cli-design §13).
-  Plus R-v0.10-NEW-4 (fold `--maxWorkers=2` into the
-  `test:coverage` npm script) as a work-of-opportunity candidate
-  — fold whenever `package.json` is next touched, or include in
-  a v0.10.x release-prep. **Re-probe `@mondaydotcomorg/api`** at
-  candidate-selection: if SDK 15.x publishes (baking `2026-04`),
-  M39/M40/M41 reopen and preempts the C/E/G backlog (M40 already
-  feature-confirmed on multi_level boards via the 2026-05-22
-  probe sweep — only the M39 SDK gate remains). If still 14.0.0
-  (6th-consecutive stall), 5th-consecutive pivot is the default
-  expectation across the C/E/G/D backlog. **Post-publish
+- **Next session:** **v0.11-G pre-flight contract diff.** v0.11
+  candidate-selection ran 2026-05-22 per R-NEW-75 over the
+  C/D/E/G + R-v0.10-NEW-4 backlog. SDK probe:
+  `@mondaydotcomorg/api@14.0.0` — **5th-consecutive stall**
+  (v0.6 → v0.10), so M39/M40/M41 (SDK 15.x → API `2026-04`) +
+  M44/M45 (SDK 16.x → API `2026-07`) stay DEFERRED. User picked
+  **G — `Item.description` read-side, ships standalone** (the
+  2026-05-22-at-M52-close pair-with-M40 user binding BROKEN at
+  this candidate-selection per the 2-question round-trip);
+  **E (profile-scoped argument defaults) queued for v0.12**; C
+  stays-filed (4 slips on Monday's `ColumnMappingInput` no-value-
+  slot at API `2026-01`); D stays design-blocked.
+  **R-v0.10-NEW-4 RESOLVED inline at `085e999`** —
+  `--maxWorkers=2` folded into the `test:coverage` script
+  (work-of-opportunity per the v0.10 post-publish refactor-audit
+  finding). **v0.11-G scope:** unblock the v0.9-M52-surfaced
+  read gap where `ITEM_FIELDS_FRAGMENT`
+  (`src/api/item-helpers.ts`) doesn't select `description`, so
+  every item-read verb
+  (`item get`/`list`/`find`/`search`/`subitems`/`history`)
+  returns items without descriptions. Pre-flight binding
+  decisions: shape (a) extend `ITEM_FIELDS_FRAGMENT` (universal
+  projection — heavier) vs (b) dedicated `monday item
+  get-description <iid>` verb (narrow projection — mirrors
+  M52's `board views` carve-out); plus the **open empirical
+  probe** for `Item.description` field availability at API
+  `2026-01` (the CLI pin — the 2026-05-22 dev-board sweep
+  confirmed OBJECT type at `2026-04` but didn't test `2026-01`
+  availability). Same SDK-drift class as
+  `hierarchy_type`/`views`; the M52-graduated `match_query`
+  selection-pin two-layer guard (cassette + RUN_LIVE_TESTS smoke
+  per `.claude/rules/testing.md`) applies. **No
+  `docs/v0.11-plan.md` opens this session** per the v0.10
+  precedent (`5d89754` — plan-doc opens at the first pre-flight
+  contract diff commit of the milestone). **Post-publish
   refactor-audit ran 2026-05-22** over `36d705d..177b40c`
   (recency window: release-prep cluster + post-publish flip) —
   process-only cluster (matching v0.9's precedent at `253233f`),

docs/v0.10-plan.md

@@ -679,11 +679,18 @@ pending the user):
 - **R-v0.9-NEW-5 — Board-projection schema fragmentation across 4
   schemas** (LOW). Trigger UNMET (M53 doesn't touch board schemas).
   **Status: OPEN.** Full entry: v0.9-plan §22.
-- **R-v0.9-NEW-8 — `Item.description` read-side, paired with
-  v0.7-M40 reopen** (MEDIUM, user-directed at v0.9-M52 close).
-  Trigger UNMET (M53 is the noun-descriptions lift, NOT `Item.
-  description`); stays paired with M40 reopen. **Status: OPEN.**
-  Full entry: v0.9-plan §22.
+- **R-v0.9-NEW-8 — `Item.description` read-side** (MEDIUM, user-
+  directed at v0.9-M52 close). **Status: PROMOTED to v0.11
+  2026-05-22** at the v0.11 candidate-selection session — the
+  original pair-with-M40 user binding (2026-05-22 at M52 close)
+  was BROKEN at this candidate-selection per the AskUserQuestion
+  round-trip (G ships standalone; M40 stays SDK-15.x-gated). The
+  read-side surface is independent of the M40 write mutation (no
+  atomicity envelope ties them — they share only the
+  `Item.description` data shape). Pre-flight contract diff opens
+  next session; (a)-vs-(b) shape Decision + `2026-01`
+  availability empirical probe close at pre-flight kickoff. Full
+  entry (status update + binding-break narrative): v0.9-plan §22.
 - **R-v0.9-NEW-9 / 10 / 11 / 12** — fixture-factory / helper-lift /
   fixture-leftover-detection / Codex `-xhigh` behaviour. All
   watch-items, all UNMET at M53. Full entries: v0.9-plan §22.
@@ -765,9 +772,17 @@ pending the user):
   `package.json` so the gate runs stably out-of-the-box. The
   underlying timing-race surface (R-v0.7-NEW-8) stays unaddressed
   by this lift — this only restores parity between the two test
-  invocations' stability properties. **Status: OPEN** (file at this
-  audit; close at any v0.10.x release-prep or earlier work-of-
-  opportunity touching `package.json`).
+  invocations' stability properties. **Status: RESOLVED 2026-05-22**
+  at `085e999` — folded inline at v0.11 candidate-selection as the
+  work-of-opportunity per the user's binding at the 2-question
+  round-trip (E + G bundle initially picked; subsequently re-shaped
+  to v0.11 = G alone, v0.12 = E, with R-v0.10-NEW-4 retained as the
+  inline fold). Re-verified at the fold: `npm run test:coverage`
+  with `--maxWorkers=2` produces 4270 + 4 skipped, branches 95.89%
+  (4489/4681), functions 98.97% (1354/1368) — same numbers as the
+  audit-time measurement. The underlying R-v0.7-NEW-8 SIGINT-mid-
+  cadence flake umbrella stays UNRESOLVED (this only restores
+  parity-on-touch between `npm test` + `npm run test:coverage`).
 
 - **R-v0.10-NEW-3 — Docstring mentions of 3-arg `ensureSubcommand`
   pattern surface in broader sweep** (data point, NOT drift).

docs/v0.9-plan.md

@@ -1236,13 +1236,24 @@ pending the user):
   Item.description IS feature-real on multi_level boards, so this
   is a real read gap, not academic).
 
-  **Trigger:** bundle with v0.7-M40 when SDK 15.x publishes (which
-  bakes `2026-04` natively + unblocks the M40 write mutation).
-  Both surfaces ship in the same release per user directive
-  2026-05-22 at M52 close. Cross-refs v0.7-plan §3 M40 +
-  `project_m40_findings_deferred` + `project_multilevel_dev_board_capabilities`.
-
-  **Status: OPEN — paired-pending.**
+  **Trigger:** ~~bundle with v0.7-M40 when SDK 15.x publishes~~
+  **PROMOTED to v0.11 standalone at the v0.11 candidate-selection
+  session 2026-05-22.** The user re-bound the original 2026-05-22-
+  at-M52-close pair-with-M40 directive at the candidate-selection
+  AskUserQuestion (single round-trip, 2 questions): G ships
+  standalone now; M40 stays SDK-15.x-gated. The two surfaces are
+  read vs write — independent transport paths sharing only the
+  underlying `Item.description` data shape, so no atomicity
+  envelope ties them. Cross-refs v0.7-plan §3 M40 +
+  `project_m40_findings_deferred` +
+  `project_multilevel_dev_board_capabilities`.
+
+  **Status: PROMOTED to v0.11 (M40-pair binding BROKEN
+  2026-05-22).** Pre-flight contract diff opens next session;
+  the (a)-vs-(b) shape Decision + the `2026-01` availability
+  empirical probe close at pre-flight kickoff per
+  `.claude/rules/workflow.md` "Read-side field-add" discipline
+  (graduated v0.9-M52).
 
 - **R-v0.9-NEW-9 — Shared `BoardMetadata` fixture factory** (code
   lift, watch-item). Filed at the M52 close refactor-audit. M52 IMPL