Skip to content

SDK: Publish confirmed MCP and Skill installation lifecycle bindings #2720

Description

@gokhanarkan

Tracking consolidated

Remaining in-scope work is tracked in Data pipeline: catalogue, authentication and SDK, one of the four direct workstreams in epic #1230.

Closed as not planned for this separate tracker, not as implemented or delivered. This removes duplicate/nested tracking; the remaining requirements move to the workstream checklist. Existing history and implementation evidence are preserved below.

Previous scope and evidence

Parent: https://github.com/github/copilot-ecosystem/issues/1233
Epic: https://github.com/github/copilot-ecosystem/issues/1230

Target: 2 October 2026 (unchanged epic target).

Outcome

App and other SDK consumers can transport the runtime-owned, explicitly confirmed MCP and complete Skill installation lifecycles through verified generated SDK packages.

Dependencies

  • Concrete MCP confirmation/apply/uninstall and recovery: github/copilot-agent-runtime#16829.
  • Complete immutable Skill planning/apply/uninstall contracts under github/copilot-agent-runtime#13837.
  • Canonical CLI/runtime artefacts actually containing those operations and schemas.

Acceptance criteria

  • Consume the implemented runtime contracts through the official checksum-verified CLI dependency update/code-generation workflow, reusing valid existing update work.
  • Preserve explicit plan/choice/payload/confirmation binding, secure-value transport, typed auth/policy/drift/replay/expiry/recovery outcomes and resource-specific distinctions.
  • Keep SDKs thin: no network policy, resource downloading, planning, configuration/secret writes or plan-and-apply convenience wrapper.
  • Validate all supported generated SDKs and record semantic round-trip and actual package smoke evidence for the supported operations.
  • Publish through normal reviewed release workflows and document exact minimum runtime/SDK versions and App pin handoff.
  • Document explicit confirmation, cancellation, secret handling, activation/recovery and uninstall, including unsupported older runtimes.

Scope separation

#2389 retains its original stable search/planning evidence bar. #2719 delivers the already-merged selection/pagination/Plugin contracts and must not wait for these future installation operations. This issue is the later installation release, not hand-authored bindings or a reason to block same-repo runtime/CLI development.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions