Skip to content

Verify declared component paths exist and enter resource validation #425

Closed

Description

@devantler

🤖 Generated by the Agentic Engineer

Problem

The real gate accepts skills: ["./absent/"]. It counts the default skills directory despite the unresolved declared path, allowing a consumer-facing component declaration to pass without its referenced files being examined.

Observed on fresh main during hands-on validation on 2026-10-03. The package cases exercise the production gate against a complete isolated fixture; the catalogue cases exercise its shared parser and native CLI argument contract.

Intended outcome

Require declared skill directories and agent files to exist within the marketplace's canonical skills/ and agents/ layout, validate their contents, and keep catalogue and provenance checks aligned with those selections. Reject alternate layouts explicitly until their discovery and validation are extended together. Cover missing and wrong-kind targets alongside healthy explicit paths.

Success proxy: a regression fails against current main, then passes with the root-cause repair; healthy packages and normal installation remain usable. No external adoption is claimed.

Size: S. Part of #38.

Activity

  1. added theissue type on Oct 3, 2026
  2. self-assigned this
    on Oct 3, 2026
  3. added a commit that references this issue on Oct 3, 2026
  4. devantler commented on Oct 3, 2026

    @devantler
    ContributorAuthor

    🤖 Generated by the Agentic Engineer

    Delivered in #426 at merged commit 465a84f. The merged tree matches the reviewed final source. The actual merged package passes its production gate; introducing a conflicting repeated declaration into that otherwise healthy package is rejected.

    The 39 package boundary cases, 313 existing manifest cases and 25 MCP boundary cases pass, and required CI was green at the final reviewed commit. All review findings were fixed or refuted with evidence before merge.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

Fields

Priority

None yet

Effort

None yet

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions