Repository navigation
Move the Carried-Surface Cluster Off Decision - #1468
Conversation
The cluster asks for a maintainer decision that has been made, so a session reading the backlog selects it under the wrong rule. Measure rather than ready, because the cluster's own deliverable line and its only remaining sub-bullet both state a measurement, and its open question is answered by that count rather than before it. The decision, its evidence, and the work it leaves are recorded on #1321 and #1464, and restating any of that here is what five review rounds found fault with, so none of it is restated. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Advanced Run ID: Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
🟢 Approval recommended
The change is a low-risk, internally consistent one-word backlog state correction with no functional impact.
Pull request overview
This PR updates the backlog metadata for the "Reducing the Carried Surface Further" work cluster in TODO.md, moving its State from decision to measure to reflect that the next step is evidence-gathering rather than a maintainer decision.
Changes:
- Change the "Reducing the Carried Surface Further" cluster state from
decisiontomeasure.
File summaries
| File | Description |
|---|---|
| TODO.md | Updates the cluster state to match the documented selection workflow and the cluster's remaining measurement-oriented work. |
Review details
- Files reviewed: 1/1 changed files
- Comments generated: 0
- Review effort level: Lite
💡 Configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
…g, and the Release-Trigger Retirement (#1489) Promotes thirteen merged pull requests from `develop` to `main`. ## What this promotes - **#1486** State the `host-tools.json` carry rule and stop the empty-overlay warning. `spec/files.json` now requires the declaration unconditionally, and `host_gate.py` no longer warns on an empty one. - **#1484** Fan the validator's pytest leg out over a `python-versions` input, so a caller with more than one interpreter no longer silently loses its other legs to a pinned 3.13, with an entry guard that refuses a value `fromJson` would otherwise admit. - **#1476** Retire the publish-on-merge release trigger, which `spec/files.json` applied to an interface contract whose task has no publish-on-merge path. - **#1479** Ship the release caller snippet and retire the not-yet-released claim. - **#1474** Exclude `node_modules` from markdownlint and Docker lint discovery at any depth. - **#1468** Move the carried-surface cluster off decision, recording the measurements and what stays unmeasured on the issues that hold them. - **#1498** Correct the release-caller snippet's publish-on-merge claim, raised by CodeRabbit against this promotion and fixed on its own branch, since a promotion PR's head is `develop`. - **#1494** Settle the markdown lint exclusion seam as a nested config. - **#1492** Check declared deployment environments and fix the carried-payload rule. - **#1501** Move the session handoff to a chain of labeled issues. Two of its units are verbatim fidelity, `AGENTS.md` "Session Scope" and `GOVERNANCE.md` "Communicating with the User", so every fleet repo picks them up on its next resync. - **#1505** Refuse a bare handoff link rather than reading it as no successor, answering a finding raised against this promotion. - **#1504** Reject a deployment environment name or branch carrying surrounding whitespace, answering two more. - **#1506** Encode an environment name before it becomes a path segment, delete a branch that cannot fire, and dedupe a registry name by case, answering two more and declining one on a reproduction. ## Closing references A `develop`-targeted pull request registers no closing reference, so the issues those pull requests settled close with this promotion. #1470 is the one that needs a word. Two of its seven acceptance items are not met as literally written, and the maintainer's decision to close it here anyway, with the basis for both, is recorded on the issue itself. Closes #1483 Closes #1473 Closes #1487 Closes #1482 Closes #1475 Closes #1470 ## Left open deliberately - **#1499**, **#1500** follow-ups #1501 filed rather than fixed. - **#1503** the validator-looser-than-its-consumer class, filed from findings on this promotion and deliberately not closed by it. Five instances recorded, and the fix is a design decision rather than a check. - **#1497** the Docker delta list never says to remove the `push:` block. - **#1472** the fleet-level pin call, deliberately not pre-empted by #1479. - **#1321**, **#1464** carry #1468's decision record and remain in their own scope. ## Verification `origin/main..origin/develop` merges clean, no end-of-line conflict. Each promoted pull request ran the fleet gate set on its own branch before merging; this promotion adds no content of its own. 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_01817rckKywjfoaEV5WF9TKs
What this changes
One word. The
Reducing the Carried Surface Furthercluster inTODO.mdmoves from**State** \decision`toState `measure``.Why
The cluster asked for a maintainer decision that has been made, so a session reading the backlog
selects it under the wrong rule from "How to Select the Next Item".
measurerather thanreadybecause the cluster's own deliverable line and its only remaining sub-bullet both state a
measurement, and its lone
Open, whetherAUDIT.mdmoves, is answered by that count rather thanbefore it. That matches how the file's other three
measureclusters are labelled.Why it is only one word
The decision, its measurements, and what is still unmeasured are recorded on #1321 and #1464. A
fuller record was written into this cluster and then reverted. Five adversarial review rounds over
it raised roughly 66 findings, every one on the restated text and none on anything pre-existing,
because restating a decision that is already filed duplicates it into a file whose stated purpose is
work not yet filed. The state was the only thing this file actually had wrong.
Carried over rather than fixed here
The review noted that this cluster's
Costclause names only edits, where the file's other threemeasureclusters lead theirCostwith the count and sequence the edit after it. It is athree-of-three convention rather than a stated rule, the measurement is still stated on the cluster's
own deliverable line and sub-bullet, and the
Costline was deliberately left untouched, so it isreported here rather than changed.
Two things about #1321 itself, relevant to anyone following the pointer:
tree. The selection keeps that tree and retires four documents instead. A note now sits at the top
of that issue's body saying so.
AUDIT.md. The other three aretracked in P2 (decision): Carry Only the Fleet Bootstrap Verbatim, and Reach Everything Else From the Hub #1321's own scope rather than in the backlog.
Verification
prose_lint.py,markdownlint-cli2,spec/validate.py,spec/audit.py --selftest,spec/workflow_reuse.py --selftest,gh-write-guard.py --selftest, and the fullunittestsuiteat 1168 passed.
canonical_review.py checkreports no carried canonical unit changed. Alocal_review.pyreceipt covers this content.