Add P1 routing contracts and P2 safety baseline

[hlinor-systems]

What changed

P1 routing contracts

• Added a controlled vocabulary for sector, stage, and ecosystem aliases at ingestion and routing boundaries.
• Added an optional source-backed provenance contract for program cards, including snapshot hash, semantic review timestamp, eligibility version, confidence, and diff-review state.
• Made runner and route-verification output explicit about deterministic policy_score semantics while keeping score for compatibility.
• Added quality.status: not_calibrated so policy scoring is not presented as empirical acceptance probability.

P2 packaging and privacy baseline

• Added pyproject.toml, uv.lock, package entry points, and the one-command repository validation gate.

• Moved CI installation to the locked uv environment.

• Added local credential scanning/redaction helpers and a documented security/privacy threat model.

• Documented the mandatory tenant, consent, retention/deletion, audit, redaction, and provider-control gates before SaaS/API work.

• Updated schemas, tests, documentation, changelog, and workboard.

Why

The review identified fragile matching, insufficient program-card provenance, ambiguous score semantics, unreproducible setup, and an insufficient privacy posture for future private projects. This patch creates explicit local contracts and blocks SaaS/API expansion until the required security controls are designed and tested. It does not invent provenance for legacy cards or claim score calibration that does not yet exist.

Validation

• 38 passed
• uv lock --check
• uv run --locked python -m runtime.check
• python3 runtime/validate_schemas.py
• python3 runtime/verify_route.py tests/cases/ai_startup.yaml --all-ai
• python3 -m py_compile runtime/*.py tests/test_p1_contracts.py
• git diff --check