Validate plugin manifest contracts and file structure

Catching recurring plugin-contract bugs (schema strip, action/tool mismatch, missing files, chip wiring) that occur after editing or before release.

• · vertical id (or list if args.only provided)
• · verticals directory path

• · findings array per vertical with issue, kind (missing_file, schema_strip, action_tool_mismatch, chip_wiring, seed_data_mismatch), severity, evidence
• · verdict: isReal, severity, explanation, fix

• · verticals directory structure accessible
• · manifest schema and loader files present
• · vertical configuration files exist

• · Zod schema field stripping (silently discards unknown fields, breaking contract)
• · action/tool name mismatch not caught without full simulation
• · new verticals require re-inventory (self-scaling partially mitigated)

• · dynamic discovery of verticals (self-scaling on new verticals added)
• · adversarial verification step per finding
• · specific enum of failure kinds (missing_file, schema_strip, etc.)