Repository navigation
Require canonical stable cache versions during package validation #422
Description
🤖 Generated by the Agentic Engineer
Problem
The package validator accepts version: 7 and version: tomorrow in mirrored plugin and marketplace entries. Matching invalid values pass parity even though the repository's version tools require canonical stable versions.
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
Use the existing stable-version contract for plugin and marketplace entry versions at the package boundary. Reject non-string, malformed and out-of-range values while valid versions pass.
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.
Metadata
Metadata
Assignees
Labels
Type
Fields
Priority
Effort
Projects
- Status
Activity
chore: agent-claim #422 nonce=9805364f35087d6c32f985a11c0d1726
devantler commentedon Oct 3, 2026
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.