speckit.validatelisted

## 🎯 Mission Check whether the ENTIRE implementation meets spec.md or not — final gate before deploying. ## 📥 Input - All artifacts: spec.md, plan.md, tasks.md - Source code (implementation) - `.agent/memory/constitution.md` - `.agent/project.json`, dependency manifests, and documented verification commands ## 📋 Protocol 1. **Tasks Completion**: All tasks in tasks.md have `[X]` ? 2. **Success Criteria**: All SCs in spec.md passed? 3. **Capability Discovery**: - Detect project type, language, package manager, containerization, configured services, build/test commands, and health checks. - Produce an applicability table. A non-applicable check is `N/A`, not PASS. 4. **Build Verification** (MUST run applicable commands): - Run the repository-defined build/type/lint commands. - Use the matching container service when the constitution requires Docker. - For non-Docker projects, use the documented project runtime. - Any applicable build failure → ❌ BLOCKED. 5. **Runtime Verification** (when the project has a runtime): - Start the documented runtime or discovered Compose configuration. - Wait using health/retry behavior with a bounded timeout; do not use a fixed sleep as proof of readiness. - Inspect failing service/application logs immediately. 6. **Health Check** (when configured): - Read health endpoints and ports from project configuration or environment. - Verify the expected status/body. Do not assume web/admin/API services. 7. *