docs: require maintainer approval before merge or deploy

[jontsai]

Strengthen the public website contributor rules so production changes stop at the PR until the maintainer explicitly approves merge/deploy.

• Clarifies that implementation/fix requests authorize preparing a PR only, not shipping to production
• Adds a pre-merge/deploy checklist for explicit approval
• Documents that rollback authorization is limited to the requested rollback
• Uses generic maintainer wording appropriate for a public repo

Verification:

• git diff --check
• Husky/lint-staged pre-commit completed successfully

[Copilot]

Pull request overview

This PR tightens the project’s operational documentation to ensure merges/deploys to master (production via GitHub Pages) only happen after explicit maintainer approval, and clarifies that implementation/fix requests authorize opening a PR—not shipping changes.

Changes:

• Clarifies in contributor workflow docs that master is production and requires explicit approval before merge/deploy.
• Expands agent guidance (“golden rules” + workflow steps) to require stopping at PR until approval is explicitly granted.
• Adds a pre-merge/deploy checklist (including rollback boundary) across the agent documentation set.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.

File	Description
CONTRIBUTING.md	Adds explicit “approval required” language to the contributor workflow and PR checklist.
AGENTS.md	Strengthens agent rules and workflow steps to require explicit approval before merge/deploy; adds a pre-merge/deploy checklist.
agent-docs/repository.md	Reinforces the deploy model and approval gating in the repository guide.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.