Pattern miner: Add responsive-docs-tester curated archetype

[github-actions]

Caution

Protected files were modified in this change.
This pull request is in request_review mode and requires explicit human scrutiny before merge.

Protected files: .github/copilot-instructions.md

Mined pattern: Responsive Docs Tester

Upstream repos mined: githubnext/agentics (workflow files), github/gh-aw (.github/aw/*.md reference docs). Evidence:

• /tmp/gh-aw/data/upstream/githubnext-agentics/files/workflows/accessibility-review.md
• /tmp/gh-aw/data/upstream/githubnext-agentics/files/workflows/multi-device-docs-tester.md

Recurring pattern (2 upstream workflows): Both are schedule-triggered workflows that (1) build and start a web app/docs site locally in a pre-step, (2) poll localhost until the server is ready, (3) drive playwright-cli in bash (not an installed npm Playwright dependency) across multiple device viewports, and (4) report layout/accessibility/interaction findings as GitHub issues or discussions, cleaning up the server afterward. accessibility-review.md even documents in its own prompt that it should propose the build/serve commands as a one-time setup edit if they are still placeholders. multi-device-docs-tester.md is the more complete, generalized implementation (configurable devices, docs_dir, build_command, serve_command, server_port inputs) and explicitly names mobile/tablet/desktop viewport sizes, navigation/overflow/image/accessibility checks, and upload-asset for failure screenshots.

Why the existing library didn't cover it: The existing accessibility-expert archetype is pull_request-triggered and reviews diffs against a live preview — it does not cover the scheduled, build-and-serve-locally-then-multi-viewport-sweep shape, device-size matrix, or the explicit playwright-cli-not-npm-package constraint. No other archetype (community-digest, link-checker, performance-nut) combines scheduled triggers with Playwright-driven multi-viewport testing of a locally built site.

What changed in patterns/:

• Added patterns/archetypes/responsive-docs-tester.json (curated: success_rate: null, count: 0, top_repos: []), covering the build-and-serve pre-step, named viewport set, playwright-cli-only constraint, failure-only screenshot capture via upload-asset, server cleanup, and noop/create-issue duplicate-prevention tips.
• Appended "responsive-docs-tester" to archetypes in patterns/manifest.json.
• Added the responsive-docs-tester runtime rendering entry to patterns/workflow-generation.json (icon device-desktop, bash/browser/network capabilities, Playwright/tools-imports instructions, phase-based prompt body).
• Updated .github/copilot-instructions.md: archetype count 31 → 32 and added responsive-docs-tester to the curated-archetype list, to keep that doc in sync with the manifest (validated by test/copilot-instructions.test.js).

Validation:

• npm test: 19 test files, 327 tests passed (includes test/copilot-instructions.test.js and test/patterns.test.js, which validate the new manifest/archetype entries).
• npm run build: succeeded; dist/patterns/archetypes/responsive-docs-tester.json is emitted alongside the updated manifest.json and workflow-generation.json.

Candidates deliberately left out:

• assign-to-agent safe output (seen in issue-monster.md) — only one upstream workflow demonstrates it; no corroborating doc recommends it as a standalone pattern beyond what backlog-drip's existing tip already covers.
• gollum trigger / wiki-sync workflows (agentic-wiki-writer.md, agentic-wiki-coder.md) — only one upstream pair, and no second independent workflow or doc section recommends this combination; insufficient corroboration per the two-workflow rule.
• Parent/sub-issue auto-closing (sub-issue-closer.md) — only one upstream example; the existing issue-hierarchy-manager archetype already covers the general sub-issue organization pattern it overlaps with.
• Visual-regression-on-PR (playwright + cache-memory baselines) — well documented in visual-regression.md, but no upstream workflow file in the scanned set demonstrates it, so it doesn't meet the "workflow evidence" bar even though it has doc support; left for a future mining run if an upstream workflow example appears.

Generated by Pattern Miner · copilot · auto · 407.7 AIC · ⌖ 12.7 AIC · ⊞ 8.3K · ◷

[github-actions]

Protected files were modified in this pull request and require manual scrutiny before merge.

Please verify that each protected-file change is intentional, policy-compliant, and safe:

• Protected files: .github/copilot-instructions.md