refactor: rename conventions/ to standards/ #790

The folder conventions/ holds rules that work is judged against (engineering, review, process), and every consumer syncs them into docs/standards/. The repository name already says standards; only this folder name contradicts it. The owner approved the rename on 2026-10-15. The repository name stays.

Plan (net change in every repository is a pure move or a path edit, no stale copies)

1. This repository, one PR:
   • Commit 1: git mv conventions standards only (55 files, 100% similarity renames).
   • Commit 2: path edits in 22 files (75 lines), including the 7 source keys at distribution/sync-manifest.yml:190-196. The sync engine refuses a key whose source file is missing, so the move and the key edits land in the same PR.
   • Run distribution/sync-manifest.sh validate and plan; the destinations must be unchanged.
   • Leave no stub README at the old path.
2. Merge opens the normal sync PRs in the 10 targets. They change content only, because the consumer path (docs/standards/) does not depend on the source folder name. The sync never deletes (sync-manifest.mjs:946-955), and no file moves downstream, so no stale copy can appear.
3. Hand edits after merge: claude-code-plugins (21 lines), github-iac (3), provisioning (2, plus 5 optional), .github (1), medley (1).
4. Check: rerun the code searches for conventions/engineering, conventions/review, conventions/process and standards/blob/main/conventions. Old blob/main/conventions/... URLs return 404 until step 3 lands, and the offline link check skips URLs (lychee.toml:54), so this search is the only check.

Count the references again before starting; these numbers are from a read on 2026-10-15.

🤖 Generated with Claude Code

https://claude.ai/code/session_01J5d23i6K8cwkJC4ZFxVyJh