AFK: Generate act-board issue bodies and upsert by rule id

[WilcoFiers]

Parent

#60

Type

AFK

What to build

Given classifier JSON, upsert one issue per rule in act-rules/act-board. Title key: [674b10] Role attribute has valid value. Body is fully generated: bot disclaimer at the top, changelog (rule vs definition), non-blocker CG issue links, complete implementations, links to WAI proposed/approved pages and the CG rule file.

Skip GitHub writes when title, body, fields, and sub-issue set are unchanged. Close issues for deprecated/removed rules. Humans comment; they must not need to edit the body.

Blockers: do not copy CG tickets. Use GitHub cross-repo sub-issues: addSubIssue so each matching open Blocker issue on act-rules/act-rules.github.io is a child of the act-board rule issue. Remove the link if the CG issue is closed or no longer labelled Blocker.

A GitHub issue can have only one parent. If a blocker matches several rules, attach it under the lowest rule id only, and still list it in every matching rule body (so those rules stay Blocked by issue).

Acceptance criteria

• Upsert finds existing issues by [ruleId] title prefix
• Body starts with a generated-by-bot / do-not-edit note
• No-op when nothing changed (including sub-issue set)
• Deprecated rules get their issues closed
• Open CG Blocker issues are linked as cross-repo sub-issues; they are not duplicated
• Multi-rule blockers get a single parent (lowest rule id) and still appear in each matching body
• Tests cover body content, upsert key, skip/close, and add/remove sub-issue behavior (API mocked)

Blocked by

• AFK: Classifier JSON, seven statuses, and split commit counts #62

[WilcoFiers]

Shipped in #70 (feat: upsert act-board issues and blocker sub-issues). That PR was tagged as part of #60, so this issue stayed open.

Acceptance criteria on origin/main (src/approval-report/act-board.ts, src/cli/upsert-act-board.ts, mocked tests in src/approval-report/__tests__/act-board.test.ts):

• Upsert finds existing issues by [ruleId] title prefix
• Body starts with a generated-by-bot / do-not-edit note
• No-op when nothing changed (including sub-issue set)
• Deprecated rules get their issues closed (also closes snapshot-missing issues; closed issues are not moved to Approved, current because Project automations are off)
• Open CG Blocker issues are linked as cross-repo sub-issues; they are not duplicated
• Multi-rule blockers get a single parent (lowest rule id) and still appear in each matching body
• Tests cover body content, upsert key, skip/close, and add/remove sub-issue behavior (API mocked)

Closing as completed.