Build Week: Promote correlated incident lifecycle to main

[CodeBuildder]

Summary

Promotes the tested cross-agent correlation engine and evidence-to-recovery timeline onto main after the unified command center merged in #51.

Correlation integrity

Sentinel creates a case only when the same explicit correlation_id appears on both Argus and Phoenix evidence. Similar timestamps, resources, or severity never fabricate an incident relationship. Standalone findings remain evidence and do not affect incident counts.

Changes

• normalizes observed, replayed, simulator, and live Chaos Mesh provenance
• creates ordered cases from explicit cross-agent identity
• preserves existing SOG incidents without duplication
• exposes case status, severity, sources, evidence count, provenance, and lifecycle
• renders an inspectable evidence-to-recovery timeline
• normalizes structured Argus assessments into safe readable summaries
• tests correlated and standalone evidence behavior

Live proof

The actual Argus and Phoenix producer clients published two explicitly non-live records with correlation ID build-week-case-20260718. Sentinel produced exactly one resolved critical case with:

• sources: argus, phoenix
• evidence records: 2
• provenance: replayed, simulator

Verification

• Sentinel backend: 5 passed
• TypeScript compilation and Vite production build: passed
• Argus producer tests: 11 passed
• Phoenix Chaos tests: 58 passed
• Phoenix World Model contract test: passed

Related producer PRs: CodeBuildder/argus-k8s#109 and CodeBuildder/phoenix#64.

Closes #52