Phase 2: Migrate to HVE Core extension component

[coatsy]

Parent: #33
Depends on: #34

Summary

After the fork relationship is removed (Phase 1, #34), restructure this repo to contribute its agents, skills, and content as a component of the HVE Core extension (ise-hve-essentials.hve-core) instead of publishing independently under the coatsy publisher.

Context

HVE Core (ise-hve-essentials.hve-core, v3.3.101) is a VS Code extension published by ise-hve-essentials (Microsoft ISE) that bundles agents, skills, instructions, and prompts under .github/. It uses native VS Code contributes.chatAgents, contributes.chatSkills, contributes.chatPrompts, and contributes.chatInstructions — no build-time frontmatter transformation.

This repo currently publishes as coatsy.copilot-studio-skills with a build pipeline that strips Claude Code frontmatter, resolves paths, and generates package.json dynamically. Moving to the HVE Core model means adopting its conventions so the Copilot Studio content can either be folded into HVE Core directly or published as a companion extension under the same publisher.

Scope of work

1. Decide integration model

Resolve the key architectural question:

• Option A: Copilot Studio content is contributed directly into the ise-hve-essentials.hve-core extension (agents/skills added to the HVE Core repo).
• Option B: Copilot Studio content remains a separate extension but published under the ise-hve-essentials publisher, following HVE Core conventions.

2. Restructure repo layout

• Reorganise to match HVE Core conventions:
  • .github/agents/copilot-studio/ — agent .agent.md files
  • .github/skills/copilot-studio/ — skill directories with SKILL.md
  • .github/instructions/ — any instruction files (if applicable)
• Ensure all agent and skill files use native VS Code frontmatter format (no Claude Code-specific fields like allowed-tools, context, agent, argument-hint, user-invocable).
• Scripts, templates, and reference files may stay in their current locations or move as needed.

3. Eliminate build-time transformation

• Remove or simplify the frontmatter stripping step in the build pipeline — source files should already be in VS Code format.
• Remove ${CLAUDE_SKILL_DIR} path resolution — use relative paths natively.
• Skill reference auto-discovery in agents may still be useful, but evaluate whether HVE Core handles this differently.

4. Update publisher and extension identity

• Change publisher from coatsy to ise-hve-essentials (or fold into HVE Core's package.json).
• Update extension/templates/package.template.json with new publisher, repository URL, and identity.
• Determine the new extension ID (e.g., ise-hve-essentials.copilot-studio-skills).
• Publish a final version of coatsy.copilot-studio-skills that directs users to the new extension.

5. Update CI/CD pipelines

• Align build workflow with HVE Core's approach (pre-built content, minimal transformation).
• Update publish workflow to target the ise-hve-essentials publisher.
• Update or remove the extension pack (coatsy.copilot-studio-development-bundle):
  • If HVE Core bundles the content, no extension pack is needed.
  • If separate extension, create a new pack under ise-hve-essentials or add to HVE Core's extension pack.

6. Adopt HVE Core version scheme

• Decide on versioning: independent semver or aligned with HVE Core releases.
• Update VERSIONING.md and version validation workflows accordingly.
• Upstream version tracking (upstream-version.json) is retained for content sync.

7. Update documentation and clean up

• Update README.md, CONTRIBUTING.md, SETUP_GUIDE.md, VERSIONING.md.
• Remove coatsy-specific references, marketplace links, and extension pack docs.
• Add migration guide for existing coatsy.copilot-studio-skills users.

Open questions

• Option A or Option B for integration model?
• What is the ise-hve-essentials publisher's VSCE PAT provisioning process?
• Does HVE Core have a contribution guide for adding new agent/skill domains?
• Should the Copilot Studio VS Code Extension dependency (ms-copilotstudio.vscode-copilotstudio) be added to HVE Core's extension pack, or handled separately?
• How should pre-release/stable channels work for the Copilot Studio content?

Acceptance criteria

• Extension layout matches HVE Core conventions
• No build-time frontmatter transformation required
• Extension published under ise-hve-essentials publisher (or folded into HVE Core)
• All 4 agents and 33 skills registered and functional
• CI validates the built extension
• Final coatsy.copilot-studio-skills release published with migration notice
• Extension pack updated or retired
• Documentation updated with new architecture and migration guide