Gate optional dependency-aware integration

[rsolerortuno]

Closes #60.

Summary

• audits the current production scoring, ranking and profile-selection boundaries;
• verifies compatibility between the frozen universes, dependency profiles, benchmark artifacts, context and baseline ranking;
• introduces an immutable integration policy with explicit, traceable criteria;
• distinguishes synthetic fixture, local real-data and externally validated evidence scopes;
• ensures synthetic fixture evidence always blocks activation;
• evaluates benchmark coverage, holdout coverage, eligible-target count, control behaviour, stability, band violations and ablation robustness independently;
• treats unavailable criteria as non-passing;
• creates a deterministic, context-bound dependency-aware candidate profile;
• reproduces the bounded overlay while retaining baseline scores and ranks separately;
• proves that baseline bytes, fingerprints, scores and ranks remain unchanged;
• requires explicit opt-in and future human authorization;
• creates no approved authorization;
• registers no production profile and changes no production defaults;
• produces a blocked activation-readiness bundle for the synthetic fixture;
• performs no network access and adds no dependencies.

Validation

• equivalent end-to-end integration runs produced byte-identical artifacts;
• integration-gate tests passed;
• baseline-preservation tests passed;
• opt-in and authorization-isolation tests passed;
• DepMap ingestion, profiles, universe and benchmark compatibility tests passed;
• full repository test suite passed;
• python -m targetintel.cli run --validate passed;
• git diff --check passed;
• Claude final decision: APPROVE;
• AGY advisory audit: SKIPPED_ERROR_126;
• final test exit code: 0;
• final process exit code: 0.

Fixture decision

The synthetic fixture is intentionally blocked:

• evidence scope: synthetic_fixture;
• integration state: blocked_fixture_evidence;
• activation status: blocked;
• human review required;
• baseline production default unchanged;
• no approved authorization emitted.

Boundaries

Issue 506 creates only an isolated and optional integration boundary.

It does not activate a dependency-aware production profile, modify TargetIntel
scores or ranks, register a global profile, establish clinical validity or
authorize therapeutic target selection.

Issue 507 must execute the complete workflow with real local data and still
requires explicit human review.