Skip to content

fix: match self-nudge-loop steps to the popover and kanban-md (#16164) - #16208

Merged
bolichen97 merged 1 commit into
mainfrom
fix/self-nudge-scaffold-docs-16164
Oct 3, 2026
Merged

bolichen97 merged 1 commit into
mainfrom
fix/self-nudge-scaffold-docs-16164

Conversation

@cruisercohen

@cruisercohen cruisercohen commented Oct 2, 2026 •

Copy link
Copy Markdown
Contributor

Problem / Motivation

Goal: A user who follows the self-nudge-loop skill's generated LOOP.md fills in the inputs the Set a goal popover actually has, and a loop that follows the ready-to-paste nudge runs every kanban-md command without an unknown flag error.

skills/self-nudge-loop/scaffold.sh writes a LOOP.md that tells the user to fill "all four fields" of the Set a goal popover, the fourth a stop-sentinel path. The popover has three inputs. The nudge and SKILL.md also give kanban-md commands with flags kanban-md 0.37.0 rejects: edit --add-body (the flag is --append-body), pick --assignee, move <id> --status todo and handoff --notes.

Why it matters

A repo-checkout user arming a loop from the popover looks for an input that does not exist. A loop that follows the nudge hits unknown flag on its board steps every cycle, so it either spends tool calls finding the right flag or skips the claim and the progress record.

Not a goal

What changed (motivation → approach → change)

The skill text drifted from the two things it describes: the popover's inputs and kanban-md's CLI.

  • Popover step: lists the popover's three inputs by their English labels (Goal description, Seconds between nudges, Max cycles (0 = ∞)). It adds the issue's suggested pointer for the stop file the popover does not ask for: the service gives a popover-armed loop its own per-session stop file (authorize_and_add_nudge defaults a blank stop_sentinel_path, src/kiro_crew/autonudge_authz.py), and {{STOP_FILE}} in the goal text names it at fire time. The line also says the nudge's first check halts on the anchor's STOP file either way, and REST arming makes that file the service's. The stop-methods table row for touch $STOP_PATH now says the service honors that file only for a loop armed over REST with it.
  • kanban-md commands, in both the nudge and SKILL.md: pick --claim … --status todo, positional move <id> todo, edit <id> --claim … --append-body, handoff <id> --claim … --note … --release. pick and handoff require a claimant, and kanban-md refuses an edit of a claimed card that does not name the same claimant, so the claimant is one name per loop ("loop-$PROJECT" in the generated nudge, quoted so a project name with a space stays one argument; loop-<project> in the templates), not one per cycle. Because pick always takes a new card, the claim step first lists the cards that name holds (list --claimed-by) and resumes one. Every way a held card leaves the loop releases its claim, so the resume step never returns it again: --release on handoff when it is done, and edit <id> --block "<reason>" --release when the loop walks away from it as blocked (kanban-md refuses --claim with --release on edit, and pick skips blocked cards). skills/goal-loop/SKILL.md summarizes the same cycle (goal-loop runs this scaffold), so its claim step gets the same resume-or-pick command, its move-to-Review step names the same handoff … --release, its blocked-card rule names the same edit … --block … --release, and its prerequisites now say the commands were written for and checked against kanban-md 0.37.0 and list the subcommands the cycle uses, without changing which version the install lines fetch.

Backwards compatibility

Compatible: only skill prose and a new test change. No code path, API or stored format is touched.

Removes nothing: the stop-sentinel bullet named a popover input that never existed, and every replaced kanban-md flag is one kanban-md 0.37.0 already rejects.

Tests

test/test_self_nudge_loop_skill.py (new) reads scaffold.sh, SKILL.md and goal-loop's SKILL.md as text, so it needs neither bash nor kanban-md:

  • test_popover_steps_name_exactly_the_popover_inputs: the popover bullets equal the dashboard's English labels from website/src/i18n/locales, with no extra field.
  • test_every_kanban_md_command_is_one_kanban_md_accepts (per file, including goal-loop's SKILL.md): every kanban-md command uses a known subcommand and its 0.37.0 flags, gives a task ID where one is required, and names a claim where kanban-md requires one.
  • test_a_command_continued_on_the_next_line_is_scanned_whole: a command split with a trailing \ is checked as one, so the flags on scaffold.sh's two-line kanban-md init are checked too.
  • test_claimant_is_stable_across_commands_and_cycles (per file): every --claim in the file names the same claimant with no per-cycle token, a list --claimed-by for that claimant comes before any new pick, every handoff passes --release, and the file has an edit … --block … --release path for a blocked held card.
  • test_edit_release_and_claim_are_mutually_exclusive: an edit that passes --release must not pass --claim (kanban-md refuses the pair), while any other edit, and handoff, still need the claimant.
  • test_scaffold_claimants_are_double_quoted: every --claim and --claimed-by value in scaffold.sh is double-quoted, since $PROJECT expands into the generated text.

The popover test and all per-file command and claimant tests fail on the files before this change and pass after it.

Manual verification

  • bash -n skills/self-nudge-loop/scaffold.sh passes. scaffold.sh --with-board into a scratch anchor writes LOOP.md, README.md and a board initialized by the real kanban-md 0.37.0.
  • Every rewritten command was run against the kanban-md v0.37.0 linux_amd64 release binary (checksum verified) on a scratch board, and each exits 0: list --status todo --json, pick --claim loop-1 --status todo, show 1, edit 1 --claim loop-1 --append-body …, move 2 todo, handoff 1 --claim loop-1 --note …. Each old form exits 1 with unknown flag (--assignee, --status on move, --add-body, --notes). Bare pick exits 1 with required flag(s) "claim" not set, handoff without a claim exits 1 with claim name is required, and an edit of a claimed card without --claim is refused.
  • Three loop cycles replayed on the real binary from the generated LOOP.md (--project demo): cycle 1 finds no held card and picks card 1 as loop-demo; cycle 2 finds card 1 held, edits it, and hands it off with --release; cycle 3 finds nothing held and picks card 2. Every command exits 0, and card 1 ends in review with no claim. With the old per-cycle claimant (loop-1 then loop-2), cycle 2's edit of card 1 exits 1.
  • Blocked held card, same binary: edit 1 --block "waiting" --release exits 0 and leaves list --claimed-by loop-demo empty, and the next pick takes card 2. edit 1 --claim loop-demo --release exits 1 with cannot use --claim and --release together.
  • Spaced project name: scaffold.sh --project "my proj"; the generated step-4 pick, run through bash -c on the real binary, claims the card as loop-my proj. Unquoted, the same pick claims it as loop-my and the handoff exits 1 (accepts 1 arg(s), received 2).
kanban-md 0.37.0 --help for the rewritten subcommands (captured from the release binary; global flags and -h omitted)
$ kanban-md list --help   (flags excerpt)
Usage:
  kanban-md list [flags]
Flags:
      --claimed-by string   filter by claimant
      --status strings      filter by status (comma-separated)
      --unclaimed           show only unclaimed or expired-claim tasks
$ kanban-md pick --help
Usage:
  kanban-md pick [flags]
Flags:
      --claim string    agent name to claim as (required)
      --move string     also move the picked task to this status
      --no-body         suppress full task details after pick
      --status string   status column to pick from (default: all non-terminal)
      --tags strings    filter by tags (comma-separated, OR logic)
$ kanban-md move --help
Usage:
  kanban-md move ID[,ID,...] [STATUS] [flags]
Flags:
      --claim string   claim task for an agent during move
      --next           move to next status
      --prev           move to previous status
$ kanban-md edit --help   (flags excerpt)
Usage:
  kanban-md edit ID[,ID,...] [flags]
Flags:
  -a, --append-body string   append text to task body
      --assignee string      new assignee
      --body string          new body text (replaces entire body)
      --claim string         claim task for an agent
      --status string        new status
$ kanban-md handoff --help
Usage:
  kanban-md handoff ID [flags]
Flags:
      --block string   mark task as blocked with reason
      --claim string   claim task for an agent (required)
      --note string    handoff note to append to body
      --release        release claim after handoff
  -t, --timestamp      prefix a timestamp line to the note

Related Issues

Fixes #16164

Pattern harvest

Rule candidate: agents-md
Pattern: skill prose that quotes another surface's UI labels or a third-party CLI's flags drifts from it silently; pin such text with a test that reads both sides.

Checklist

  • At most two commits (one is the norm), with a Conventional Commits title (feat|fix|docs|style|refactor|perf|test|chore|ci|build|revert: ...)
  • Existing tests pass and new tests added for new functionality
  • Self-review completed; code follows project style guidelines
  • Documentation updated (if applicable)
  • No secrets, credentials, or internal references in the diff

@cruisercohen
cruisercohen requested a review from a team as a code owner October 2, 2026 17:19
@github-actions github-actions Bot added the readiness: checking Automated validation is still running label Oct 2, 2026
@github-actions

github-actions Bot commented Oct 2, 2026 •

Copy link
Copy Markdown
Contributor

Design Review (Fable 5) — ✅ PASS

Design-level review of 4f0912a6405209303f1a0ed85bd98102160474da — updated in place on each push. A BLOCK verdict blocks PR readiness; PASS/CONCERNS are advisory.

Design-Verdict: PASS

Install lines still fetch kanban-md @latest while every command is checked only against 0.37.0 — a newer release can re-open the unknown flag failure.

Suggestions

  • Pin the install lines (go install …@v0.37.0, tagged release URL) to the version the commands and the test's flag table were verified against; the current prose warning makes the user debug the drift this PR exists to prevent.

[DESIGN-REVIEWED] 4f0912a

Description read

[DESCRIPTION-READ] 10da996e8038976055e1fd467046c985b67558eccdb30183862988bb7500192d

That sha256 names everything this verdict read: the PR description, plus the 1 evidence file(s) the workflow collected from it and handed this review. It covers that evidence because the media strip replaces every attachment URL with the same placeholder, so an edit swapping one attachment for another would leave the description's captured text identical while what this review judged changed. Recompute it with .github/scripts/pr-description-capture.sh over the same inputs; if it differs, the description or that evidence changed after this verdict was formed and any finding drawn from either is unproven.

@github-actions

github-actions Bot commented Oct 2, 2026 •

Copy link
Copy Markdown
Contributor

First Principles Review (Fable 5) — ✅ PASS

Premise-level review of 4f0912a6405209303f1a0ed85bd98102160474da — why this exists and whether the shipped surface is the smallest honest version. Updated in place on each push. A BLOCK verdict blocks PR readiness; PASS/CONCERNS are advisory.

First-Principles-Verdict: PASS

Verify the new test's kanban-md 0.37.0 flag tables against the real binary once — CI never runs kanban-md, so the pin is only as true as the author's capture.

What this change ships

Inventory (8 items) — 8 justified

Intent: FIX — make the generated LOOP.md name the popover's real inputs and make every kanban-md command in the nudge and skill docs actually run on kanban-md 0.37.0 (issue #16164; the new tests fail on base).

  1. LOOP.md popover step lists the three real inputs by their English labels, dropping the nonexistent stop-sentinel field — justified
  2. Popover step now explains where the stop file comes from ({{STOP_FILE}}, REST arming) — justified
  3. Stop-methods table says touch $STOP_PATH is service-honored only for REST-armed loops — justified
  4. Every kanban-md command rewritten to flags 0.37.0 accepts (--claim, --append-body, positional move <id> todo, --note) — justified
  5. Loop now resumes its held card (list --claimed-by) with one stable claimant per loop, instead of a fresh per-cycle pick — justified
  6. Handoff and blocked-card walk-away now release the claim so the resume scan stops returning the card — justified
  7. goal-loop prerequisites pin kanban-md 0.37.0, replacing "check verbs rather than a version" — justified
  8. New text-only test pins the skill files to the popover's i18n labels and 0.37.0's flag tables — justified

Checked: autonudge_authz.py:820,1122 confirms the blank stop_sentinel_path default; en.json carries exactly the three labels asserted; grep kanban-md finds 5 files — the three edited, the new test, and skills/goal-loop/scaffold.sh, whose only command mention (kanban-md create, no flags) is not broken, so zero unfixed siblings. Items 7–8 fix at cause level: nothing previously pinned the skill text to the CLI it describes.

[FIRST-PRINCIPLES-REVIEWED] 4f0912a

Description read

[DESCRIPTION-READ] 664794ae251b713420637d9fef17aabc4957f3db2dc414642a1bc1580e2f2fed

That sha256 names the PR description this verdict read. Recompute it with .github/scripts/pr-description-capture.sh; if it differs, the description changed after this verdict was formed and any finding drawn from the description is unproven.

@github-actions

github-actions Bot commented Oct 2, 2026 •

Copy link
Copy Markdown
Contributor

GPT 5.6 Review — ✅ no blocking findings

GPT 5.6 completed its review of 4f0912a6405209303f1a0ed85bd98102160474da and found no blocking issues.

This comment is updated in place on each push.

Review details

No findings.
[GPT-REVIEWED] 4f0912a

False positive or not applicable? A repository writer can comment:
/ai-review override gpt 4f0912a6405209303f1a0ed85bd98102160474da: <one-sentence reason>

@github-actions

github-actions Bot commented Oct 2, 2026 •

Copy link
Copy Markdown
Contributor

Opus 5 Review — ✅ no blocking findings

Reviewed 4f0912a6405209303f1a0ed85bd98102160474da — this comment is updated in place on each push.

Review details

No findings.

[OPUS-REVIEWED] 4f0912a

Verdict parsed from the review's SHA-scoped output markers for commit 4f0912a6405209303f1a0ed85bd98102160474da.

False positive or not applicable? A repository writer can comment:
/ai-review override fable 4f0912a6405209303f1a0ed85bd98102160474da: <one-sentence reason>

@cruisercohen
cruisercohen force-pushed the fix/self-nudge-scaffold-docs-16164 branch from 0f38d1c to ba69337 Compare October 2, 2026 17:41
@github-actions github-actions Bot added readiness: action required A blocking check or review needs attention and removed readiness: checking Automated validation is still running labels Oct 2, 2026
@cruisercohen
cruisercohen force-pushed the fix/self-nudge-scaffold-docs-16164 branch from ba69337 to 156aed5 Compare October 2, 2026 18:00
@github-actions github-actions Bot added readiness: checking Automated validation is still running and removed readiness: action required A blocking check or review needs attention labels Oct 2, 2026
@cruisercohen

cruisercohen commented Oct 2, 2026 •

Copy link
Copy Markdown
Contributor Author
  • Pin the kanban-md install instruction to v0.37.0 (span=166a1b3821e3)

Outcome: declined for this PR, not deferred as a defect.
Pinning go install …@latest / the brew tap would change which kanban-md every goal-loop user installs, which is new install policy outside this PR's goal (make the skill's commands match the kanban-md they run against today).
The drift risk is already covered on the repo side: the test's flag table names 0.37.0 as the version it was checked against and says moving to a newer kanban-md means re-reading its help and updating the table, and every command was run against the 0.37.0 release binary (see Manual verification).
If kanban-md renames a flag again, the right fix is the same text change plus a table update, which this test makes visible.

@cruisercohen

Copy link
Copy Markdown
Contributor Author

First Principles headline on 156aed5 asked to confirm the test's _SUBCOMMAND_FLAGS table against the real kanban-md 0.37.0 binary, beyond the four pasted --help excerpts. Checked: I parsed kanban-md <sub> --help from the v0.37.0 linux_amd64 release binary (checksum verified) for every subcommand in the table. Every flag the table lists for create, edit, handoff, init, list, move, pick and show exists on the binary, and _GLOBAL_FLAGS equals the binary's global flag set exactly.

@github-actions github-actions Bot added readiness: action required A blocking check or review needs attention readiness: checking Automated validation is still running and removed readiness: checking Automated validation is still running readiness: action required A blocking check or review needs attention labels Oct 2, 2026
@cruisercohen
cruisercohen force-pushed the fix/self-nudge-scaffold-docs-16164 branch from 156aed5 to a243244 Compare October 2, 2026 19:10
@cruisercohen

Copy link
Copy Markdown
Contributor Author
  • Pin the kanban-md install lines to v0.37.0, or state the supported version next to them (span=43efe394c837)

Outcome: declined for this PR, same as the earlier install-pin suggestion on this lane.
Pinning the install changes which kanban-md every goal-loop user installs, and that install policy is outside this PR's goal: the skill's commands should match the kanban-md they run against today.
The repo side already records the version: the test's flag table names 0.37.0 as the version it was checked against and says a newer kanban-md means re-reading its help and updating the table. Every rewritten command was also run against the 0.37.0 release binary (see Manual verification).
A version pin or support statement for the install lines is a separate maintainer decision about the goal-loop skill's install policy.

@cruisercohen

Copy link
Copy Markdown
Contributor Author
  • goal-loop step 5 never releases the claim the new resume-first scan finds (span=be931fab1be4)

Outcome: fixed in db8b527.
goal-loop's step 5 now moves the card to Review with kanban-md --dir <BOARD> handoff <id> --claim loop-<project> --note "<summary>" --release, the same releasing handoff the self-nudge-loop nudge uses, so a card in Review no longer comes back from list --claimed-by.
The test now expects a handoff command in goal-loop's SKILL.md, so the existing every-handoff-releases check applies to it; removing --release from that line fails the test.
Checked on the kanban-md 0.37.0 binary: after that handoff, list --claimed-by loop-demo --json returns [].

@github-actions github-actions Bot added readiness: checking Automated validation is still running and removed readiness: action required A blocking check or review needs attention labels Oct 2, 2026
@cruisercohen

Copy link
Copy Markdown
Contributor Author
  • Add an optional check that diffs the flag table against a real kanban-md binary's --help (span=fa3e2c678edc)

Outcome: declined for this PR.
CI has no kanban-md binary, so an automated check would either be skipped everywhere it runs or add a download step the test suite does not have today; a manual script would be a new surface beyond this fix.
The comparison was done once by hand for this PR: every flag the table lists for create, edit, handoff, init, list, move, pick and show exists on the 0.37.0 release binary, and the global flags match exactly (see the earlier PR comment). The table's own comment says a newer kanban-md means re-reading --help and updating it.

@cruisercohen

Copy link
Copy Markdown
Contributor Author
  • Item 5: the list --claimed-by resume scan rides along beyond the flag fix (span=c35ade44b916)

Outcome: kept; it is the smallest change that closes a defect this PR's own flag fix introduced.
Making the nudge name a claimant (kanban-md 0.37.0 requires one on pick and handoff) first produced a per-cycle claimant, which GPT 5.6's discovery pass flagged as BLOCKING: a card claimed in cycle N cannot be edited in cycle N+1 (reproduced on the 0.37.0 binary, edit exits 1).
A stable claimant fixes that, but pick always takes a new unclaimed card, so without a held-card scan each cycle would strand the card it already holds. The scan is one list --claimed-by call before pick, verified over three cycles on the real binary.

@cruisercohen

Copy link
Copy Markdown
Contributor Author
  • Item 7: --release on handoff exists only to serve item 5's scan (span=f3b33330767e)

Outcome: kept, for the reason the item states.
handoff keeps the claim by default (checked on the 0.37.0 binary), so with the resume scan a card already in Review would come back every cycle and the loop would never pick new work. --release is the one flag that prevents that; it is covered by the test that every handoff in the three files releases the claim.

@github-actions github-actions Bot added readiness: action required A blocking check or review needs attention and removed readiness: checking Automated validation is still running labels Oct 2, 2026
@cruisercohen
cruisercohen force-pushed the fix/self-nudge-scaffold-docs-16164 branch from db8b527 to 82799e6 Compare October 2, 2026 20:02
@cruisercohen

Copy link
Copy Markdown
Contributor Author
  • A held card abandoned as blocked is never released, so the resume scan returns it every cycle (span=be931fab1be4)

Outcome: fixed in 82799e6, with a different command than suggested.
The suggested edit <id> --claim loop-<project> --release fails on kanban-md 0.37.0 ("cannot use --claim and --release together"). edit <id> --block "<reason>" --release without --claim exits 0, marks the card blocked and clears the claim, and pick then skips it. The self-nudge-loop nudge, its template and minimal-ops block, and goal-loop's blocked-card rule now name that command, and the test now treats --claim with edit --release as an error.
Every way a held card leaves the loop now releases it: progress keeps the claim on purpose (edit --claim … --append-body); done uses handoff --claim … --note … --release; blocked uses edit --block … --release. A claim left alone also expires (kanban-md reports about an hour), after which the card is unclaimed and pick can take it again, so no path strands a card.
Replayed on the 0.37.0 binary: pick card 1; block and release card 1; list --claimed-by is empty; next pick takes card 2.

@cruisercohen

Copy link
Copy Markdown
Contributor Author
  • goal-loop's install lines fetch the latest kanban-md while the commands are a 0.37.0 snapshot (span=0ab16d442014)

Outcome: fixed in 82799e6 by the second clears-when option.
goal-loop's prerequisites now say the loop's commands were written for and checked against kanban-md 0.37.0, list the six subcommands the cycle uses, and say to compare that subcommand's --help with the command if a newer kanban-md rejects one with unknown flag.
The install lines themselves are unchanged: which version they fetch is install policy outside this PR's goal.

@github-actions github-actions Bot added readiness: checking Automated validation is still running and removed readiness: action required A blocking check or review needs attention labels Oct 2, 2026
@cruisercohen

Copy link
Copy Markdown
Contributor Author
  • Pin the install lines to the version the commands and test table were checked against (span=09778dd637bf)

Outcome: declined for this PR; same decision as the earlier install-pin items on this lane.
Which kanban-md version goal-loop's install lines fetch is install policy for every goal-loop user, outside this PR's goal of making the skill's commands match the kanban-md they run against today.
This head states the targeted version (0.37.0) and the subcommands the cycle uses next to the install block, which is the clears-when option the earlier Watch item offered; pinning the install itself is left to a maintainer decision.

The LOOP.md that scaffold.sh writes told the user to fill four fields in
the Set a goal popover, the fourth a stop-sentinel path the popover does
not have. It now names the popover's three inputs by their labels and
says where the stop file comes from instead: the service gives a
popover-armed loop its own stop file, which {{STOP_FILE}} in the goal
text names; the nudge's first check also halts on the anchor's STOP
file, and REST arming makes that file the service's.

The nudge and SKILL.md's board commands used kanban-md flags kanban-md
0.37.0 rejects with "unknown flag": pick --assignee, move --status,
edit --add-body and handoff --notes. They now use pick --claim with
--status todo, a positional status for move, edit <id> --append-body
and handoff --note, each naming the claim: kanban-md requires one for
pick and handoff, and refuses an edit of a claimed card without it.
The claimant is one name per loop ("loop-$PROJECT" in the generated
nudge, quoted so a project name with a space stays one argument), each cycle resumes the card that name already holds before
picking a new one, handoff passes --release, and a held card the loop
walks away from as blocked is released with edit --block --release
(kanban-md refuses --claim with --release on edit). A card claimed in
one cycle stays workable in the next, and neither a handed-off nor a
blocked card is resumed. goal-loop's SKILL.md, which summarizes the
same cycle, gets the same claim, handoff and blocked-card commands;
its prerequisites now say the commands target kanban-md 0.37.0 and
which subcommands the cycle uses.

A new test reads the three files as text: the popover bullets must equal
the dashboard's English labels; every kanban-md command, including
one continued over two lines, must use a known subcommand and flags,
give a task ID where one is required, and name the claim where
kanban-md requires it (but never with edit --release); and each file
must use a single claimant (quoted in scaffold.sh), look for held work
before picking, and release the claim on handoff and on a blocked card.

Closes #16164
@cruisercohen
cruisercohen force-pushed the fix/self-nudge-scaffold-docs-16164 branch from 82799e6 to 4f0912a Compare October 2, 2026 20:21
@cruisercohen

Copy link
Copy Markdown
Contributor Author
  • A spaced --project splits the unquoted loop-$PROJECT claimant (span=33c910afc084)

Outcome: fixed in 4f0912a.
scaffold.sh now writes --claimed-by "loop-$PROJECT" and --claim "loop-$PROJECT" in all four commands this PR added, and test_scaffold_claimants_are_double_quoted checks that every claimant in the scaffold stays quoted.
Checked on the kanban-md 0.37.0 binary with --project "my proj": unquoted, the pick claimed the card as loop-my and the handoff exited 1 (accepts 1 arg(s), received 2); quoted, the generated pick claims it as loop-my proj.

@cruisercohen

Copy link
Copy Markdown
Contributor Author
  • Pin the install lines to the version the commands and flag table were verified against (span=15fce963b526)

Outcome: declined for this PR; same decision as the earlier install-pin suggestions on this lane.
Which kanban-md version goal-loop's install lines fetch is install policy for every goal-loop user, outside this PR's goal. The prerequisites state the targeted version (0.37.0) and the subcommands the cycle uses next to the install block; pinning the install itself is left to a maintainer decision.

@github-actions github-actions Bot added readiness: passed Eligible automated validation passed for the current revision and removed readiness: checking Automated validation is still running labels Oct 2, 2026

@iamwhatever iamwhatever left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed: fixes both parts of #16164. The popover steps now name its three real inputs from the en locale and explain the {{STOP_FILE}} token, and every kanban-md command uses 0.37.0 flags (--append-body, pick --claim, positional move todo, handoff --note ... --release). The claim handling is needed once a claim name is required. Text-only tests fail on the old files. Caution for a maintainer: the flag table is pinned to 0.37.0 while the install lines fetch the latest release.

@iamwhatever
iamwhatever added this pull request to the merge queue Oct 2, 2026
@bolichen97
bolichen97 enabled auto-merge (squash) October 3, 2026 01:30
@bolichen97
bolichen97 merged commit d0dc81c into main Oct 3, 2026
97 checks passed
@bolichen97
bolichen97 deleted the fix/self-nudge-scaffold-docs-16164 branch October 3, 2026 01:32
@github-actions github-actions Bot removed the readiness: passed Eligible automated validation passed for the current revision label Oct 3, 2026
@bolichen97 bolichen97 mentioned this pull request Oct 6, 2026
5 tasks done
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

3 participants