Skip to content

[FEATURE] OpenAPM: shared MCP attribution rule, alias/target: removal policy and schema refresh (0.1.61 follow-ups) #3880

Closed

Description

Proposals are welcome before implementation. For substantive changes, wait
for a responsible human maintainer to approve the scope and identify a review
contact. An automated recommendation, label alone, or silence is not approval.
See Contributing.

Is your feature request related to a problem? Please describe.
The apm-spec-guardian panel on #3875 (proposed OpenAPM amendment 0.1.61, #3866/#3868) returned fold_and_ship with no blockers. It deferred three spec items to a later patch revision; they are not needed for 0.1.61:

  1. Shared MCP document attribution (Section 4.5 req-mf-023 / req-mf-026, Section 8.5 / req-lk-021). copilot and claude now share the project .mcp.json. The spec keys MCP ownership by target, but on a shared document it is really keyed by destination file. Deactivating one target must not remove entries another active target still selects. The CLI already behaves this way (install/mcp/ownership.py, SHARED_PROJECT_MCP_DESTINATIONS), but no normative text states it.
  2. Removal policy for the deprecated vscode alias and singular target:. 0.1.61 announces both deprecations under the Section 9.5 window and leaves removal timing open. Decide whether the removal needs a later MINOR revision (no earlier than 0.2), and mirror that decision in Appendix E.5.
  3. Manifest JSON Schema refresh (Appendix A). The next manifest schema revision should update the targets description to mention the deprecated vscode alias, and add a deprecated annotation for vscode and target.

Describe the solution you'd like
A spec amendment drafting (1) as a normative attribution rule, plus a maintainer decision on (2), plus the schema refresh in (3). Each item should pass the apm-spec-guardian panel.

Describe alternatives you've considered
Folding these into 0.1.61. The panel kept them out because each one is new normative surface, beyond the fixed maintainer decision for #3866/#3868.

Additional context
Source: the apm-spec-guardian synthesizer on #3875 (defer_v0_1_1 items F1, F2 and F4). The deferred alias table and the related items stay in #3859.

Activity

  1. danielmeppiel commented on Nov 19, 2026

    @danielmeppiel
    CollaboratorAuthor

    Decision: approve
    Area: spec
    Scope: One OpenAPM v0.1 proposed amendment (next free 0.1.x number) that makes the shipped 0.37 behavior normative: (1) a numbered rule that MCP entry ownership in a shared MCP document is per destination file, so deactivating one target never removes entries another active target still selects (matches install/mcp/ownership.py); (2) removal policy: removing the vscode alias or singular target: requires a later MINOR revision (no earlier than 0.2) and the Section 9.5 window, mirrored in Appendix E.5, naming no APM version; (3) Appendix A manifest schema refresh: targets description mentions vscode, and deprecated annotations for vscode and target; (4) give all one meaning under targets: (the no-restriction sentinel, equal to omitting the field), scope the "union of auto-detectable targets" definition to legacy singular target: all and --target all, and state that the replacement for target: all is the explicit list. No behavior change.
    Done when: The amendment row, Appendix C rows and statement counts agree; conformance tests cover each new requirement and pass against main; CONFORMANCE regenerated; apm-spec-guardian panel comment posted with fold_and_ship and zero blockers; linter checklist passes.
    Out of scope: Removing vscode or target:; changing what targets: [all] or target: all deploy.
    Review contact: Daniel Meppiel (@danielmeppiel)

  2. danielmeppiel commented on Nov 19, 2026

    @danielmeppiel
    CollaboratorAuthor

    Decision: approve
    Area: spec
    Scope: Supersedes the earlier record on this issue (pruned by Daniel, 2026-11-19). Add only the normative text the spec needs to match shipped behavior: MCP entry ownership in a shared MCP document (the project .mcp.json shared by copilot and claude) is per destination file, so deactivating one target never removes entries another active target still selects (install/mcp/ownership.py). The alias/target: removal policy, the schema refresh and the all semantics are not planned.
    Done when: One amendment row with matching Appendix C and statement counts; a conformance test that passes on main; CONFORMANCE regenerated; apm-spec-guardian comment with fold_and_ship and zero blockers.
    Out of scope: Removal policy, schema changes, behavior changes.
    Review contact: Daniel Meppiel (@danielmeppiel)

  3. danielmeppiel commented on Nov 19, 2026

    @danielmeppiel
    CollaboratorAuthor

    Decision: approve
    Area: project
    Scope: Supersedes the earlier record on this issue (pruned by Daniel, 2026-11-19). Add only the normative text the spec needs to match shipped behavior: MCP entry ownership in a shared MCP document (the project .mcp.json shared by copilot and claude) is per destination file, so deactivating one target never removes entries another active target still selects (install/mcp/ownership.py). The alias/target: removal policy, the schema refresh and the all semantics are not planned.
    Done when: One amendment row with matching Appendix C and statement counts; a conformance test that passes on main; CONFORMANCE regenerated; apm-spec-guardian comment with fold_and_ship and zero blockers.
    Out of scope: Removal policy, schema changes, behavior changes.
    Review contact: Daniel Meppiel (@danielmeppiel)

  4. added a commit that references this issue on Nov 19, 2026
    f52280c
  5. added a commit that references this issue on Nov 19, 2026
    92f5274
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    status/acceptedHuman scope approval; verify the issue's approval record and review contact before work.type/featureNew capability, new flag, new primitive.

    Type

    No type

    Projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions