Repository navigation
chore(hold): delete the legacy hold labels - #546
Conversation
Quest-Claim: bbb98b1c236305a8
Only quest:active and quest:kix hold a PR now. quest:iterate, quest:ready, quest:merge, and other quest:* labels hold nothing, and a token naming kix's hold is refused rather than swapped for quest:active. Co-Authored-By: Claude Haiku 5.5 <noreply@anthropic.com>
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 41 minutes. View limit details
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. |
kixelated
left a comment
There was a problem hiding this comment.
Automated review by review (OpenAI)
Reviewed head 2991a38 against base 1c3cf6a.
No actionable findings. The two-label policy is shared by CLI and Worker consumers, and acquisition refuses a token naming kix's hold before making label writes. The named rind and rust2 Quest pins both contain #326, matching the deleted quest's remaining prerequisite. Direction: the narrower hold policy and removal of the legacy token swap fit the stated goal; no revision suggested.
Verification: GitHub-only static review of the changed files, hold callers, tests and relevant commit history. No tests or live GitHub label races were executed. quest context and quest guide were read from their base-revision sources rather than run.
(Written by review (OpenAI))

Summary
Finishes
quest/m2/legacy-labels.md, which this PR deletes along with its link inquest/m2/README.md.isHoldLabelnow counts onlyquest:activeandquest:kix.LEGACY_IGNOREDis gone.quest:iterate,quest:ready,quest:merge, and any otherquest:*label hold nothing, soiterate,ready,release,merge --land,status, and the land watcher no longer refuse or hold on them.KIX_LABELmoves intosrc/core/hold.tsand is exported fromquest/core. The Worker imports it instead of defining its own copy.quest iterate <token>refuses a token that names kix's hold instead of removing it. The swap of a token-named label forquest:activeexisted only for older quest versions' labels, so it is removed rather than left to reach kix's hold.quest iterate --helpdrop the notes on older labels, and the OWNERSHIP text namesquest:activeorquest:kix.Waiting item cleared
The
Waitingitem (every gated repository pins a quest release that includes #326) is verified and dropped. Checked 2026-11-07: rind'sflake.nixpins99eb7f25and rust2's pinsa3789c7b. GitHub's compare shows both contain #326's merge commitba0cf190(behind_by: 0). quest, moq and moq.pro were already past it.Public API and wire impact
quest/coreexportsKIX_LABEL.isHoldLabelaccepts two labels instead of everyquest:*label exceptquest:merge.quest:iterate,quest:ready,quest:merge, or a customquest:*label is no longer held or refused by it.quest:kixis the same string.Choices made without asking
quest:activeandquest:kix. The Goal says so, and the Plan's "recommend only the two" is taken as the decision. The alternative, keeping everyquest:*label exceptquest:merge, contradicts the Goal.quest:activehold is kix's, so keeping the swap would let a token remove kix's hold. Refusing is simpler and safer.KIX_LABELin core. One definition for the CLI and the Worker, instead of two.quest/m2/legacy-labels.mdand its line inquest/m2/README.md.Validation
just install,just fix,just check: exit 0.quest check --base origin/main: 81 documents ok.just test: exit 0. Root vitest 30 files, 1100 passed, 6 skipped. Worker 21 files, 539 passed.quest:ready) is refused; a token naming kix's hold is refused and writes nothing.Models
Size: XS
Implementer: Claude Code, claude-haiku-5-5, high effort
Review
Rewritten by
quest reviewafter each round.01a1b767-5ab6-7090-aad5-7ce25412915c, round 1The specified diff consistently limits holds to quest:active and quest:kix and prevents acquisition from taking over kix's hold; no actionable regressions were found, though tests were not run in the read-only environment.