Fix docs link-validator failures from stale experiments page URLs

docs/src/content/docs/practices/experiments-specification.md

@@ -9,7 +9,7 @@ sidebar:
 
 **Version**: 1.0.0  
 **Status**: Draft  
-**Latest Version**: [experiments-specification](/gh-aw/reference/experiments-specification/)  
+**Latest Version**: [experiments-specification](/gh-aw/practices/experiments-specification/)  
 **Editors**: gh-aw maintainers
 
 ---

docs/src/content/docs/reference/artifacts.md

@@ -185,7 +185,7 @@ The `🧪 A/B Experiments` section of the audit report shows the variant chosen
   • style = concise (cumulative: concise:5, detailed:4)
 ```
 
-See [A/B Experiments](/gh-aw/guides/experiments/) for how to declare experiments in workflow frontmatter.
+See [A/B Experiments](/gh-aw/practices/experiments/) for how to declare experiments in workflow frontmatter.
 
 ## Naming Compatibility
 

docs/src/content/docs/reference/forecast-specification.md

@@ -83,7 +83,7 @@ This specification does NOT cover:
 
 - The Effective Tokens (ET) computation algorithm (defined in the [Effective Tokens Specification](/gh-aw/reference/effective-tokens-specification/))
 - The `aw_info.json` artifact schema
-- A/B experiment frontmatter schema (defined in the [A/B Experiments Specification](/gh-aw/reference/experiments-specification/))
+- A/B experiment frontmatter schema (defined in the [A/B Experiments Specification](/gh-aw/practices/experiments-specification/))
 - Billing, pricing, or financial modeling beyond token projections
 - Streaming or real-time token consumption reporting
 
@@ -974,7 +974,7 @@ For orchestrator workflows that primarily use `workflow_call` or `workflow_dispa
 - **[RFC 2119]** Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. <https://www.ietf.org/rfc/rfc2119.txt>
 - **[RFC 3339]** Klyne, G. and Newman, C., "Date and Time on the Internet: Timestamps", RFC 3339, July 2002. <https://www.ietf.org/rfc/rfc3339.txt>
 - **[ET-SPEC]** GitHub Agentic Workflows Team, "Effective Tokens Specification". [effective-tokens-specification](/gh-aw/reference/effective-tokens-specification/)
-- **[EXP-SPEC]** GitHub Agentic Workflows Team, "A/B Experiments Specification". [experiments-specification](/gh-aw/reference/experiments-specification/)
+- **[EXP-SPEC]** GitHub Agentic Workflows Team, "A/B Experiments Specification". [experiments-specification](/gh-aw/practices/experiments-specification/)
 
 ### Informative References
 

docs/src/content/docs/reference/glossary.md

@@ -341,7 +341,7 @@ See [Engines Reference](/gh-aw/reference/engines/).
 
 A frontmatter section that enables A/B testing of workflow prompt variants across successive runs. Each key in the `experiments:` map names an experiment; the value is either a bare array of variant strings or a rich object with additional fields (`variants`, `description`, `hypothesis`, `metric`, `weight`, `min_samples`, `start_date`, `end_date`). At runtime the activation job selects one variant per experiment using a balanced round-robin counter and exposes the selection as `${{ experiments.<name> }}` for use anywhere in the workflow body.
 
-Experiment state is persisted to dedicated `experiments/<name>` git branches in the workflow repository. Use `gh aw experiments list` and `gh aw experiments analyze` to inspect variant distribution and statistical readiness (chi-square balance test, Bonferroni correction, EXTEND / READY_FOR_ANALYSIS recommendation). See [A/B Experiments](/gh-aw/guides/experiments/) and the [Experiments Specification](/gh-aw/reference/experiments-specification/).
+Experiment state is persisted to dedicated `experiments/<name>` git branches in the workflow repository. Use `gh aw experiments list` and `gh aw experiments analyze` to inspect variant distribution and statistical readiness (chi-square balance test, Bonferroni correction, EXTEND / READY_FOR_ANALYSIS recommendation). See [A/B Experiments](/gh-aw/practices/experiments/) and the [Experiments Specification](/gh-aw/practices/experiments-specification/).
 
 ```aw wrap
 experiments: