Pattern miner: Add min-integrity tip to status-report archetype from upstream mining

[github-actions]

Summary

Mined upstream workflow sources for recurring shapes not yet represented in patterns/, and added one small, evidence-backed refinement to the status-report archetype.

Upstream sources mined

• githubnext/agentics: .github/workflows/*.md (58 workflow files), including team-status.md, repo-status.md, weekly-issue-activity.md, repo-chronicle.md, plan.md, q.md, repo-ask.md, daily-issue-triage.md
• github/gh-aw: .github/aw/syntax-tools-imports.md, .github/aw/pr-reviewer.md (docs confirming supported frontmatter for tools.github.min-integrity)

Recurring pattern found

16 upstream workflows in githubnext/agentics set tools.github.min-integrity: none (or explicitly document the equivalent trust rationale), including report/status-style workflows: team-status.md (line 23), repo-status.md (line 26), weekly-issue-activity.md (line 26), repo-chronicle.md (line 31), plan.md (line 33), q.md (line 33), repo-ask.md (line 26), plus daily-issue-triage.md (line 38), issue-arborist.md, contribution-check.md, contribution-guidelines-checker.md, ai-moderator.md, pr-fix.md, pr-nitpick-reviewer.md, discussion-task-miner.md, weekly-research.md.

In each case the comment explains the same rationale: the workflow only reads/summarizes issues, PRs, or discussions (never acts destructively on them), so it deliberately sets the lowest trust gate (min-integrity: none) to avoid filtering out content from untrusted authors when generating a report. github/gh-aw's .github/aw/syntax-tools-imports.md (line 84) and .github/aw/pr-reviewer.md (line 62, "Use the lowest min-integrity that supports the required actions") confirm this is a documented, recommended tuning knob, not an incidental one-off.

This satisfies the two-workflow-plus-documentation bar for a recurring, evidence-backed candidate.

Why the existing library did not cover it

Searched patterns/*.json and patterns/archetypes/*.json for min-integrity and lockdown — the only prior mentions are lockdown in content-moderation.json and pr-review.json. No archetype mentioned min-integrity at all, despite it recurring heavily across exactly the reporting-style workflows (status-report archetype: team-status/repo-status/weekly-issue-activity/repo-chronicle/plan/q/repo-ask all map to this archetype's shape — scheduled, read-heavy, report-producing).

What changed

• patterns/archetypes/status-report.json: appended one tip to the existing tips array:

  "Set tools.github.min-integrity: none when the report must read issues, PRs, or discussions from any author regardless of trust — the workflow only summarizes, it never acts on that content"

No other fields (metadata, anti_patterns, trigger_combos, research_findings, success_rate, count, top_repos) were touched. No new archetype was added, no manifest changes, no workflow-generation.json changes (the status-report runtime body doesn't currently render per-archetype tips separately).

Validation

• npm test: 18 test files, 319 tests passed.
• npm run build: succeeded (✓ built in 145ms), dist/patterns/archetypes/status-report.json regenerated with the updated tip.

Candidates considered and left out

• Link-checker as a new archetype (link-checker.md): only one upstream workflow of this specific shape (daily doc link-checking via a scripted steps: block, no safe-outputs, direct commit-based fix). No second corroborating workflow or explicit doc recommendation found, so it does not meet the two-workflow-or-documented bar.
• assignees: copilot on findings (duplicate-code-detector.md, large-file-simplifier.md): only 2 upstream workflows use this exact convention, both already summarized in and consistent with the existing code-health-auditor archetype's tip ("Assign findings to copilot so remediation can be picked up automatically") — already covered.
• Pre-activation PR-count throttle (glossary-maintainer.md, unbloat-docs.md): same guard already reflected in code-improvement.json / documentation-updater.json tips ("Add a pre-activation step that skips scheduled runs once too many open PRs share your title prefix") — already covered.
• New dispatcher/slash_command archetype: only unbloat-docs.md combines slash_command with schedule; not enough distinct recurring shape beyond what's already described in the custom-instruction trigger-combo notes (slash_command as dispatcher pattern) to warrant a new archetype file.

Generated by Pattern Miner · copilot · auto · 62.4 AIC · ⌖ 11.8 AIC · ⊞ 8.5K · ◷

[Copilot]

🟢 Approval recommended

The change is a small, valid JSON-only update consistent with existing pattern guidance (including prior min-integrity mentions) and does not introduce behavioral or structural risk.

Pull request overview

This PR updates the pattern library’s status-report archetype to capture a newly mined, recurring upstream configuration tip related to GitHub tool integrity filtering, improving guidance for report-style workflows.

Changes:

• Added a new tips entry to patterns/archetypes/status-report.json recommending tools.github.min-integrity: none for read-only reporting workflows that must include content from any author.
• Kept all other archetype fields unchanged (e.g., metadata, anti-patterns, trigger combos).

File summaries

File	Description
patterns/archetypes/status-report.json	Appends a mined tip about tools.github.min-integrity tuning for comprehensive, non-destructive reporting scenarios.

Review details

• Files reviewed: 1/1 changed files
• Comments generated: 0
• Review effort level: Lite

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.