Repository navigation
Require a text marketplace identifier in the packaging gate #419
Description
🤖 Generated by the Agentic Engineer
Problem
The real packaging gate accepts a numeric marketplace name (name: 7). Both mirrored manifests are identical, so parity cannot detect an unusable marketplace identifier.
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
Reject non-string, blank or unsupported marketplace names at the package boundary, while current healthy marketplace names remain valid.
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 #419 nonce=c3a218f8962e602cc3cbf6feed094632
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.