Skip to content

check-ticket: say how to clear "outside touches" after ticket set - #220

Merged
hhff merged 1 commit into
mainfrom
check-pr-log-hint
Nov 14, 2026
Merged

hhff merged 1 commit into
mainfrom
check-pr-log-hint

Conversation

@hhff

@hhff hhff commented Nov 14, 2026

Copy link
Copy Markdown
Member

Why

A supervisor lesson on a cloud box (stacks, candidate k-20261113-074439233) holds for any project. check-pr and merge read tickets from main's landed log. After ticket set widens a ticket's touches, the forge still sees the old touches, and the PR fails changes files outside touches until log-sync and merge --chore log land the change. That happened on two tickets (stacks-117, stacks-213). #196 added the hint only for a ticket that was added (has no ticket).

What

  • check-ticket: the "outside touches" failure ends with the same hint: land the log first and check again.
  • supervisor.md, Merging: covers ticket set (touches, done-whens) as well as ticket add.
  • test/fixtures/g1/{check-ticket,merge-dry-run}.txt: the goldens carry the new wording.

Tested

  • node --test test/components.test.mjs (the g1 goldens): 7/7 pass.

🤖 Generated with Claude Code

#196 named the fix for a ticket added since the log last landed. The
same holds for a ticket the supervisor changed with ticket set (touches,
done-whens): the forge checks it as main's log has it, so widened
touches fail "changes files outside touches" until log-sync and
merge --chore log land the change. A supervisor recorded this twice
(stacks-117, stacks-213). The error now says so, and supervisor.md's
Merging bullet covers ticket set as well as ticket add.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@hhff

hhff commented Nov 14, 2026

Copy link
Copy Markdown
Member Author

Reviewed: the hint text and the doc line match the forge reading only main's landed log, and the g1 goldens are updated. No authority change, and CI passes 9 of 9. Merging.

@hhff
hhff merged commit 026cb86 into main Nov 14, 2026
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant