[v0.4.0·M6] Pre-release aggregate gate — verify all gates pass before tagging #660

Task

Run a pre-release aggregate gate to verify all conditions are met before creating the v0.4.0 tag. This is the final go/no-go checkpoint.

Gate checklist

Code quality

• ruff check src/ — zero errors
• mypy src/ — zero errors
• pytest tests/ --cov=src/ — 100% pass, coverage >95%
• 3 consecutive CI runs green

Security

• truffleHog scan clean
• Dependency audit zero known vulns
• No hardcoded secrets in dashboard/fleet/integration code
• OpenSSF scorecard passing

Documentation

• README updated for v0.4.0
• CHANGELOG complete
• Release notes written
• SECURITY.md updated
• CONTRIBUTING.md updated
• User guide updated
• Architecture docs updated
• Design docs updated (fleet, dashboard, matching, integrations)
• API reference current

Packaging

• PyPI build succeeds
• TestPyPI install verified
• Docker multi-arch build succeeds
• Homebrew formula ready (but not published until after tag)

Version consistency

• pyproject.toml version = 0.4.0
• __init__.py version = 0.4.0
• All Dockerfiles reference v0.4.0
• docker-compose.yaml references v0.4.0
• No stale 0.3.0 references in source (except historical changelog)

Previous milestones

• v0.4.0-M1: Deep Integrations — all issues closed
• v0.4.0-M2: Observability & Analytics — all issues closed
• v0.4.0-M3: Advanced Matching & Extraction — all issues closed
• v0.4.0-M4: Multi-Agent & Fleet — all issues closed
• v0.4.0-M5: Field Test — all issues closed
• All M1-M5 exit gates satisfied

Release preparation

• All M1-M5 changes merged to main
• All M6 release-readiness changes PR'd and reviewed
• Final PR merged to main (issue [v0.1.0] M3: Serialization & Config — 3.4 Environment variable support #16)
• main branch CI green on latest commit

Execution

Create a gist or issue comment documenting gate results:

echo "# v0.4.0 Pre-Release Aggregate Gate" > /tmp/aggregate-gate.md
echo "Date: $(date)" >> /tmp/aggregate-gate.md
echo "" >> /tmp/aggregate-gate.md
echo "## Results" >> /tmp/aggregate-gate.md
# For each item above, add a checkbox result

If any gate fails, file a follow-up issue and the release is blocked until resolved.

Action

• Run all checks above
• Document results
• If all green: proceed to tagging (issue [v0.1.0] M2: Core Data Models — 2.6 Define ConflictReport dataclass #12)
• If failures: file issues and postpone release