Pattern quality: Add duplicate-prevention tip to status-report archetype

[github-actions]

What was evaluated

I evaluated all 6 samples in /tmp/gh-aw/data/generated-patterns-and-prompts.json (status-report, issue-triage, code-improvement, documentation-updater, dependency-monitor, pr-review) against the pattern data in patterns/archetypes/*.json and the prompt-generation logic in src/js/workflow.js.

Recurring quality issue found

src/js/workflow.js already has a duplicatePreventionTips() helper that surfaces any archetype tip matching skip-if-match|tracker-id|expires into the generated prompt as an explicit "Prevent duplicate scheduled findings" requirement. dependency-monitor and security-scanner — both schedule-triggered archetypes whose safe output is create-issue — already carry this tip and it correctly reaches the downstream prompt.

status-report has the exact same shape (schedule trigger, create-issue safe output, as seen in the status-report-daily sample), but its archetype file had no dedup tip. As a result, the generated wizard prompt for status-report-daily told the downstream agent to add a pre-fetch step and DO-NOT constraints, but never mentioned deduplication. A Monday–Friday scheduled status-report workflow built from this prompt as-is would create a brand-new issue every single run with no skip-if-match/tracker-id guard, so daily reports would accumulate as separate open issues indefinitely instead of updating/replacing a rolling report issue — the same failure mode the existing duplicatePreventionTips() logic was specifically built to prevent for the sibling archetypes.

What changed

• patterns/archetypes/status-report.json: added a tip, "Use skip-if-match and expires on create-issue so scheduled reports don't accumulate as duplicate open issues", matching the phrasing style of the existing dependency-monitor/security-scanner tips. No generator code changes were needed — the existing duplicatePreventionTips() regex already picks this up automatically.
• test/workflow.test.js: updated the existing test surfaces duplicate-prevention guidance for scheduled findings archetypes, which previously asserted status-report should not contain this guidance, to instead assert it does (matching the new, correct behavior).

Validation

• npm test: 199/199 passed
• npm run build: succeeded

Follow-ups deliberately left out

• issue-hierarchy-manager and user-simulator are also schedule + create-issue archetypes without a dedup tip, but they weren't in the evaluated sample set and their found-issue semantics differ enough (hierarchy sync vs. persona simulation) that I didn't want to guess at appropriate tip wording without more evidence. Worth a follow-up pass.
• repo-maintainer combines reaction/slash_command/schedule triggers with issues+pull-requests outputs but also lacks a dedup tip; same reasoning — left out to keep this change minimal and evidence-based.

Generated by Pattern Quality Eval · auto · 69.9 AIC · ⌖ 6.82 AIC · ⊞ 7.6K · ◷

[github-actions]

Reviewer: matt-pocock (auto-dispatched — change touches patterns/archetypes/status-report.json data plus a test/workflow.test.js assertion update)

No blocking issues found. The change is minimal and well-justified:

• The added tip string matches the existing phrasing/regex convention used by duplicatePreventionTips() (skip-if-match|tracker-id|expires), so it correctly flows through to the generated prompt without any generator code changes.
• The corresponding test was updated to assert the new (correct) behavior rather than the old absence-of-guidance behavior, and the PR description reports 199/199 tests passing plus a successful build.
• Scope is appropriately narrow — the PR explicitly declines to touch issue-hierarchy-manager, user-simulator, and repo-maintainer pending further evidence, which is a reasonable, low-risk boundary for a data-only fix.

No further changes requested.

Generated by Specialist PR Review for #172 · auto · 13.6 AIC · ⌖ 1.66 AIC · ⊞ 7.9K