Skip to content

docs: point standards links at the renamed standards/ folder - #224

Merged
kyle-sexton merged 1 commit into
mainfrom
docs/standards-folder-rename
Oct 31, 2026
Merged

kyle-sexton merged 1 commit into
mainfrom
docs/standards-folder-rename

Conversation

@kyle-sexton

Copy link
Copy Markdown
Member

Refs: melodic-software/standards#790

Summary

melodic-software/standards renames its conventions/ folder to standards/
in melodic-software/standards#930.
GitHub does not redirect blob URLs after a folder rename, so links and path
citations to the old folder stop resolving once that PR merges.

Fix

Point the branch-naming link in CONTRIBUTING.md at standards/engineering/naming.md.

Merge this after melodic-software/standards#930 merges; before that, the new
paths do not exist yet.

Verification

  • standards/engineering/naming.md exists on the standards rename branch.

Related

🤖 Generated with Claude Code

https://claude.ai/code/session_01VcupojYKhHyDni9LuAXBuX

melodic-software/standards renames its conventions/ folder to
standards/, and GitHub does not redirect blob URLs after a rename.
Update every reference here to the new path.

Refs: melodic-software/standards#790

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01VcupojYKhHyDni9LuAXBuX
kyle-sexton added a commit to melodic-software/standards that referenced this pull request Oct 31, 2026
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 (#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](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](melodic-software/github-iac#807):
  `README.md` and `LabelsGrammarTests.cs` (3 lines).
-
[melodic-software/provisioning#886](melodic-software/provisioning#886):
  ADR 0003 (2 blob URLs) and two topic plans (4 lines).
-
[melodic-software/.github#224](melodic-software/.github#224):
  `CONTRIBUTING.md` (1 blob URL).
-
[melodic-software/medley#2257](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.com/claude-code)

https://claude.ai/code/session_01VcupojYKhHyDni9LuAXBuX

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
@kyle-sexton
kyle-sexton marked this pull request as ready for review October 31, 2026 05:37
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 31, 2026 •

Copy link
Copy Markdown

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:38:29.117308Z 2c4c8f1 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

Copy link
Copy Markdown

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

Security review of PR #224 (head 2c4c8f1): no security issues found.

The PR changes one line of CONTRIBUTING.md. It repoints the branch-naming link from .../standards/blob/main/conventions/engineering/naming.md to .../standards/blob/main/standards/engineering/naming.md, the same org repository with a renamed folder. The diff has no code, workflow, action, manifest, trust-control or instruction-surface change, and no secrets or tokens. The link target stays inside the melodic-software org, so it adds no external or unpinned source. The change is safe to merge from a security standpoint. The PR body says to merge it after standards#930, but that is a link-resolution matter, not a security one.

I skipped the deep review under skip gate 2 (no security-relevant surface). I did not check the instruction-exception register, because no standing instruction is removed or softened.

critical-findings: 0

@github-actions

Copy link
Copy Markdown

claude-review reviewed 2c4c8f11ec97611519e9f4e6c841cd509a0b6e1a: 0 finding(s), 0 as inline comments.

No findings. The PR changes one URL in CONTRIBUTING.md, from standards/blob/main/conventions/engineering/naming.md#... to standards/blob/main/standards/engineering/naming.md#.... The fragment is unchanged. The change matches the PR's stated intent (Refs: melodic-software/standards#790).

  • Link target unchecked. I did not fetch the new URL. The PR states that the target exists only on the standards rename branch, and I have not verified that. The author says to merge after refactor: rename conventions/ to standards/ standards#930, and the link 404s until that lands. The PR body gives the ordering, but nothing in CI enforces it.
  • Remaining conventions/ references. The repo still has conventions/ references that this PR leaves alone. These are docs/standards/*.md (the README marks them "synced from melodic-software/standards ... Change them there, not here"), REVIEW.md, .claude/source-control.md, and .github/workflows/pr-check-managed-files-hosted.yml. CLAUDE.md makes synced files upstream-owned, so editing the docs/standards ones here would be wrong. I did not look at whether the REVIEW.md, .claude/source-control.md and workflow-file ones are also synced or need their own follow-up. The PR's "Fix" section only claims the CONTRIBUTING.md link, so I count that as out of scope rather than a defect.
  • PR body. It follows the contract: a Refs: line, then Summary, Fix, Verification and Related. The Verification line is author-claimed and I have not independently confirmed it.
  • No other lane items hit. No plugin manifests changed, there is no closing issue (it is Refs:, not Closes), and no path-scoped rule other than pr-body-contract.md exists.

@kyle-sexton
kyle-sexton merged commit a012fe5 into main Oct 31, 2026
18 checks passed
@kyle-sexton
kyle-sexton deleted the docs/standards-folder-rename branch October 31, 2026 05:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant