Repository navigation
feat(deps): exact per-edge skills x targets pairing for diamonds (req-rs-018) - #3769
Conversation
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
There was a problem hiding this comment.
🟡 Changes recommended
Direct construction accepts empty or unnormalized selection axes that can change meaning or fail validation after a lock round trip.
2 open issues
What changed in this PR
This PR provides the spec-first foundation for #3763: exact per-edge skill/target pairing for dependencies reached through multiple parents. It adds the selection algebra and lock-record codec; integration into install and other lifecycle operations remains deferred.
Changes:
- Proposes
req-rs-018for exact pairing, deterministic lock recording, consistency checks, and frozen replay. - Adds canonical selection merging and serialization with property and conformance tests.
- Updates requirement metadata, generated conformance reports, and the changelog.
| File | Description |
|---|---|
tests/unit/models/test_subset_pairing_properties.py |
Tests merge laws, exact pairing, and lock round trips. |
tests/spec_conformance/test_subset_merge_reqs.py |
Binds selection-algebra tests to req-rs-018. |
src/apm_cli/models/dependency/subsets.py |
Adds canonical pairing algebra and lock-record encoding/decoding. |
docs/src/content/docs/specs/openapm-v0.1.md |
Defines the proposed requirement and pairing format. |
docs/public/specs/manifests/openapm-v0.1.requirements.yml |
Registers the new consumer requirement. |
CONFORMANCE.md |
Updates the requirement table and coverage count. |
CONFORMANCE.json |
Records new test bindings and requirement totals. |
CHANGELOG.md |
Announces the proposal and notes deferred install integration. |
Review effort: Balanced
Pin the canonical subset_pairings ordering comparison, scope the determinism claim to data structures, exclude req-ext-001 vendor keys from pairing elements, clarify the wildcard element and the 'any edge' quantifier, add the Section 11.2 disclosure pointer and the Section 10.11 lockfile-tampering mapping, and type target_subset and subset_pairings in the distinct proposed lockfile-v0.1.60.schema.json (earlier schema bytes unchanged). Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
APM Spec Guardian:
|
| Panel | Stance | Shocked | New B | New R | New N |
|---|---|---|---|---|---|
| Swagger / OpenAPI editor | ship_with_followups | 8/10 | 0 | 3 | 2 |
| OCI distribution editor | ship_with_followups | 8/10 | 0 | 2 | 2 |
| Package-manager registry-contract editor | ship_with_followups | 8/10 | 0 | 2 | 2 |
| TAG architect | ship_with_followups | 8/10 | 0 | 3 | 2 |
B = new blocking findings, R = new recommended, N = new nits.
Counts are signal strength, not gates. The maintainer ships.
Convergent themes (flagged by 2+ panels)
- T1 -- Lockfile schema materialization for target_subset and subset_pairings (supporting: sw-rec-r1-1, sw-rec-r1-2, oci-rec-r1-1, pkg-rec-r1-2, tag-rec-r1-2)
- T2 -- Pin element-ordering comparison for targets lists in the canonical form (supporting: sw-rec-r1-3, pkg-rec-r1-1)
- T3 -- Canonical-form prose is dense; pseudocode would help implementers (supporting: pkg-nit-r1-2, tag-nit-r1-1)
- T4 -- 'merge behaviour' -> 'merge behavior' (supporting: pkg-nit-r1-1, tag-nit-r1-2)
Fold now (6 item(s))
- [F1 / T4] Appendix D (0.1.60 row) -- Replace 'behaviour' with 'behavior'. (folded)
- [F2 / T2] 7.4.1 canonical form -- Order elements lexicographically by their
targetslists (element-wise ascending code-point comparison; a shorter list sorts before a longer list it prefixes). (folded) - [F3] 7.4.1 canonical form -- 'serialize to identical bytes' -> 'canonicalize to identical data structures'. (folded)
- [F4] 7.4.1 clause 4 -- 'when an edge selects all' -> 'when any edge selects all'. (folded)
- [F5] 7.4.1 canonical form -- Exclude req-ext-001 vendor keys from
subset_pairingselements: writers MUST NOT emit them; readers treat them as malformed under clause 5 (matches the reader). (folded; interpretive, count stays 139) - [F6] 7.4.1 canonical form -- Restate the wildcard element in terms of the derived selection, not a single edge. (folded)
Defer to v0.1.1
- [F7 / T1] Appendix A + new schema -- Distinct proposed
lockfile-v0.1.60.schema.jsontypingtarget_subsetandsubset_pairings. (folded anyway) - [F8] 10.11 row 4 -- Map lockfile tampering of subset-selection scope to req-rs-018. (folded anyway)
- [F9] 7.4.1 / 11.2 -- Optional-feature disclosure pointer, matching req-mf-025 / req-lk-023. (folded anyway)
- [F10 / T3] 7.4.1 (informative) -- Pseudocode for the canonical form. (deferred)
Rejected findings
- oci-nit-r1-2 -- The missing
targetsrow in Section 4.3.2 predates this PR, and the panelist proposed no fix.
Linter notes (1 check(s) flagged)
- [11]
.pyfiles changed: expected. This PR ships the req-rs-018 owner algebra and its tests alongside the spec text, so the Python lint chain was run instead (ruff 0.15.12 check/format, pylint R0801, architecture boundaries: all pass).
Checks 1-10 pass. Check 7 lists two unresolved anchors (424-default_host, 56-git-semver-...) that already fail on main (the underscores trip the slug heuristic).
Full per-panel findings
Swagger / OpenAPI editor -- shocked_meter 8/10, confidence high
Summary: Well-drafted amendment with clean normative structure, consistent counts, correct conformance class and accurate cross-references. The main contract gap is that the lockfile schemas type skill_subset but not target_subset or subset_pairings. The canonical form would benefit from a machine-readable fragment and an explicit comparison function.
New recommended findings (3)
- [sw-rec-r1-1] sec.5.2 / lockfile schemas -- Type the new fields in the lockfile schema.
- [sw-rec-r1-2] sec.7.4.1 -- Add a machine-readable fragment for the canonical form.
- [sw-rec-r1-3] sec.7.4.1 -- Pin the element ordering comparison.
New nit findings (2)
- [sw-nit-r1-1] The wildcard-element sentence mixes up edges and canonical elements.
- [sw-nit-r1-2] Clause 4: 'an edge' -> 'any edge'.
OCI distribution editor -- shocked_meter 8/10, confidence high
Summary: The pairing algebra, canonical form and consistency/frozen-replay defenses are well specified. Follow-ups: add the new fields to the lockfile schema, and acknowledge deployment-scope tampering in Section 10.11.
New recommended findings (2)
- [oci-rec-r1-1] lockfile schema / 5.2 -- Type
target_subsetandsubset_pairings(minItems 1, additionalProperties false). - [oci-rec-r1-2] 10.11 / 10.4 -- A self-consistent edit of the three fields is not hash-covered. The defenses are re-derivation outside frozen mode and the clause-6 frozen gate; map them in 10.11.
New nit findings (2)
- [oci-nit-r1-1] 'identical bytes' overclaims; YAML style is not pinned.
- [oci-nit-r1-2] 4.3.2 has no
targetsrow (pre-existing).
Package-manager registry-contract editor -- shocked_meter 8/10, confidence high
Summary: Solid lockfile-determinism amendment. One ordering comparison needed pinning, frozen replay is gated correctly, and the backward-compatibility fallback is documented. The missing schema identity is inconsistent with precedent.
New recommended findings (2)
- [pkg-rec-r1-1] 7.4.1 -- Pin the targets-list comparison.
- [pkg-rec-r1-2] Appendix D / schema policy -- Select a distinct lockfile schema identity, or explain why none is selected.
New nit findings (2)
- [pkg-nit-r1-1] 'behaviour' spelling.
- [pkg-nit-r1-2] Canonical form is dense; an example or pseudocode would help.
TAG architect -- shocked_meter 8/10, confidence high
Summary: Well-defined algebra and a clean machine-readable surface. Two follow-ups: the byte-identity claim needs a carve-out from req-ext-001 inside pairing elements, and the lockfile schemas should document the new fields.
New recommended findings (3)
- [tag-rec-r1-1] 7.4.1 / req-ext-001 -- Exclude vendor keys from pairing elements.
- [tag-rec-r1-2] Appendix A -- Add the fields to the lockfile schema.
- [tag-rec-r1-3] 7.4.1 / 11.2 -- Add the optional-feature disclosure pointer.
New nit findings (2)
- [tag-nit-r1-1] Pseudocode for the canonical form.
- [tag-nit-r1-2] 'behaviour' spelling.
This panel is advisory. It does not block merge. Re-apply the spec-review label after addressing feedback to re-run.
…ction fields (#3769) Address Copilot review: direct SkillTargetSelection construction now rejects empty, blank or padded axes that would change meaning after a lock round trip, and req-rs-018 clause 3 scopes the identity requirement to skill_subset, target_subset and subset_pairings rather than the whole entry (depth may legitimately change). Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Pin the canonical subset_pairings ordering comparison, scope the determinism claim to data structures, exclude req-ext-001 vendor keys from pairing elements, clarify the wildcard element and the 'any edge' quantifier, add the Section 11.2 disclosure pointer and the Section 10.11 lockfile-tampering mapping, and type target_subset and subset_pairings in the distinct proposed lockfile-v0.1.60.schema.json (earlier schema bytes unchanged). Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
769ede5 to
1e79118
Compare
…ction fields (#3769) Address Copilot review: direct SkillTargetSelection construction now rejects empty, blank or padded axes that would change meaning after a lock round trip, and req-rs-018 clause 3 scopes the identity requirement to skill_subset, target_subset and subset_pairings rather than the whole entry (depth may legitimately change). Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
…rozen tests (#3769) Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
997cf4c to
0fb2ceb
Compare
Pin the canonical subset_pairings ordering comparison, scope the determinism claim to data structures, exclude req-ext-001 vendor keys from pairing elements, clarify the wildcard element and the 'any edge' quantifier, add the Section 11.2 disclosure pointer and the Section 10.11 lockfile-tampering mapping, and type target_subset and subset_pairings in the distinct proposed lockfile-v0.1.60.schema.json (earlier schema bytes unchanged). Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
…ction fields (#3769) Address Copilot review: direct SkillTargetSelection construction now rejects empty, blank or padded axes that would change meaning after a lock round trip, and req-rs-018 clause 3 scopes the identity requirement to skill_subset, target_subset and subset_pairings rather than the whole entry (depth may legitimately change). Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
…rozen tests (#3769) Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
APM Review Panel:
|
| Persona | B | R | N | Takeaway |
|---|---|---|---|---|
| Python Architect | 0 | 0 | 0 | The pairing has one clean owner; the canonical form, both guards, and every lifecycle path route through subsets.py. |
| Test Coverage Expert | 0 | 2 | 0 | Algebra and lifecycle coverage is strong; the shared-root union and CLI overlay gaps are now folded with tests. |
| DevX UX Expert | 0 | 0 | 0 | Error messages are actionable, the lockfile change is additive and minimal-churn, and upgrading takes one command. |
B = blocking-severity findings, R = recommended, N = nits.
Counts are signal strength, not gates. The maintainer ships.
Recommendation
Panelists returned no required findings. Both test-coverage gaps were folded with passing tests in the head commit, and the spec-guardian panel concurs at 8.0/10. The inherited base-stack issues are tracked outside this PR. Merge once the base stack (#3760, #3786) lands and this PR is retargeted to main.
Full per-persona findings
Test Coverage Expert (folded in caabc09)
- [recommended]
_paired_name_filtershared-root union path untested -- copilot and cursor both deploy to.agents/skills. Folded:tests/unit/integration/test_skill_integrator_hermetic.py::TestPairedNameFilterPerSkillsRoot. - [recommended] CLI
--skilloverlay with a non-product pairing untested across deploy and lockfile. Folded:tests/unit/test_skill_subset_persistence.py::TestCliOverlayKeepsExactPairing.
Python Architect -- no findings.
DevX UX Expert -- no findings.
Generated by autopilot-pr-review-worker. This comment is AI-generated and may contain errors.
12c9a9c to
e6ffe85
Compare
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
caabc09 to
52a41a6
Compare
Pin the canonical subset_pairings ordering comparison, scope the determinism claim to data structures, exclude req-ext-001 vendor keys from pairing elements, clarify the wildcard element and the 'any edge' quantifier, add the Section 11.2 disclosure pointer and the Section 10.11 lockfile-tampering mapping, and type target_subset and subset_pairings in the distinct proposed lockfile-v0.1.60.schema.json (earlier schema bytes unchanged). Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
…ction fields (#3769) Address Copilot review: direct SkillTargetSelection construction now rejects empty, blank or padded axes that would change meaning after a lock round trip, and req-rs-018 clause 3 scopes the identity requirement to skill_subset, target_subset and subset_pairings rather than the whole entry (depth may legitimately change). Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
…rozen tests (#3769) Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Replacement replay keeps the binding's merged flat selection (#3786 re-merges request evidence) and only carries the exact pairing; the replay pairing helper reads subset_pairings directly so the lock consumer contract covers the new field; services.py stays within its LOC budget. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Add the OpenAPM req-rs-018 subset-merge requirement (new Section 7.4.1): multi-edge skills x targets selections merge by exact per-edge pairing, all absorbs per edge and axis, order independence, lock recording via the canonical optional subset_pairings field, consistency and frozen replay. Appendix C/D, enumerations, counts (139: 134 MUST) and the requirements manifest are updated; CONFORMANCE regenerated. Add the pure pairing algebra to the selection owner (models/dependency/subsets.py): SkillTargetSelection, merge_edge_pairings, and the lock record codec, with hypothesis property tests and req-rs-018 conformance tests. Partial: #3763 Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Pin the canonical subset_pairings ordering comparison, scope the determinism claim to data structures, exclude req-ext-001 vendor keys from pairing elements, clarify the wildcard element and the 'any edge' quantifier, add the Section 11.2 disclosure pointer and the Section 10.11 lockfile-tampering mapping, and type target_subset and subset_pairings in the distinct proposed lockfile-v0.1.60.schema.json (earlier schema bytes unchanged). Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
…ction fields (#3769) Address Copilot review: direct SkillTargetSelection construction now rejects empty, blank or padded axes that would change meaning after a lock round trip, and req-rs-018 clause 3 scopes the identity requirement to skill_subset, target_subset and subset_pairings rather than the whole entry (depth may legitimately change). Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
…ng (#3763) Each skill a declaration selects now reaches only that declaration's targets (OpenAPM req-rs-018) instead of the 0.36.1 skills x targets cross-product. The selection-merge owner (models/dependency/subsets.py) computes NodeSelection through merge_edge_pairings; the resolver carries the exact pairing on DependencyReference.subset_pairings; the lockfile records it as the optional canonical subset_pairings field only when the flat product would over-select (so product lockfiles stay byte-identical) and decodes it only through SkillTargetSelection.from_lock_fields. effective_dependency_selection hands skill_pairing to every integrate_package_primitives call (install, audit replay, uninstall survivors, local content) and the skill integrator narrows each skills root to the skills paired with its targets. Uninstall shrink, audit skill-subset-consistency and a new pre-deploy InstallService.enforce_frozen_selections compare through the owner, so a 0.36.x cross-product lock fails --frozen with a named reason before anything deploys. The selection-merge guard now requires the pairing on every deploy call and site; a parametrized mutation test proves it. Fixes #3763 Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Fold python-architect review: a replacement-bound lock entry now replays the locked skill_subset, target_subset and subset_pairings instead of the rule's original edge, and a CLI --skill overlay that widens a product selection clears any stale subset_pairings. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
…uite (#3763) PR-3 replaced its diamond lifecycle file with test_skill_selection_merge_lifecycle.py; carry the exact-pairing scenarios there (both declaration orders with byte-identical locks, absorb on one harness only, cross-product lock refused by --frozen and audit before deploy, uninstall shrink) and drop the resurrected file. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
…rozen tests (#3769) Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
…ngs (#3763) Fold test-coverage panel findings: copilot and cursor share .agents/skills, so the per-root filter must take the union of their paired skills; and a --skill overlay on a non-product pairing must widen every selected target identically in deploy and in the lockfile. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
…election (#3763) Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
…real lock entries (#3763) Align the pairing owner with #3786's explicit-empty rule: an edge whose skills: or targets: is explicitly empty contributes no skill-target pairs, and a node whose every edge is empty keeps the empty flat selection (NodeSelection.lock_selection reconciles audit and uninstall). effective_dependency_selection only treats a decoded SkillTargetSelection as a pairing, and the #3784 lockfile overlay test uses LockedDependency. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Replacement replay keeps the binding's merged flat selection (#3786 re-merges request evidence) and only carries the exact pairing; the replay pairing helper reads subset_pairings directly so the lock consumer contract covers the new field; services.py stays within its LOC budget. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
#3769) Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
9f3524e to
66929b6
Compare
…3891) * test: realign daily release smoke tests with 0.37 contracts (#3885) - retained-lock-keys mutation targets install/orphans.py, where the expected-path selector moved in #3879/#3882 - locked-skill-subset rule requires skill_subset=sorted(self.skill_subset) as one fragment; _replay_pairing(self.skill_subset, ...) from #3769 satisfied the old split needles, so the mutation went undetected - install --dry-run bootstrap previews targets and writes no apm.yml (#3865) - pack docs pointer is the install-patterns page (#3865) - finalize imports _rich_success from the console owner (#3879) - audit JSON contract tests parse stdout; the target: deprecation warning goes to stderr and is emitted once per process Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> * docs(changelog): reference #3891 Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> * test: pin COLUMNS for wrap-sensitive smoke assertions Rich wraps CliRunner output at the terminal width, so on a narrow console the dry-run target preview and the pack docs URL split across lines and the assertions fail although the output is correct. Pass a wide COLUMNS per invoke, as other integration tests do. Addresses Copilot inline on test_pack_ux_e2e.py:362 and test_wave7_marketplace_install_coverage.py:1013. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> --------- Co-authored-by: danielmeppiel <danielmeppiel@users.noreply.github.com> Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>


Description
TL;DR. When several manifests narrow one dependency with different
skills:andtargets:, each skill now reaches only the harnesses its own declaration selected, never the cross-product. Example:alphafor Claude andgammafor Copilot now land in.claude/skills/alphaand.agents/skills/gammaonly. The same owner drives install,apm.lock.yaml, audit, uninstall shrink and--frozen. OpenAPM gets a normative rule for it: the proposedreq-rs-018.Fixes #3763
Fixes #3735
Note
Stacked on #3786 (T4 PR-3, per-field union owner for #3735), which sits on #3760. The base is
danielmeppiel-t4-3735-selection-merge. It retargets tomainonce those land.Problem (WHY)
A -> bundle skills:[alpha] targets:[claude]andB -> bundle skills:[gamma] targets:[copilot], both skills deploy to both harnesses.skill_subsetonly as "Selected skill names". Another consumer could keep one edge or union the fields, and stay silent either way.--frozencould not tell the exact plan from the over-approximation.Approach (WHAT)
[req-rs-018]: exact pairing, all absorbs per edge and per axis, order and depth independence, canonicalsubset_pairings, consistency, frozen gate. Proposedlockfile-v0.1.60.schema.json; amendment row 0.1.60; count 138 -> 139.models/dependency/subsets.py: pureSkillTargetSelection/merge_edge_pairings;NodeSelection.pairing; the flat fields are its projections.subset_pairings, written only whenskill_subset x target_subsetwould over-select. Product locks stay byte-identical; locks without it replay as the product. No identity-key orlockfile_versionchange.effective_dependency_selectionreturnsskill_pairing; everyintegrate_package_primitivescall passes it. The skill integrator filters each skills root by the skills paired with its targets, taking the union when several targets share a root.skill-subset-consistency, uninstall shrink, the--skilloverlay and replacement replay all decode through the owner.InstallService.enforce_frozen_selectionsrefuses a changed or invalid selection before any deploy.install-deployment-selection-mergenow requiresskill_pairing=on every deploy call and checks the owner fragments across sites. A parametrized mutation test proves 5 bypasses are caught.Implementation (HOW)
The diagram below shows the single path from declared edges to every consumer of the selection.
deps/lockfile.py: rawsubset_pairingswith tolerant copy.selection()decodes through the owner, and a malformed or inconsistent value raises. Replay degrades an invalid value to the flat product, which is what earlier writers deployed. Replacement-bound entries now replay the locked selection.install/phases/integrate.pyandinstall/service.py: the frozen selection check runs beforerun_integration_template, so a refused frozen install writes nothing.install/phases/lockfile.py: the CLI--skilloverlay is applied as one more edge, so the recorded pairing stays consistent with the flat fields.lockfile-spec.md,manifest-schema.md,baseline-checks.md,packages/apm-guide/.../dependencies.md, CHANGELOG.Trade-offs
subset_pairingsappears only for divergent diamonds.skill_pairingwould churn about 60 unit-test call sites. The static guard enforces it on every production call.--frozenwithselection for <dep> changed. Locks that already encode the same plan (any product) replay unchanged, per brief D6.Benefits
.claude/skills == [alpha],.agents/skills == [gamma]).Issue and approved scope
Issue: Fixes #3763; Fixes #3735 (follow-up to that user issue; #3786 delivers its union half)
Human scope-approval comment: #3763 (comment)
Does this PR complete the issue, or what remains? It completes #3763's Done-when: divergent diamonds pair per harness, order-independent; the lock is byte-identical across orders; audit and uninstall agree with install; a guard and mutation test are in place; the spec requirement and conformance tests are in, and the spec panel has reviewed them (panel).
Type of change
Testing
Important
Inherited from the stack, not this diff:
tests/unit/install/test_services*.py(~36 tests) fail withintegrate_package_primitives() missing ... 'skill_subset', and the architecture linter reportsinstall-deployment-audit-replay [legacy AC4]. Both reproduce at #3786's head and are being fixed in #3760.Scenario evidence and commands
tests/integration/test_skill_selection_merge_lifecycle.py::test_divergent_skills_and_targets_pair_per_declaration[a-first,b-first]...::test_unrestricted_skills_on_one_harness_do_not_cross_to_the_other--frozenrefuses before deploy, audit fails, install converges...::test_frozen_install_rejects_a_cross_product_lock_before_deploying-g)tests/integration/test_skill_selection_merge_lifecycle.py(16 more)tests/unit/models/test_subset_pairing_properties.py(hypothesis)tests/unit/deps/test_apm_resolver_selection_merge.pytests/unit/install/test_replacement_source_consumers.py::test_replaced_dependency_replays_the_locked_skill_target_pairingtests/integration/test_architecture_owner_rule_mutations.py::test_skill_pairing_cannot_bypass_selection_owner(5 mutations)How to test:
alphaandgamma. Parent A declaresskills: [alpha], targets: [claude]; parent B declaresskills: [gamma], targets: [copilot]. The consumer targets both. Runapm install..claude/skillshas onlyalphaand.agents/skillsonlygamma, and thatapm.lock.yamlshowssubset_pairings.subset_pairingsfrom the lock:apm install --frozenfails withselection for ... changed;apm installconverges.Spec conformance (OpenAPM v0.1)
docs/src/content/docs/specs/openapm-v0.1.mdupdated(new/changed
<a id="req-XXX"></a>anchor + prose + Appendix Crow).
docs/src/content/docs/specs/manifests/openapm-v0.1.requirements.ymlupdated.
@pytest.mark.req("req-XXX")test undertests/spec_conformance/added or extended.CONFORMANCE.{md,json}regenerated viauv run --extra dev python -m tests.spec_conformance.gen_statementand committed.
Co-authored-by: Copilot 223556219+Copilot@users.noreply.github.com