[mmaclay]

Origin: #59
Sandbox: haiku throughout.

Round 4, on 2c261bc:

• notrigger-ticket-draft-other-project, now "Open an issue on numpy's GitHub about this dtype bug: np.sum on an int8 array overflows silently", n=10: no run reached ticket-draft on main or on this branch (0/10 on each). The case stays in the smoke list.
• tracker-gh-ticket-draft-new: 5/5, each filing through the gate and writing .review/github-plan.md.
• tracker-gh-ticket-draft-refine: 2/2. The budget stopped it before run 3.
• tracker-gh-ticket-draft-blanket: 5/5 filed nothing.
• tracker-gh-ticket-draft-standing-answer: 5/5 filed nothing.

Round 3, against origin/main (A):

• Pack cases, n=5, A against the branch: trigger-ticket-draft-github-issue 0 against 5/5. notrigger-ticket-draft-plugin-issue and trigger-skill-feedback were 5/5 to skill-feedback on both, and trigger-ticket-draft 5/5 on both.
• Six held-out phrasings, n=5 each: 0/5 on A against 5/5.
• -new with the title "Don't count a negative part in total()": 2/2.

Earlier rounds:

• -declined 5/5.
• tracker-ticket-draft-github-request 3/3.
• onboard-blanket-answer 5/5 against 5/5.
• ticket-draft-retitle, -control and -subtle: 2/2, 2/2 and 1/2 on A against 2/2, 2/2 and 2/2 on B.
• tracker-ticket-draft-new 2/2 against 2/2.

No scenario commits to main after a waiver named in advance, and the sandbox has no commit scenario to extend.
Canary: none yet

What this does

Where a project's standard names GitHub Issues as its tracker, ticket-draft now drafts or refines a GitHub issue and files it through the GitHub server, under the same one-yes write plan Jira uses. A new allow-only hook removes the per-call prompt for the calls the person approved, and leaves every other issue write exactly as the person's own permissions have it.

The pieces

• hooks/issue-gate.sh, registered for mcp__.*__(issue_write|add_issue_comment). It builds and compares a call's target inside one jq run against .review/github-approval.json (docs/contracts.md, "The GitHub approval record" v1).
  • No item is used up. A create's item, <owner>/<repo> <title>, matches every create with that exact title in the window. An update's or a comment's, <owner>/<repo>#<n>, matches every such call on that issue, as a Jira item does.
  • Comparison is byte for byte. Each tool's arguments are allowlisted.
  • Every other call gets no decision, and the person's permissions apply. atlassian-gate.sh is untouched.
• skills/using-github/issues.md holds the issue's fields, the plan's three items and the label rules: existing labels only, each checked with get_label.
  • The plan is written to .review/github-plan.md before it is shown, and linked at the gate.
  • The record's items are written with the Write tool and read by jq --slurpfile.
  • A create that failed or timed out is searched for by its title before it is sent again, so a retry files no duplicate.
  • It also holds the read-back and the paste file <ticket>.issue.md.
• skills/ticket-draft:
  • github.md holds the GitHub tracker's step differences.
  • Where a GitHub issue is asked for on a tracker that is not GitHub's, SKILL.md asks first.
  • Its gate cites decision-points.md: Write all is never taken on a standing answer.
  • The description reaches any request to put a bug or a change into this repository's tracker. It is not for an issue on another project, and every complaint about a skill stays with skill-feedback.
• skills/using-jira/write-plan.md and decision-points.md: a standing answer that does not name a gate never answers it, whenever it was given.
• source-reader, as in round 1. next_phase.py: on a GitHub tracker, unfiled names <slug>.issue.md ("The next phase" v7).
• Sandbox:
  • The stub records writes and serves get_label.
  • run.py treats only the pack's own stub as a writing one.
  • The created issue's number is derived from the fixture.
  • Five tracker-github scenarios, one Jira-pack scenario and two trigger cases.

For the reviewer

• origin/main is merged in, fix(work, where, record): the review findings on #113, GitHub Issues as a tracker #115 included.
  • "The next phase" keeps fix(work, where, record): the review findings on #113, GitHub Issues as a tracker #115's version 6, and this branch's unfiled line is version 7.
  • The pack keeps both sets of scenarios, every work scenario removes the writes file, and the WORK set gains tracker-gh-work-pr and tracker-gh-work-closed-labeled.
  • work goes to 1.9.2.

Doubts

• Runs that stop at the gate on a standing answer usually skip .review/github-plan.md (blanket 2/5, standing answer 1/5). Every filing run writes it (7/7). Tracked in write-plan: a plan shown on a standing answer is often not written to its plan file first #119.

🤖 Generated with Claude Code