fix(skills): bootstrap shared RPI instructions

📝 - Generated by Copilot

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Author: algattik

.cspell.json

@@ -71,6 +71,7 @@
 	],
 	"ignorePaths": [
 		".agent/reviews/**",
+		".github/instructions/hve-core/copilot-tracking.instructions.md",
 		"**/.github/chatmodes/**",
 		"**/node_modules/**",
 		"**/vscode-extension/**",

.github/copilot-instructions.md

@@ -334,24 +334,15 @@ The weekly `copilot-setup-steps.yml` cron and `Test-BinaryFreshness.ps1` weekly
 
 The `Bootstrap hve-core RPI skills` step in `copilot-setup-steps.yml` runs **outside** the cloud-agent firewall and uses `gh skill install` to download the complete RPI skill suite from a pinned `microsoft/hve-core` commit into immediate subdirectories of `.github/skills/`.
 
-The generated `.github/skills/rpi-*/` directories are gitignored and excluded from repository Markdown linting. The setup step names all eight allowed skill paths explicitly, pins every installation to the reviewed commit, and relies on the GitHub CLI to preserve each skill's references and templates and inject its source commit and tree metadata into `SKILL.md`. Bootstrap failure is fatal because no local fallback provides these workflows.
+The generated `.github/skills/rpi-*/` directories and `.github/instructions/hve-core/copilot-tracking.instructions.md` are gitignored and excluded from repository linting. The setup step names all eight allowed skill paths explicitly, pins every installation to the reviewed commit, and downloads the shared tracking instruction from the same commit.
+
+The GitHub CLI preserves each skill's references and templates and injects its source commit and tree metadata into `SKILL.md`. Bootstrap failure is fatal because no local fallback provides these workflows.
 
 The cloud agent discovers the `rpi-quick`, `rpi-research`, `rpi-plan`, `rpi-implement`, and `rpi-review` workflows directly from their `SKILL.md` files. The bootstrap also preserves `rpi-challenger`, `rpi-plan-critique`, `rpi-walkthrough`, and every bundled reference and template.
 
 The current immutable commit predates a published hve-core release containing the skill-forward layout. Prefer a released commit on upgrades; when none exists, review the complete upstream commit and tree before changing `RPI_SKILLS_REF`.
 
-Before starting RPI work, verify each required `.github/skills/rpi-*/SKILL.md` exists and its `metadata.github-pinned` value matches `RPI_SKILLS_REF`; otherwise stop with a bootstrap failure.
-
-Use `.copilot-tracking/` for RPI intermediate state rather than conversation memory. Keep task slugs in lower kebab case and write dated artifacts to the phase-specific paths used by the skills:
-
-* Research: `.copilot-tracking/research/YYYY-MM-DD/<task>-research.md`
-* Plans: `.copilot-tracking/plans/YYYY-MM-DD/<task>-plan.md`
-* Phase details: `.copilot-tracking/details/YYYY-MM-DD/<task>-phase-details.md`
-* Implementation: `.copilot-tracking/changes/YYYY-MM-DD/<task>-changes.md`
-* Plan critique: `.copilot-tracking/reviews/plans/YYYY-MM-DD/<task>-plan-critique.md`
-* Review: `.copilot-tracking/reviews/logs/YYYY-MM-DD/<task>-review.md`
-
-Generated tracking Markdown starts with `<!-- markdownlint-disable-file -->`. Use one stable task ID across artifacts, `Pxx` phase IDs, and `Pxx-Txx` task IDs. Keep tracking paths out of production code, code comments, documentation strings, and commit messages. Update the current phase artifact when gaps remain instead of skipping ahead, and name the next phase and expected artifact path in handoffs.
+Before starting RPI work, verify each required `.github/skills/rpi-*/SKILL.md` exists, its `metadata.github-pinned` value matches `RPI_SKILLS_REF`, and `.github/instructions/hve-core/copilot-tracking.instructions.md` exists; otherwise stop with a bootstrap failure. The generated instruction is the source of truth for `.copilot-tracking/` artifact paths, evidence ownership, IDs, formatting, and handoffs.
 
 In cloud-agent PR work, persist each completed RPI phase as a PR comment and maintain an `RPI Artifact Index` in the PR description with the phase comment links and resolved upstream SHA. If PR write tools are unavailable, include the complete phase artifacts in the final response rather than claiming durable persistence.
 

.github/workflows/copilot-setup-steps.yml

@@ -150,3 +150,10 @@ jobs:
               --dir .github/skills \
               --force
           done
+
+          tracking_instruction=".github/instructions/hve-core/copilot-tracking.instructions.md"
+          mkdir -p "$(dirname "$tracking_instruction")"
+          gh api \
+            "repos/microsoft/hve-core/contents/.github/instructions/hve-core/copilot-tracking.instructions.md?ref=$RPI_SKILLS_REF" \
+            --header "Accept: application/vnd.github.raw+json" \
+            > "$tracking_instruction"

.gitignore

@@ -465,6 +465,7 @@ venv/
 **/out/*
 .agent/
 .copilot-tracking/
+.github/instructions/hve-core/copilot-tracking.instructions.md
 .github/skills/rpi-*/
 
 # Environment-specific deployment artifacts

.markdownlint-cli2.jsonc

@@ -3,6 +3,7 @@
     "**/node_modules/**",
     ".agent/reviews/**",
     ".copilot-tracking/**",
+    ".github/instructions/hve-core/copilot-tracking.instructions.md",
     ".github/skills/rpi-*/**",
     "venv/**",
     ".venv/**",

docs/contributing/architecture.md

@@ -387,12 +387,12 @@ HVE-Core artifacts are registered via the extension's `package.json` `contribute
 
 This repository defines project-specific artifacts in `.github/` that extend HVE-Core with domain knowledge:
 
-| Artifact Type | Count | Purpose                                                                          |
-|---------------|-------|----------------------------------------------------------------------------------|
-| Agents        | 2     | OSMO training manager, dataviewer developer                                      |
-| Instructions  | 4     | Copilot instructions, dataviewer conventions, documentation style, shell scripts |
-| Prompts       | 4     | OSMO training submission, LeRobot pipeline, dataviewer workflows                 |
-| Skills        | 15    | Seven committed domain skills and eight runtime-provisioned RPI skills           |
+| Artifact Type | Count | Purpose                                                                      |
+|---------------|-------|------------------------------------------------------------------------------|
+| Agents        | 2     | OSMO training manager, dataviewer developer                                  |
+| Instructions  | 5     | Four committed instructions and runtime-provisioned RPI tracking conventions |
+| Prompts       | 4     | OSMO training submission, LeRobot pipeline, dataviewer workflows             |
+| Skills        | 15    | Seven committed domain skills and eight runtime-provisioned RPI skills       |
 
 Project artifacts are auto-discovered by VS Code from the `.github/` directory without explicit registration.
 

docs/reference/copilot-artifacts.md

@@ -29,6 +29,7 @@ The cloud-agent setup workflow provisions the RPI skill suite at runtime.
 | Instruction | Commit Messages            | Conventional Commits format for all commit messages | `.github/instructions/commit-message.instructions.md`             |
 | Instruction | Dataviewer                 | Coding standards for dataviewer development         | `.github/instructions/dataviewer.instructions.md`                 |
 | Instruction | Docs Style and Conventions | Writing standards for all markdown files            | `.github/instructions/docs-style-and-conventions.instructions.md` |
+| Instruction | RPI Tracking               | Shared RPI working-artifact conventions             | `.github/instructions/hve-core/copilot-tracking.instructions.md`  |
 | Instruction | Shell Scripts              | Implementation standards for bash scripts           | `.github/instructions/shell-scripts.instructions.md`              |
 | Prompt      | `/chatlog`                 | Create and maintain conversation logs               | `.github/prompts/chatlog.prompt.md`                               |
 | Prompt      | `/check-training-status`   | Monitor OSMO training job progress                  | `.github/prompts/check-training-status.prompt.md`                 |
@@ -139,13 +140,9 @@ discovery (frontmatter only) → instructions (SKILL.md body) → resources
 
 ### rpi-* skill suite
 
-The cloud-agent setup workflow uses `gh skill install` to download eight
-explicit RPI skill paths from a pinned `microsoft/hve-core` commit into
-gitignored `.github/skills/rpi-*/` directories. Each skill is an immediate
-child of `.github/skills/`, as required for discovery. Local clones do not
-contain these skills unless the setup workflow has provisioned them. Each skill
-retains its upstream references and templates, and the GitHub CLI injects the
-source commit and tree metadata into its `SKILL.md` front matter.
+The cloud-agent setup workflow uses `gh skill install` to download eight explicit RPI skill paths from a pinned `microsoft/hve-core` commit into gitignored `.github/skills/rpi-*/` directories. It also downloads the shared `copilot-tracking.instructions.md` from the same commit into `.github/instructions/hve-core/`.
+
+Each skill is an immediate child of `.github/skills/`, as required for discovery. Local clones do not contain these runtime artifacts unless the setup workflow has provisioned them. Each skill retains its upstream references and templates, and the GitHub CLI injects the source commit and tree metadata into its `SKILL.md` front matter.
 
 | Skill               | Purpose                                             |
 |---------------------|-----------------------------------------------------|