feat: surface shock repair-block blast radius

[Euda1mon1a]

Summary

• extend annual shock preview with block-scoped blast-radius context so coordinators can see the full repair block, not only the direct absence hits
• render that broader repair-block context in the annual-planning hub with direct-vs-same-block labeling
• update tracker docs/changelog and add a branch note for the shock blast-radius slice

Validation

• backend/.venv/bin/python -m ruff check backend/app/schemas/annual_rotation.py backend/app/services/annual_rotation_service.py backend/tests/services/test_annual_rotation_service.py
• backend/.venv/bin/python -m pytest backend/tests/services/test_annual_rotation_service.py -k "preview_shock_impact_maps_absence_to_blocks or preview_shock_impact_counts_exact_assignment_pairs" -q
• PATH="/Users/aaronmontgomery/Autonomous-Assignment-Program-Manager/backend/.venv/bin:$PATH" npm run generate:types
• npm test -- --watchAll=false frontend/src/app/hub/annual-planning/__tests__/AnnualPlanningHubClient.test.tsx
• npm run type-check
• npx eslint src/app/hub/annual-planning/AnnualPlanningHubClient.tsx src/app/hub/annual-planning/__tests__/AnnualPlanningHubClient.test.tsx

Notes

• stacked on top of feat: actualize policy-layer rollover and annual-planning views #1545 (codex/policy-layer-cutover-phase1) to keep the branch scope within the repo file-limit guardrail
• review metadata only: this branch does not widen unlock scope or change repair generation/publish mechanics

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, add credits to your account and enable them for code reviews in your settings.