linear-validate-feature

To validate an OpenSpec feature branch, run a full validation pipeline that deploys the service locally using Docker-Compose and executes smoke, e2e, security, and spec compliance checks to generate a structured validation report.

Automated feature validation for deployment readiness is the process of deploying a feature locally and running pytest smoke suites, Playwright e2e tests, and security scans to verify functional correctness and security posture before merging.

Yes, Docker and docker-compose are required to start the service locally with DEBUG logging before running e2e and security scans. You also need Python, pytest, and httpx to execute the validation pipeline.

Yes, the validation pipeline runs OWASP Dependency-Check and ZAP security scans against the live local deployment to assess the security posture of the feature branch before generating a structured validation report.

To check OpenSpec compliance and GitHub CI status, the validation pipeline validates flow diagrams against the OpenSpec change, verifies spec compliance, parses service logs, and reports the GitHub CI status before posting the report to the PR.

The best way to automate feature validation and compliance is to invoke a full pipeline that deploys the feature locally, runs pytest and Playwright tests, executes security scans, and verifies architecture and spec compliance to produce a structured report.