[kyle-sexton]

Closes #790

Summary

Rename the top-level conventions/ folder to standards/, so the folder
name matches the repository name and the docs/standards/ path every
consumer already syncs into. The owner approved the rename on 2026-10-15.

Fix

Two commits, so history follows the move:

1. refactor: move conventions/ to standards/: git mv only, 56 files,
   all 100% similarity renames.
2. refactor: point every reference at standards/: 88 lines in 24 files
   (87 path references plus the standards/README.md heading). Relative links, absolute blob/main/conventions/... URLs inside the
   moved files, prose paths in README.md, AGENTS.md, REVIEW.md,
   distribution/, docs/ and component READMEs, and the eight
   engineering-standards source keys in distribution/sync-manifest.yml.
   After merging main, .github/trust-path-hold.json is gone (ci: remove the trust-path hold caller #931), so
   its glob edit dropped out with it.

Left unchanged on purpose: consumer-side docs/conventions/... paths (for
example the commit-convention destination), links into
claude-code-plugins/docs/conventions/, the github-actions-conventions
component, and every use of "conventions" as an ordinary word.

No workflow, lint config or test in this repository names the old folder,
so none needed an edit (git grep over every tracked file).

Verification

• bash distribution/sync-manifest.sh validate: Manifest valid: 47 components, 14 targets, before and after.
• bash distribution/sync-manifest.sh plan, before (origin/main) and after:
  the set of (target, mode, destination path) triples is identical, 374
  rows. The only plan lines that differ are the eight source paths
  (conventions/engineering/*.md to standards/engineering/*.md), once
  for each of the 10 targets that adopt engineering-standards.
• Destination bytes: the next sync changes content only, at the same
  paths. Synced files whose text named the old folder now name the new one:
  REVIEW.md, docs/standards/README.md, and six of the eight
  docs/standards/*.md files (their blob/main/... URLs).
• git grep -nP '(?<![\w-])(?<!docs/)conventions/' returns nothing.
• Every test:* and lint:* script in package.json passes (after npm ci
  in the root, distribution/ and each component with a lockfile).
• harness/shell/run-tests.sh over all 41 *.test.sh files: 39 pass.
  components/go-analysis/go-analysis.test.sh and components/ruff/ruff.test.sh
  fail identically on an untouched origin/main checkout (local golangci-lint
  2.13.2 against a pinned 2.12.2 and a Go 1.27 export-data mismatch; local
  ruff 0.17.0), so they are local toolchain drift, not this change.

Related

Other repositories that cite standards' conventions/... paths. GitHub does
not redirect blob URLs after a rename, so each gets a draft PR that lands
after this one merges:

• melodic-software/claude-code-plugins#11377:
  20 lines in 10 files (ADRs 0003 and 0023, five docs/contracts/*/README.md,
  docs/migration-playbook.md, docs/plugin-philosophy.md, the attribution
  audit rubric).
• melodic-software/github-iac#807:
  README.md and LabelsGrammarTests.cs (3 lines).
• melodic-software/provisioning#886:
  ADR 0003 (2 blob URLs) and two topic plans (4 lines).
• melodic-software/.github#224:
  CONTRIBUTING.md (1 blob URL).
• melodic-software/medley#2257:
  docs/conventions/progressive-disclosure.md (1 blob URL).

Not edited: the historical entry in claude-code-plugins
docs/contracts/upstream-drift/CHANGELOG.md, and dated research notes under
.work/ in medley and knowledge-corpus. azure-iac has no reference.

Synced copies update through the normal sync PRs after merge and need no
hand edit: REVIEW.md in 12 targets, docs/standards/* in 10.

🤖 Generated with Claude Code

https://claude.ai/code/session_01VcupojYKhHyDni9LuAXBuX

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-31T05:32:37.940689Z	229b22a	Draft marked ready

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[github-actions]

claude-review reviewed 229b22ab9b96d71758c9129d027dedfa47260456: 0 finding(s), 0 as inline comments.

No findings. This PR renames conventions/ to standards/ and updates references to match. I read the full diff and searched the repo at the head commit for leftover references.

• Rename: The renamed files carry no content changes beyond the path edits. Relative links inside the moved files stay valid because the folder keeps the same depth.
• Sync manifest: The eight engineering-standards source keys in distribution/sync-manifest.yml now point at standards/engineering/*.md. The destinations (docs/standards/*) are unchanged.
• Leftover references: git grep -nP '(?<![\w-])(?<!docs/)conventions/' returns nothing at the head. The remaining conventions hits in workflows, CODEOWNERS, dependabot.yml, _typos.toml and package.json are the github-actions-conventions component or ordinary prose. None names the old folder, so the PR's claim that no workflow, lint config or test needed an edit holds.
• Closing issue refactor: rename conventions/ to standards/ #790: The criteria are met: one PR, a move commit and an edit commit, no stub README at the old path, destinations unchanged.
• Not checked: I did not run sync-manifest.sh validate or plan, so the PR's verification claims stay author-claimed and unverified. The installed review plugin copy was not searched, because the search was denied. Other repositories that cite the old conventions/... paths are outside this diff. The PR lists draft follow-up PRs for them, which I did not inspect.
• Manifest and paved-path checks: Neither applies. No plugin manifests changed, and I did not resolve a standards index.
• PR body: It follows the contract, with Closes #790 and the four required sections. No embedded instructions were found in the PR context.

[github-actions]

claude-security-review reviewed 229b22ab9b96d71758c9129d027dedfa47260456: 0 finding(s), 0 as inline comments.

No security findings.

PR #930 at 229b22a renames conventions/ to standards/ across 70 files (87 additions, 87 deletions). Every added line I checked only swaps a path prefix. The one other added line is the # standards heading in AGENTS.md.

Checks that came back clean

• Sync manifest: distribution/sync-manifest.yml changes only the source keys of the engineering-standards component, from conventions/engineering/* to standards/engineering/*. The destination paths under docs/standards/ are unchanged, and the file list is the same eight files.
• Source files: the renamed standards/engineering/ directory exists and holds the files the manifest points at. The old conventions/ directory is gone.
• Stale references: a search of package.json, .github, components, scripts and distribution found no remaining reference to the old conventions/engineering|process|review paths. The other conventions/ hits are names like github-actions-conventions/ and commit-convention/.
• Trust controls and manifests: the diff touches none of the trusted-actor list, CODEOWNERS, .gitmodules, the .github/actions/ controls, the token broker, merge holds or any plugin manifest. No token scope, secret handling or actor trust changes.
• Instruction surfaces: AGENTS.md and REVIEW.md change only in path references and that heading. No rule is deleted, narrowed or softened. I did not read the instruction exception register, because this diff removes no standing rule.
• Diff access: the wrapper supplied no diff or PR-context file, so I read the diff with gh pr diff.

critical-findings: 0