Repository navigation
Validate plugin descriptions as visible text rather than JSON length #421
Description
🤖 Generated by the Agentic Engineer
Problem
The real gate accepts numeric and whitespace-only plugin descriptions when matching marketplace entries carry the same value. jq length does not prove that a consumer receives a usable textual description.
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 nonblank strings for package and marketplace entry descriptions, retain ordinary Unicode text, and test non-string and blank descriptions.
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 #421 nonce=a149e91bf78192d0136b242f9a8403fc
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.