fix(docs): replace relative pathname:// links with full GitHub URLs

docs/agents/project-planning/README.md

@@ -3,7 +3,7 @@ title: Project Planning Agents
 description: Agents for requirements gathering, architecture decisions, and security planning
 sidebar_position: 1
 author: Microsoft
-ms.date: 2026-08-12
+ms.date: 2026-10-10
 ms.topic: concept
 keywords:
   - project planning
@@ -45,12 +45,12 @@ These agents bring structure and consistency to activities that teams often hand
 
 ## Skills Overview
 
-| Skill                                                                                                   | Sub-Category              | Key Output                                                       |
-|---------------------------------------------------------------------------------------------------------|---------------------------|------------------------------------------------------------------|
-| [requirements-author](pathname://../../../.github/skills/project-planning/requirements-author/SKILL.md) | Requirements              | Drives the BRD/PRD Builder Q&A workflows                         |
-| [architecture-diagrams](pathname://../../../.github/skills/hve-core/architecture-diagrams/SKILL.md)     | Architecture              | ASCII/Mermaid diagrams from IaC analysis                         |
-| [performance-slo-planner](../../reference/skills/project-planning/performance-slo-planner.md)           | Performance & Reliability | SLIs, SLOs, load models, test matrices, and reliability backlogs |
-| [proposal-response](../../reference/skills/project-planning/proposal-response.md)                       | Proposal Responses        | Traceable internal-review question, claim, evidence, and drafts  |
+| Skill                                                                                                                               | Sub-Category              | Key Output                                                       |
+|-------------------------------------------------------------------------------------------------------------------------------------|---------------------------|------------------------------------------------------------------|
+| [requirements-author](https://github.com/microsoft/hve-core/blob/main/.github/skills/project-planning/requirements-author/SKILL.md) | Requirements              | Drives the BRD/PRD Builder Q&A workflows                         |
+| [architecture-diagrams](https://github.com/microsoft/hve-core/blob/main/.github/skills/hve-core/architecture-diagrams/SKILL.md)     | Architecture              | ASCII/Mermaid diagrams from IaC analysis                         |
+| [performance-slo-planner](../../reference/skills/project-planning/performance-slo-planner.md)                                       | Performance & Reliability | SLIs, SLOs, load models, test matrices, and reliability backlogs |
+| [proposal-response](../../reference/skills/project-planning/proposal-response.md)                                                   | Proposal Responses        | Traceable internal-review question, claim, evidence, and drafts  |
 
 ## Requirements
 
@@ -65,13 +65,13 @@ For RFI, RFP, tender, bid, or questionnaire work, use `proposal-response` direct
 
 ## Architecture
 
-Two agents address architecture documentation from different angles. The ADR Creator uses phase-gated, standards-aligned reasoning to guide users through technical decisions (Frame, Decide, Govern), producing architecture decision records. The [architecture-diagrams skill](pathname://../../../.github/skills/hve-core/architecture-diagrams/SKILL.md) analyzes infrastructure-as-code files and project structure to generate ASCII architecture diagrams directly in conversation.
+Two agents address architecture documentation from different angles. The ADR Creator uses phase-gated, standards-aligned reasoning to guide users through technical decisions (Frame, Decide, Govern), producing architecture decision records. The [architecture-diagrams skill](https://github.com/microsoft/hve-core/blob/main/.github/skills/hve-core/architecture-diagrams/SKILL.md) analyzes infrastructure-as-code files and project structure to generate ASCII architecture diagrams directly in conversation.
 
 > [!TIP]
-> Pair the ADR Creator with the [architecture-diagrams skill](pathname://../../../.github/skills/hve-core/architecture-diagrams/SKILL.md): create an ADR for a design decision, then generate a diagram showing how the chosen approach fits the broader architecture.
+> Pair the ADR Creator with the [architecture-diagrams skill](https://github.com/microsoft/hve-core/blob/main/.github/skills/hve-core/architecture-diagrams/SKILL.md): create an ADR for a design decision, then generate a diagram showing how the chosen approach fits the broader architecture.
 
 * [ADR Creator](adr-creation): Guided decision reasoning and documentation
-* [architecture-diagrams skill](pathname://../../../.github/skills/hve-core/architecture-diagrams/SKILL.md): Code-to-diagram generation from IaC analysis
+* [architecture-diagrams skill](https://github.com/microsoft/hve-core/blob/main/.github/skills/hve-core/architecture-diagrams/SKILL.md): Code-to-diagram generation from IaC analysis
 
 ## Performance & Reliability
 
@@ -97,7 +97,7 @@ See the [Security Planning](../security/README.md) guide for the workflow, opera
 * Agent definition files from the `project-planning` collection deployed to `.github/agents/`
 * For Security Planner: agent definition files from the `security` collection
 * For BRD/PRD builders: a writable `.copilot-tracking/` directory for session state persistence
-* For diagram generation: the [architecture-diagrams skill](pathname://../../../.github/skills/hve-core/architecture-diagrams/SKILL.md) works with infrastructure-as-code files (Terraform, Bicep, ARM, Kubernetes YAML, or Docker Compose) in the repository
+* For diagram generation: the [architecture-diagrams skill](https://github.com/microsoft/hve-core/blob/main/.github/skills/hve-core/architecture-diagrams/SKILL.md) works with infrastructure-as-code files (Terraform, Bicep, ARM, Kubernetes YAML, or Docker Compose) in the repository
 
 ## Getting Started
 

docs/agents/project-planning/arch-diagram-builder.md

@@ -3,15 +3,15 @@ title: Architecture Diagrams Skill
 description: Use the portable architecture-diagrams skill to generate ASCII or Mermaid architecture diagrams from infrastructure source files
 sidebar_position: 4
 author: Microsoft
-ms.date: 2026-08-01
+ms.date: 2026-10-10
 ms.topic: how-to
 keywords:
   - architecture diagrams
   - mermaid
   - infrastructure as code
 ---
 
-The [architecture-diagrams skill](pathname://../../../.github/skills/hve-core/architecture-diagrams/SKILL.md) is the recommended way to generate ASCII or Mermaid architecture diagrams from infrastructure source files. It is especially useful for ADRs, onboarding guides, and design reviews when you want a quick, text-based view of a system's structure.
+The [architecture-diagrams skill](https://github.com/microsoft/hve-core/blob/main/.github/skills/hve-core/architecture-diagrams/SKILL.md) is the recommended way to generate ASCII or Mermaid architecture diagrams from infrastructure source files. It is especially useful for ADRs, onboarding guides, and design reviews when you want a quick, text-based view of a system's structure.
 
 ## When to Use This Skill
 

docs/customization/skills.md

@@ -2,7 +2,7 @@
 title: Authoring Custom Skills
 description: Build self-contained skill packages that bundle domain knowledge, reference materials, and scripts for on-demand use
 author: Microsoft
-ms.date: 2026-08-29
+ms.date: 2026-10-10
 ms.topic: how-to
 keywords:
   - skills
@@ -159,7 +159,7 @@ Skills follow a three-level disclosure model that minimizes context consumption:
 
 This model matters for large skills. A compliance-review skill might include hundreds of pages of regulatory text in its `references/` folder, but Copilot reads only the SKILL.md body until a specific regulation is needed.
 
-The [pr-reference skill](pathname://../../.github/skills/shared/pr-reference/SKILL.md) in this repository demonstrates this pattern: the SKILL.md defines the protocol, and supporting files provide templates and helper scripts that load only during active use.
+The [pr-reference skill](https://github.com/microsoft/hve-core/blob/main/.github/skills/shared/pr-reference/SKILL.md) in this repository demonstrates this pattern: the SKILL.md defines the protocol, and supporting files provide templates and helper scripts that load only during active use.
 
 ## Including Reference Materials
 

docs/planning/adrs/0011-define-vally-baseline-equivalence-evaluation-policy.md

@@ -3,7 +3,7 @@ id: "0011"
 title: "Define the Vally baseline-equivalence evaluation policy"
 description: "Define launch-based agent invocation, authoritative evidence, report-only comparison calibration, model scope, and trial posture for the baseline-equivalence suite."
 author: "HVE Core Maintainers"
-ms.date: "2026-09-23"
+ms.date: "2026-10-10"
 ms.topic: "reference"
 status: "proposed"
 proposed_date: "2026-08-01"
@@ -202,7 +202,7 @@ The authoritative/report-only separation, fail-closed rules, population reconcil
 ## More Information
 
 * [package.json](../../../package.json) pins the Vally CLI version whose executor timeout and cleanup semantics the suite relies on.
-* [evals/baseline-equivalence/](pathname://../../../evals/baseline-equivalence/) holds the stimulus corpus and the paired baseline and customized specs this policy governs; its [README.md](pathname://../../../evals/baseline-equivalence/README.md) documents the runtime behavior, the summary field contract, and the pass and fail interpretation rules.
+* [evals/baseline-equivalence/](https://github.com/microsoft/hve-core/tree/main/evals/baseline-equivalence/) holds the stimulus corpus and the paired baseline and customized specs this policy governs; its [README.md](https://github.com/microsoft/hve-core/blob/main/evals/baseline-equivalence/README.md) documents the runtime behavior, the summary field contract, and the pass and fail interpretation rules.
 * [.github/workflows/eval-validation.yml](../../../.github/workflows/eval-validation.yml) owns the outer eval-shard timeout and credentialed calibration dispatch.
 * [scripts/evals/Invoke-BaselineEquivalence.ps1](../../../scripts/evals/Invoke-BaselineEquivalence.ps1) is the single entry point that owns tier validation, model resolution, the pinned judge invocation, and the exit policy in parts 1, 3, and 4.
 * [scripts/evals/lib/EquivalenceParsing.psm1](../../../scripts/evals/lib/EquivalenceParsing.psm1) computes both gates and the verdict described in parts 2 and 4, and reads comparison and guard results.