Skip to content

Apply packaged-resource boundaries to automatic discovery #437

Closed

Description

@devantler

🤖 Generated by the Agentic Engineer

Problem

The package validator checks regular contained files for explicit components but automatic discovery can accept linked skill, agent and MCP resources. A discovered skill link can also bypass the regular-file provenance census. The same package boundary must apply to both discovery modes.

Proposed direction

Require automatically discovered component roots and resources to be regular contained package content before validation, catalogue counting and provenance observation. Do not follow linked resources as packaged evidence.

Acceptance criteria

  • Linked skill files/directories, agents and MCP configurations are refused in default discovery.
  • Explicit component protections remain enforced.
  • Regular automatic and explicit resources still validate.
  • Meaningful positive and negative production-validator cases run in CI.

Size: S. Part of #38.

Activity

  1. added a commit that references this issue on Oct 3, 2026
  2. moved this from 🏃🏻‍♂️ In Progress to 👀 In Review in 🌊 Project Boardon Oct 3, 2026
  3. devantler commented on Oct 4, 2026

    @devantler
    ContributorAuthor

    🤖 Generated by the Agentic Engineer

    Implemented by #443, now merged. Read back on main 2ca8f56: all 24 package-discovery regressions and complete package validation pass. The corresponding negative fixture refuses and valid consumer resources retain their identities and selections.

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

    No labels
    No labels

    Fields

    No fields configured for Security.

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions