Skip to content

Annotate surviving specifics and widen the portability gate #15732

Open
0 of 2 issues completed
Open

Description

@kyle-sexton

Parent

Refs #15703
Source: PLAN Phase 15, topic ecosystem-specifics

Depends on

Outcome

A pull request that adds a model-read tool, library or command choice to a generic skill, agent or plugin-level reference or context file fails the portability gate, so the cut guidance cannot grow back. Surviving specifics carry an annotation naming the rule that keeps them.

Demo: stage a tool literal in an agent file and in a plugin-level reference file; the portability gate fails each, and passes once the line is annotated. On main, the gate's full audit passes.

What changes:

  • Every declared-scope file lacking a portability-scope: line gets one; every surviving specific kept under the design's rules R2, R6, R8, R9 or R10 in a skill body gets portability-ok: <rule id and reason>.
  • The portability gate's scope and its in-script path filter widen from skill files to agents and plugin-level context and reference files.
  • The gate's token list: enable the staged literals one at a time, and add one literal per tool named in a cut row, each only when its own full audit is green; the comment names the ecosystem-resolution contract as the fix.

Method: tests first in the gate's own test suite: an agent file and a plugin-level reference file with a staged literal each fail; an annotated one passes.

Decisions

  • The gate widens last: widening before the cuts land would fail unrelated pull requests on files not yet cut. Until then the guard is the review rule.
  • D18: a check's output names the fix; here the gate's comment names the ecosystem-resolution contract.
  • Brief finish line: merged, checked by the owner via the widened portability gate passing on main and the ladder contract showing the verification tier.

Key interfaces

  • "The consumer's ecosystem (language, framework, tools): abstract now. Seam: the ecosystem-resolution contract and the consumer's own records."

Done when

  • AC1: no generic skill ships a model-read tool, library or command choice outside the named exceptions, and the portability gate, widened to agents and plugin-level reference and context files, passes on main.
  • The gate's test suite passes, including the agent-file and reference-file failure cases.
  • The ladder contract shows ### Tier 3: Verification (the Brief's finish line).
  • The pull request body names this repository's dogfooding step.
  • AC7: nothing is cut here, so no control result is owed.
  • AC10: no new enforcement-placing skill is added here.

Out of scope

  • Cutting guidance (the per-plugin items).
  • Any new rule beyond the widened scope and the literals.

Activity

  1. added
    agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.
    on Nov 12, 2026
  2. added theissue type on Nov 12, 2026
  3. github-actions commented on Nov 13, 2026

    @github-actions
    Contributor

    Size: Large
    Complexity: Medium
    Uncertainty: Knowable
    Flags: none
    Blocked by: #16752, #16755, #16756, #16758, #16760, #16762, #16765, #17731, #17733, #17739, #17740, #17741, #17743, #17744
    Blast radius: the portability gate, its test suite and its token list, plus portability-scope: and portability-ok: annotations across skills, agents and plugin-level reference files. Every pull request touching those files runs the gate.
    Reversible: yes; revert the pull request, which restores the narrower gate scope and removes the annotations.
    Open questions: none

    I read this as a Task: widen the portability gate from skill files to agents and plugin-level reference and context files. The same change annotates the surviving specifics, so that a tool, library or command literal fails the gate unless it is annotated. The issue states its own sequencing (the gate widens last, after the cuts land), the demo and the done-when items. No design choice is left open.

    The issue is blocked. The issue lane's stop comment says #15730 is not yet closed. #15730 does not appear in the open-issues list I was given. The per-plugin cut issues that #15730 files are open, and I listed them above. If I missed any, the Blocked by edges need updating as more cut items are filed.

    I found no merged pull request that already covers this.

    Automated triage. A maintainer reviews it.

  4. melodic-automation-lanes commented on Nov 14, 2026

    @melodic-automation-lanes
    Contributor

    Not admitted to the issue lane yet: Size large: the split into sub-issues at intake is pending (owner Q93).

  5. 35 remaining items

  6. melodic-automation-lanes commented on Nov 21, 2026

    @melodic-automation-lanes
    Contributor

    Split at intake (owner Q93). This issue is Size Large, so its done-when is split into 2 sub-issues, each holding its task-list lines as written.

    Automated split by the lanes App. Admission waits on this issue while a sub-issue is open; work-unblock closes it as completed once every sub-issue is closed as completed by a merge or a listed human and its done-when is covered.

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

    agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.

    Type

    Fields

    Work status

    ready

    Priority

    medium

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions