docs: point standards links at the renamed standards/ folder

.changes/attribution/docs-standards-folder-rename-9f84a9e6.md

@@ -0,0 +1,5 @@
+---
+bump: none
+---
+
+Reference-doc path update for the standards repository's folder rename; no behavior change.

docs/adr/0003-verification-guards-earn-default-on-by-measured-precision.md

@@ -164,5 +164,5 @@ The exception covers the advisory hook only. The same check also runs from guard
   guard), #1314 (the withdrawn guard's measurement and rescope)
 - `docs/contracts/hook-precision/README.md`: over-fire discipline
 - `docs/plugin-philosophy.md`: one mechanism per concern (validation section)
-- `melodic-software/standards`, `conventions/engineering/enforceability-tiers.md`:
+- `melodic-software/standards`, `standards/engineering/enforceability-tiers.md`:
   classify the tier first, justify automation second

docs/adr/0023-scope-skill-quality-to-the-generic-static-checker.md

@@ -26,7 +26,7 @@ with a recheck trigger. (Contrast the "Deferred surfaces" record above, where th
   escape-path scanning, an encapsulation deep-cite regex, a "new script ships `--help` + a sibling test"
   assertion, a deny-list scan *mechanism* whose data is per-consumer) are net-new versus the shipped
   checks but have **no second consumer**; extracting them now is speculative generality / a pre-Rule-of-
-  Three abstraction (`melodic-software/standards` `conventions/engineering/simpler-code.md`). The plugin
+  Three abstraction (`melodic-software/standards` `standards/engineering/simpler-code.md`). The plugin
   can grow a machine-path check the day a real consumer needs one, as its own issue.
 - **Checker hardening** (block-scalar description unfolding, an unquoted-`Use when:` warning, a
   `CHECK_SKILL_BASE_REF` post-commit audit ref for the git-backed checks, and a line-1 frontmatter-fence

docs/contracts/detector-findings/README.md

@@ -671,7 +671,7 @@ review, not a script.
 
 ## Enforceability
 
-Classified per `melodic-software/standards` `conventions/engineering/enforceability-tiers.md`:
+Classified per `melodic-software/standards` `standards/engineering/enforceability-tiers.md`:
 
 | Judgment | Tier |
 |---|---|
@@ -779,6 +779,6 @@ adopter row is a minor bump; docs-only clarification is a patch.
 - [`docs/contracts/finding-suppression/`](../finding-suppression/README.md): the operator-authored suppression record whose `check:` constituent a qualified rule id is, and the consent gate a producer proposes into rather than writes.
 - [`REVIEW.md`](../../../REVIEW.md): this repository's own project severity vocabulary, the live instance of the consumer-precedence override a producer maps to.
 - [`scripts/check-cross-plugin-source-drift.sh`](../../../scripts/check-cross-plugin-source-drift.sh): the shared-source cluster mechanism the emitter decision is measured against, and the gate its revisit trigger fires at.
-- `melodic-software/standards` `conventions/engineering/enforceability-tiers.md`: tier vocabulary and routing rule.
+- `melodic-software/standards` `standards/engineering/enforceability-tiers.md`: tier vocabulary and routing rule.
 - [`liveness-assertion`](../liveness-assertion/README.md): the fail-loud-or-agent-readable contract a detector satisfies by persisting.
 - [`plugin-philosophy` Convention registry](../../plugin-philosophy.md#convention-registry): one owner doc per shared concern, and the before-a-second-adopter deadline this stub answers.

docs/contracts/liveness-assertion/README.md

@@ -118,7 +118,7 @@ states which taxonomy row applies and how it satisfies fail-loud or agent-readab
 
 ## Enforceability
 
-Classified per `melodic-software/standards` `conventions/engineering/enforceability-tiers.md`:
+Classified per `melodic-software/standards` `standards/engineering/enforceability-tiers.md`:
 
 | Judgment | Tier |
 |---|---|
@@ -148,4 +148,4 @@ instance rows is a minor bump; docs-only clarification is a patch.
 
 - [`plugin-philosophy` Prerequisites and failure behavior](../../plugin-philosophy.md#prerequisites-and-failure-behavior): prose doctrine this convention specializes.
 - [`hook-observability`](../hook-observability/README.md): hook-shaped visibility surfaces and the `silent-skip-gate` slice.
-- `melodic-software/standards` `conventions/engineering/enforceability-tiers.md`: tier vocabulary and routing rule.
+- `melodic-software/standards` `standards/engineering/enforceability-tiers.md`: tier vocabulary and routing rule.

docs/contracts/native-references/README.md

@@ -200,7 +200,7 @@ routing-affecting half and earns its separate gate.
 
 ## Enforceability
 
-Classified per `melodic-software/standards` `conventions/engineering/enforceability-tiers.md`:
+Classified per `melodic-software/standards` `standards/engineering/enforceability-tiers.md`:
 
 | Judgment | Tier |
 |---|---|

docs/contracts/recommendation-basis/README.md

@@ -125,7 +125,7 @@ other adopting plugin ships a byte-identical `context/recommendation-basis.md`,
 
 ## Enforceability
 
-Classified per `melodic-software/standards` `conventions/engineering/enforceability-tiers.md`:
+Classified per `melodic-software/standards` `standards/engineering/enforceability-tiers.md`:
 **reasoning-only**. Whether a recommendation is consequential, and whether its grounding reached
 the bar, are judgments about meaning. Presence of a `Basis:` label is greppable in a saved
 transcript, but no check is built.

docs/contracts/upstream-drift/README.md

@@ -35,7 +35,7 @@ that is the fragmentation this doc closes
 
 ## Boundary
 
-`melodic-software/standards` `conventions/engineering/documentation-and-citations.md` owns the
+`melodic-software/standards` `standards/engineering/documentation-and-citations.md` owns the
 general org-wide rule: upstream bodies are read-on-demand; prefer citing and fetching at read time
 over storing a snapshot; a time-bound external claim in durable content needs a recheck trigger.
 This doc takes the concept's name from it. This doc owns the repo-level specialization: the
@@ -44,7 +44,7 @@ for the doc pages this fleet depends on most, and the enforceability classificat
 own:
 
 - **In-repo duplication.** Facts this repo owns are governed by pointer-not-copy
-  (`melodic-software/standards` `conventions/engineering/reference-dont-duplicate.md`) and, for
+  (`melodic-software/standards` `standards/engineering/reference-dont-duplicate.md`) and, for
   byte-identical cross-plugin files, `scripts/cross-plugin-source-registry.txt`.
 - **Synced materializations.** A `managed` component from the standards distribution drifts and
   reconciles through its reviewed sync-PR pipeline, not through stamps in prose.
@@ -453,7 +453,7 @@ carry no label; whether and when to run `apply` stays a person's decision.
 
 ## Enforceability
 
-Classified per `melodic-software/standards` `conventions/engineering/enforceability-tiers.md`:
+Classified per `melodic-software/standards` `standards/engineering/enforceability-tiers.md`:
 
 | Judgment | Tier |
 |---|---|
@@ -485,7 +485,7 @@ routine suppression trains authors to bypass it. That is worse than no gate, bec
 real signal into noise with an approved silencer.
 
 - **Pointer**: for the reasoning-only tier and the worth-mechanizing routing rule, see
-  `melodic-software/standards` `conventions/engineering/enforceability-tiers.md`; the worked
+  `melodic-software/standards` `standards/engineering/enforceability-tiers.md`; the worked
   instance is above.
 - **As of**: 2026-08-12
 - **Recheck trigger**: a third unstamped upstream-fact carrier reaches `main` after this decision
@@ -558,9 +558,9 @@ docs-only clarification is a patch.
 
 ## External authority
 
-- `melodic-software/standards` `conventions/engineering/documentation-and-citations.md`: the
+- `melodic-software/standards` `standards/engineering/documentation-and-citations.md`: the
   org-wide read-on-demand rule and the concept's name.
-- `melodic-software/standards` `conventions/engineering/enforceability-tiers.md`: the tier
+- `melodic-software/standards` `standards/engineering/enforceability-tiers.md`: the tier
   vocabulary and the routing rule.
-- `melodic-software/standards` `conventions/engineering/reference-dont-duplicate.md`: the in-repo
+- `melodic-software/standards` `standards/engineering/reference-dont-duplicate.md`: the in-repo
   counterpart this doc's boundary defers to.

docs/migration-playbook.md

@@ -119,7 +119,7 @@ Namespaces name capability domains; categories are curation.
 **Boundaries are defended by design arguments, never incumbency.** A plugin's shape is justified by
 change-together, useful-alone, and distinct discovery intent, not by the fact that it already ships
 that way ("current state is evidence, never justification", `melodic-software/standards`
-`conventions/engineering/engineering-philosophy.md`).
+`standards/engineering/engineering-philosophy.md`).
 
 ## Naming
 

docs/plugin-philosophy.md

@@ -31,7 +31,7 @@ A plugin is a reusable, independently useful vertical slice of one cohesive capa
 outside the repository and organization that produced it. Publisher metadata may identify its source;
 runtime behavior must not depend on publisher names, organization-specific environment variables,
 repository names, absolute machine paths, or an undocumented consumer layout. `melodic-software/standards`
-`conventions/engineering/shareable-artifact-design.md` owns the artifact-agnostic form of this
+`standards/engineering/shareable-artifact-design.md` owns the artifact-agnostic form of this
 doctrine: consumer-agnostic behavior, externalized consumer-varying configuration, consumer tiers,
 explicit adoption. This document specializes it for Claude Code plugins and adds only what is
 plugin-specific. [Hardcoded consumer specifics](#hardcoded-consumer-specifics) routes the
@@ -124,7 +124,7 @@ invocations are part of that isolation, not an implementation detail.
 The rule is the first paragraph of [Design boundary](#design-boundary): no runtime dependence on one
 machine's paths, one organization's repository names, or an undocumented consumer layout. A value
 that varies per environment, operator, or consumer belongs in the consumer's own config layers
-(`melodic-software/standards` `conventions/engineering/shareable-artifact-design.md`,
+(`melodic-software/standards` `standards/engineering/shareable-artifact-design.md`,
 "Externalize what a consumer may decide"). This subsection is the doctrine owner; component-scoped
 audits cite it instead of restating the rule:
 
@@ -1812,7 +1812,7 @@ covering a topic named beside it. The first list is as of 2026-08-10 (the
   tags, bundles.
 - [Claude Code settings](https://code.claude.com/docs/en/settings): settings scopes, precedence, and
   the special storage and read scopes of `pluginConfigs`.
-- `melodic-software/standards` `conventions/engineering/shareable-artifact-design.md`: the
+- `melodic-software/standards` `standards/engineering/shareable-artifact-design.md`: the
   artifact-agnostic consumer-facing design doctrine the design boundary, configuration ownership,
   and setup contract above specialize for plugins.
 - `melodic-software/standards` engineering philosophy and cross-platform review criteria: repository

plugins/attribution/skills/audit/reference/rubric.md

@@ -394,7 +394,7 @@ the rubric offline cannot follow a pointer. Each is pinned so it can be re-deriv
 **Prefer the pointer over the snapshot.** This rubric treats a pointer read on demand as the end
 state and a stored snapshot as a candidate, and expects a time-bound external claim in durable
 content to carry a recheck trigger. *Pointer:* `melodic-software/standards`,
-`conventions/engineering/documentation-and-citations.md`, as cited by
+`standards/engineering/documentation-and-citations.md`, as cited by
 `docs/contracts/upstream-drift/README.md` "Boundary" in the marketplace repository. *As of:*
 2026-10-01. *Recheck trigger:* any revision of that org standard, or of the upstream-drift
 convention's Boundary section that cites it.