Skip to content

docs: draft-PR merge safety + npm 0.8.0 roadmap note#1250

Merged
hartsock merged 2 commits into
mainfrom
feat/draft-safety-npm-roadmap
Jul 17, 2026
Merged

docs: draft-PR merge safety + npm 0.8.0 roadmap note#1250
hartsock merged 2 commits into
mainfrom
feat/draft-safety-npm-roadmap

Conversation

@hartsock

Copy link
Copy Markdown
Member

What this PR does

Two small docs/governance changes prompted by a near-miss where a 'merge on green' sweep almost promoted a deliberately-drafted PR (#1222):

  1. gh bundled skill — adds a hard rule: draft PRs are a do-NOT-merge, do-NOT-un-draft signal. A blanket 'merge on green' / 'merge my PRs' never authorizes merging or gh pr ready-ing a draft; the sweep must skip drafts and say so. Includes the isDraft check.
  2. ROADMAP — records the npm installer as Step 11.4 with an explicit release decision: the first npm publish ships with 0.8.0, and PR feat(npm): newt-agent npm installer — @gilamonster shim (newt + newt-mcp-server) [draft] #1222 is kept in draft as the hold mechanism. Links feat(npm): newt-agent npm installer — @gilamonster shim (newt + newt-mcp-server) [draft] #1222 so the intent survives even if branch feat/npm-shim is closed/deleted by accident.

Test plan

  • Docs-only; no code touched. gh skill frontmatter unchanged; ROADMAP renders (new Step 11.4 under Phase 11).
  • pr-pre-review privacy scan clean.

Out of scope

🤖 Generated with Claude Code

hartsock and others added 2 commits July 17, 2026 11:22
WHAT: Add an explicit rule to the gh bundled skill's Pull Requests
section — a draft PR is a 'do NOT merge yet' signal; never merge it and
never mark it ready (gh pr ready) unless a human names that PR by number.
A blanket 'merge on green' / 'merge my PRs' instruction must skip drafts
and say so, never promote them. Includes the isDraft check commands.

WHY: A 'merge on green' sweep nearly promoted a deliberately-drafted PR
(#1222, held for a release gate). Draft is the mechanism authors use to
keep exactly that from happening; the skill must encode that drafts are
untouchable so the accident can't recur.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
 held in draft)

WHAT: Record the npm installer (@gilamonster shim, PR #1222) as roadmap
Step 11.4 with an explicit release decision: the first npm publish ships
with 0.8.0, not before. Note that PR #1222 is kept in draft AS the hold
mechanism and links it so the intent survives even if branch
feat/npm-shim is closed/deleted by accident.

WHY: The 'hold npm until 0.8.0' intent was not written down anywhere —
it lived only as the draft state of a PR, which evaporates if the branch
is closed. The roadmap is the durable home for a release-gating decision.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@hartsock hartsock added the risk:low Low-risk change (scoped, tested, no CI/build/hook changes) label Jul 17, 2026
@hartsock
hartsock merged commit e58d27a into main Jul 17, 2026
14 checks passed
@hartsock
hartsock deleted the feat/draft-safety-npm-roadmap branch July 17, 2026 15:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

risk:low Low-risk change (scoped, tested, no CI/build/hook changes)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant