Adapter stubs :: Toolchain Framework

An adapter stub maps an ecosystem’s existing toolkit into the Toolchain Management Protocol surface. Full generators and host lifecycle are roadmap; today stubs declare capabilities and are validated in CI.

Required fields

Field Notes

Field	Notes
`ecosystem`	Non-empty string id (e.g. `flutter`).
`protocolVersion`	Integer ≥ 1.
`capabilities`	Non-empty array of protocol behavior ids (`bootstrap`, `pin-resolve`, `health`, `repair`, `upgrade-rollback`, `surface-parity`).

ecosystem

Non-empty string id (e.g. flutter).

protocolVersion

Integer ≥ 1.

capabilities

Non-empty array of protocol behavior ids (bootstrap, pin-resolve, health, repair, upgrade-rollback, surface-parity).

Optional: displayName, entrypoint, communityBridges, notes.

Example (Flutter)

{
  "ecosystem": "flutter",
  "displayName": "Flutter",
  "protocolVersion": 1,
  "entrypoint": "",
  "capabilities": [
    "bootstrap",
    "pin-resolve",
    "health",
    "repair",
    "upgrade-rollback",
    "surface-parity"
  ],
  "communityBridges": ["fvm", "puro", "mise"],
  "notes": "Stub adapter until a first-party control plane owns pinning."
}

Place stubs under examples/ (or your repo’s adapter path) and run pnpm run validate. Partial capability lists are allowed; validate reports missing behaviors without failing on that alone—schema and shape must still pass.