Tracking Issue: deterministic Agent distributions from one canonical plugin

Goal

Use one canonical PowerContext Agent Plugin as the hand-maintained source for shared Skill, MCP, plugin metadata, and naming. Generate deterministic host distributions from that source.

This tracker owns source layout, target projection, generated artifacts, migration, and drift prevention. #1352 is the parent roadmap, and #1244 established the reusable packaging baseline.

Existing ownership

• #1338 defines capability requirements; #1357 owns the machine-readable integration manifest.
• #1362 owns lifecycle semantics and host behavior.
• #1378 fixes explicit memory routing in the project-context Skill. The accepted fix should enter the canonical Skill source.
• #1397 owns reviewed Skill package lifecycle; #1301 owns multi-host installation.

Tracking

• Record the source model, naming, generated-file policy, and compatibility policy in an RFC.
• Add the canonical Agent Plugin source and a validated target-adapter schema that consumes or checks #1357.
• Implement deterministic build, build --target, and check commands.
• Standardize plugin, Skill, MCP server, and tool names, with explicit compatibility windows for legacy names.
• Migrate maintained distributions without changing native runtime behavior or existing installation paths.
• Add focused tests, packaging smoke tests, CI drift checks, and maintained documentation.
• Remove duplicate hand-maintained sources only after every maintained distribution is generated and verified.

Completion criteria

One command produces every maintained distribution from the canonical source. Names, versions, and MCP identity remain consistent. check detects drift and invalid outputs. Unsupported host capabilities fail or degrade explicitly.

Non-goals

• A universal lifecycle hook API or equal tool counts across hosts.
• Generated native runtime logic or publication of managed Skill packages.
• Automatic host installation or a public plugin compiler SDK.

Start by reading the parent roadmap #1352 and packaging baseline #1244, then review the ownership issues #1357, #1362, #1378, #1397, and #1301. Define the RFC and canonical source model before implementing deterministic build and check commands. Done means maintained distributions are generated and verified, names and MCP identity stay consistent, drift is detected, and unsupported capabilities fail or degrade explicitly.