Initialize the site's GitHub Copilot harness - #3
Merged
Conversation
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 70b8f4d7-f7bf-4a47-b37e-12a987760918
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The site had detailed Copilot guidance, but no canonical cross-surface source of truth, no deterministic checks for fragile static-site contracts, and no disciplined delivery team for taking visual work from product framing through independent release review. This initializes a focused harness for GitHub Copilot app/CLI and VS Code agent mode while preserving the site's dependency-free architecture.
What changed
AGENTS.mdthe canonical repository guidance and reduces.github/copilot-instructions.mdto a thin adapter.PRODUCT.md.DESIGN.md, and a product-specific anti-slop contract.taskbean/taskbeanis product truth andtaskbean/docsowns canonical docs.Non-obvious boundaries
The director coordinates rather than editing. Hidden specialists remain programmatically invokable but do not appear as user entry points. Every UI-changing branch requires both independent release-readiness PASS and anti-slop PASS before the director requests merge approval. Detector output is evidence rather than an automatic verdict: false positives and deliberate exceptions require a concrete product or composition reason. Impeccable onboarding requires
PRODUCT.md, followed byDESIGN.md, before replacement visual-world work.The legacy in-repo
docs/tree is intentionally retained as a temporary migration source. It should be removed only after the separatetaskbean/docsmigration is merged anddocs.taskbean.aiis verified.Validation
node scripts/validate-agent-team.mjs.agent.mdprofilesnode scripts/validate-site.mjsnode scripts/validate-site.mjs --check-externalgit diff --check