Repository navigation
Make package validation match the resources consumers can load #436
Description
🤖 Generated by the Agentic Engineer
Evidence and problem
Hands-on production-validator fixtures reproduce six distinct gaps between declared package contents and the resources consumers can actually load. A passing catalogue or manifest comparison must cover regular contained resources, the exact selected agents, complete skill directories and every plugin directory. Literal descriptions and supported MCP names must retain their meaning through validation.
Direction and success signal
Repair the existing package validator rather than add a second package contract. Each linked defect has a positive control and an observable production-gate regression. The success proxy is correct acceptance/refusal for those fixtures, unchanged validation for the current marketplace and green current-head CI/review before merge. No new runtime permissions or automatic-release behavior are introduced.
Acceptance criteria
- The six independently reproduced current defects are corrected and verified through the production gate.
- Prior explicit component-boundary deliveries remain enforced.
- The shipped marketplace validates and all required readiness gates pass before merge.
- The merged command is exercised and linked children record their verified outcomes.
Size: M. Part of #38.
Activity
devantler commentedon Oct 5, 2026
Workstream completed. All ten native children are closed with reason completed: #424, #437, #438, #439, #440, #441, #442, #531, #532 and #536. The complete child universe was rebound immediately before this completion record, and no live conflicting parent claim exists.
The original boundary repairs remain enforced by the complete package gate and 433-case manifest regressions. The additional YAML identity repair is delivered by #533; this round delivered malformed remote URL refusal in #535 and linked/nonregular desired-state refusal with complete canonical membership in #537. Each delivery records its production-gate controls and substantive exact-head review/required CI before merge.
Actual merged-command proof: the final signed main commit 149b300 was checked out by native main run 37417456266, and Validate manifests job 112119118941 executed the complete command successfully, including the canonical desired-state document. The broader automatic main CI rerun was still running at this readback; the completion criteria here require green readiness before merge and actual merged-command evaluation, both satisfied. Linked children contain their verified delivery outcomes.