Pattern miner: Add close-older-issues tip to status-report archetype

[github-actions]

Upstream evidence

Mined githubnext/agentics (files/workflows/) status-report style workflows for recurring safe-output patterns not yet captured by the status-report archetype tips.

• workflows/team-status.md — safe-outputs.create-issue.close-older-issues: true
• workflows/repo-status.md — safe-outputs.create-issue.close-older-issues: true
• workflows/weekly-repo-map.md — safe-outputs.create-issue.close-older-issues: true

All three are daily/weekly scheduled report generators that create a single status/report issue per run and use close-older-issues: true to close the prior run's issue instead of relying on skip-if-match/expires. Documented upstream in github/gh-aw (.github/aw/safe-outputs-content.md, line ~103): "Optional: close previous issues from same workflow (default: false)".

Recurring pattern

3 upstream status-report-shaped workflows demonstrate the same shape: create-issue + close-older-issues: true as the deduplication mechanism for periodic report issues, backed by the gh-aw core docs describing the option.

Why the library didn't already cover it

patterns/archetypes/status-report.json only listed skip-if-match + expires as the deduplication tip. close-older-issues is a distinct, commonly used alternative (close the prior issue on new run) not previously mentioned anywhere in patterns/.

What changed

• patterns/archetypes/status-report.json: appended one tip describing close-older-issues: true as an alternative to skip-if-match for status-report deduplication. No other fields touched (success_rate, count, top_repos, anti_patterns, triggers, safe_outputs, tools all unchanged).

Validation

• npm test: 318 passed (18 test files)
• npm run build: succeeded

Candidates considered and left out

• Discussion Task Miner (discussion-task-miner.md) — single upstream example scanning Discussions to create issues; no second corroborating workflow or explicit doc recommendation, so it doesn't meet the two-workflow threshold for a new archetype.
• Sub-Issue Closer (sub-issue-closer.md) — overlaps with the existing issue-hierarchy-manager archetype's "close parent issues once sub-issues complete" tip; not additive.
• Weekly Repo Map / ASCII tree visualization — only one upstream example (weekly-repo-map.md); insufficient corroboration for a new archetype.
• Editorial/content-quality board (tech-content-editorial-board.md) — overlaps significantly with existing code-health-auditor and documentation-updater archetypes (issue + PR dual safe-outputs, quality focus); not a distinct recurring shape.
• Pre-activation open-PR-count throttle (glossary-maintainer.md, unbloat-docs.md, tech-content-editorial-board.md) — already captured by the existing tip "Add a pre-activation step that skips scheduled runs once too many open PRs share your title prefix" in code-improvement and documentation-updater.

Generated by Pattern Miner · copilot · auto · 47 AIC · ⌖ 10.5 AIC · ⊞ 8.5K · ◷