You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Apply packaged-resource boundaries to automatic discovery #437
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.
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.
Activity
chore: agent-claim #437 nonce=0f6fc8f1869090b9d6f56535d5d0d841
devantler commentedon Oct 4, 2026
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.