[potiuk]

Layer 4b (part 1) of the security-family deep split (#1672), after #1705 (cve-allocate) and #1707 (deduplicate): the rule-shaped parts of security-issue-sync move into an issue-sync family of tools/security-management. Mining signals, the signals-to-actions table and the gather recipe stay with the model and follow in part 2.

What moves to code

Where	Command	Decides / renders
Inputs / bulk 1	selector, resolve	the selector as gh reads (a malformed CVE-… token stops it before any search); the resolved set (ledger dropped, closed announced cut to 90 days, a CVE matched only in its CVE tool link field, capped lists flagged) and the echo
Bulk 1b	preflight-query, preflight	the batched state read; the no-op rule table, never skipping an explicitly named tracker
Bulk 3–4	bucket, parse-bulk-reply	CVE-affecting vs non-CVE-affecting (the allocated → review-ready push rides the latter), walk order; the merged confirmation syntax
Step 3	parse-reply	the single-tracker form (shared.numbered)
Guardrails	check	reporter CVSS outside the observed state, other ASF projects, a bare CVE ID on markdown (or the CVE-tool URL in an email), bare #NNN
Step 0 / drafts	security-cc, draft-backend	the CC through the configuration layers (shared.recipients); Gmail or Maildir, then the Gmail backend (shared.drafting.choose)
GHSA	ghsa-route	the access tier and how each advisory change is delivered
Step 5b	push-decision	skip, the seven gates (three checked on the JSON, four taken as the model's verdicts), session probe, push, state verification
Step 6	render-recap	the recap with every link

Nine eval suites become pytest cases named after each former case (tests/test_issue_sync.py, tests/test_issue_sync_rules.py): step-bulk-selectors, step-bulk-orchestration, step-3-confirm, step-6-recap, step-guardrails, step-security-cc, step-draft-backend, step-ghsa-access-tier, step-5b-push-decision. A new step-5b-judged-gates model suite covers the four gates the model still judges, and passes 2/2. The skill's model cases go from 86 to 38.

SKILL.md grows slightly (7,006 → 7,282 tokens): this part adds the router lines but moves no large section out yet; gather.md and signals-to-actions.md, the bulk of the skill, are part 2.

Behaviour changes

• A malformed CVE token stops the whole selector before any search.
• A CVE search keeps only trackers whose CVE tool link names the CVE, read through github-body-field rather than a body regex.
• A bulk reply naming an unknown tracker or item, two dispositions for one tracker, or force-sync of a tracker that was not skipped applies nothing.
• An explicit null or blank fallback address in the project layer disables the organization's, and the draft is blocked.
• An admin-only advisory change after a 403 is never retried, and is always a draft relay, never a tracker comment.
• A judged push gate with no verdict is asked for before the push, never assumed to pass.
• The cve-allocate title cascade also strips a bracketed [GHSA-…] ID.
• A CVE ID that is not CVE-YYYY-NNNNN never reaches a printed command: push-decision and the deduplicate apply plan (from perf(security-issue-deduplicate): decide and render the merge as code #1707) refuse it, and quote it.

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