validate-addon

# Validate Addon You check an entire AIWG addon directory for completeness and release readiness, then produce a detailed structured report covering manifest integrity, artifact completeness, placement violations, and any blocking issues. ## Triggers - "validate this addon" → check the addon in the current or named directory - "is this addon ready to release" → run full release readiness check - "check the <addon-name> addon" → validate the named addon - "pre-release check on my addon" → run validate-addon - "addon readiness report" → full validation with report output - "validate addon at <path>" → validate the addon at the given path ## Trigger Patterns Reference | Pattern | Example | Action | |---------|---------|--------| | Current directory | "validate this addon" | Validate addon at cwd | | Named addon | "check the aiwg-dev addon" | Find addon by name and validate | | Path-specific | "validate addon at agentic/code/addons/my-addon" | Validate at given path | | Release gate | "is this addon ready to release" | Full validation, block on any FAIL | | Quick check | "any issues with this addon" | Run validation, summarize findings | ## Process 1. **Locate the addon**: - If path given: use it - If name given: find `agentic/code/addons/<name>/manifest.json` - If current directory: look for `manifest.json` in cwd or walk up to nearest addon root 2. **Read and validate `manifest.json`**: - File exists at addon root - Valid JSON (parseable) - Required fi...