[potiuk]

Layer 3 of the security-family deep split (#1672), after #1680 (import) and #1686 (triage and invalidate): security-cve-allocate's rule-shaped steps move into a cve-allocate family of tools/security-management.

What moves to code

security-management cve-allocate <command> --input <file> prints JSON and runs nothing; tracker text reaches it only in files the agent wrote.

Step	Command	Decides / renders
Inputs	selector	the tracker and an optional CVE-YYYY-NNNNN override; a malformed or second CVE token is refused
0 item 5	preflight	the vulnogram-api-check exits as the Step 3 path, the next check, or the setup to offer
1	blockers	closed, CVE already in the field or cve allocated, duplicate, not exactly one scope label, undecided field; needs triage warns only when nothing blocks
2	title	the strip cascade, from the project's names and tracker prefixes; over-strip warning under 3 words
3	recipe, allocate-result, cve	the API proposal (title shell-quoted), self-service recipe or terse relay; what an allocation exit means next (never re-run on its own); the one CVE ID in the paste-back
4	draft-plan, check-draft, proposal, render-rollup	whether the reporter gets a status draft and how; the draft's leak check; items 1–5; the rollup entry
5	parse-reply, apply-plan	the confirmation forms (nothing applies by default); the per-backend apply order
7	render-recap	the recap with every link

The model keeps writing the reporter draft; the user keeps the allocation. The draft-backend choice and leak scan move unchanged from issue_invalidate to shared.drafting, so both skills use one copy.

SKILL.md becomes a router (7,679 → 7,324 tokens). Every heading and golden-rule headline is unchanged, and the blocker list moved to outcomes/blockers.md. The step-1, 2, 3, 4, 5 and 7 model suites are now pytest cases named after each former case (tests/test_cve_allocate.py). A new step-4-draft-body model suite covers the reporter draft, the one step the model still owns, and passes 3/3 on a self-eval.

Behaviour changes

• The reporter status draft names the bare CVE ID, never the CVE-tool record URL, which a reporter cannot open (editorial guidelines). The skill and the canned-response template said the opposite; both are fixed.
• A malformed or second CVE token, in the invocation or the paste-back, is refused, never repaired.
• Two scope labels, or a CVE tool link field github-body-field will not decide on, block instead of being guessed.
• A re-run whose override is already wired into the field (a partial apply) is a resume, not an "already allocated" blocker.
• A draft ID is claimed pending in the rollup only after checking Drafts.
• An allocation is never re-run automatically; after an expired token it needs a fresh yes.
• A free-form reply applies nothing: it is an edit, and the proposal is confirmed again.

Spec security-issue-lifecycle describes the new family.

Part of #1672

Generative AI disclosure

Drafted with Claude Code (Claude Opus 5) and reviewed by the author.

🤖 Generated with Claude Code