Skip to content

feat: typed auto_groomable/branch_prefix at create; typed auto-groom abstain/rearm (change 0382) - #342

Merged
danielhanold merged 12 commits into
mainfrom
feat/changecreaterequest-typed-auto-groomable-branch-prefix-scalars
Sep 27, 2026
Merged

danielhanold merged 12 commits into
mainfrom
feat/changecreaterequest-typed-auto-groomable-branch-prefix-scalars

Conversation

@danielhanold

@danielhanold danielhanold commented Sep 27, 2026 •

Copy link
Copy Markdown
Owner

↩ Change 0382 — ChangeCreateRequest should accept typed auto_groomable / branch_prefix scalars

Summary

  • docket change create accepts typed auto_groomable (tri-state) and branch_prefix (normalized in Go by domain.NormalizeBranchPrefix; invalid values refused as invalid-branch_prefix).
  • docket change groom gains abstain and rearm outcomes that write the flag, the dated ## Auto-groom blocked entry (or remove it), and the board atomically.
  • docket-new-change, docket-auto-groom, docket-groom-next, and docket-convention use the typed ops instead of plain-git frontmatter edits.
  • Human-approved: docket-groom-next/SKILL.md word ceiling 1889 -> 1996.

Results: docs/results/2026-09-27-changecreaterequest-typed-auto-groomable-branch-prefix-scalars-results.md

Review

Rung: docket-review-deep (default standard, bumped one step for a >1500-line diff). 4 minor findings, 0 blocker, 0 important.

# Finding State
1 Board marker detection matched fenced headings; rearm did not fixed (529d7f3)
2 Non-boolean auto_groomable became an error-severity finding blocking publish/finalize fixed (529d7f3), now a warning
3 Abstain/rearm untested with a section following the blocked section fixed (6b24de3)
4 groom-next description / Step 5 omitted the re-arm exit fixed (6b24de3)

Build evidence

command: go run ./cmd/docket development test
result: green
head_sha: 603123b
ran_at: 2026-09-27T19:49:10Z

Docket-Plan-Path: docs/superpowers/plans/2026-09-27-0382-typed-auto-groomable-branch-prefix-and-abstain-rearm.md
…groomable is a warning (change 0382 review minors 1-2)

Review minor 1: the board's auto-groom-blocked cell (hasHeading) matched fenced
heading-shaped lines while change.groom rearm's section scanner skipped them, so a
fenced example could show 'needs you' with no typed op able to clear it. hasHeading
now skips fenced code for all presence markers, matching scanTopHeadings.

Review minor 2: a non-boolean auto_groomable raised an error-severity
field-malformed that would block pr.publish/finalize on previously valid records;
it is now a warning and the value stays unset.
…; groom-next documents the re-arm exit (change 0382, findings 3+4)
@danielhanold
danielhanold force-pushed the feat/changecreaterequest-typed-auto-groomable-branch-prefix-scalars branch from 19c22c9 to 603123b Compare September 27, 2026 19:49
@danielhanold
danielhanold merged commit 360f79f into main Sep 27, 2026
1 check failed
@danielhanold
danielhanold deleted the feat/changecreaterequest-typed-auto-groomable-branch-prefix-scalars branch September 27, 2026 19:50
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