Add compliance service contract

[haasonsaas]

Summary

• add the shared compliance.v1 contract for evidence packages, control coverage, gap detection, and exports
• include governance policy snapshots and approval evidence in the package payload so the service integrates with existing platform services
• wire generated Go, TypeScript, and Python outputs plus package/smoke metadata

Verification

• buf lint --path proto/compliance/v1/compliance.proto
• buf generate --path proto/compliance/v1/compliance.proto --timeout 10m
• actionlint .github/workflows/ci.yml
• go test ./... -count=1
• npm ci && npm run check:package
• python3 -m venv .venv-build && . .venv-build/bin/activate && python -m pip install --upgrade build && python -m build

[cursor]

PR Summary

Low Risk
Mostly additive schema + generated code changes; risk is limited to downstream consumers that may now rely on the new compliance.v1 types and exports.

Overview
Adds a new compliance.v1 protobuf API contract with RPCs to generate evidence packages, compute coverage, detect gaps, and export artifacts, including message types for evidence items, control coverage, and approval/governance policy snapshots.

Checks in regenerated client/server stubs for Go (including Connect handlers), TypeScript, and Python, and wires the new module into packaging/CI by adding package.json exports, tool descriptions in descriptions.yaml, and a Python wheel smoke-import assertion for EvidencePackage.

^{Reviewed by Cursor Bugbot for commit eb49952. Bugbot is set up for automated code reviews on this repo. Configure here.}