Khalim Conn-Kowlessar 98d2f7aa16 Goal-aligned dispatch reads one enum-keyed table 🟪 ... Review findings on PR #1527: - The 'which goals are goal-aligned' set lived in two adjacent if-chains (_objective_for and _require_budget_for_goal_aligned) that had to stay in sync — a new goal-aligned goal added to one but not the other would slip the budget guard. Both now read a single _GOAL_ALIGNED_OBJECTIVES table. - The goal strings are the canonical PortfolioGoal enum values, not re-declared string constants, so goal-value drift can't silently degrade a goal to max-SAP; _target_sap reads the enum too. - _scored_candidate_groups takes objective without a default (its only caller passes it). - scoring.py: 'cached: float | None' -> Optional[float] per the CLAUDE.md 'Use Optional over | None' rule. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>		2026-07-10 11:17:27 +00:00
..
__init__.py	refactor(modelling): group domain/modelling into generators/scoring/optimisation	2026-06-03 13:48:36 +00:00
overlay_applicator.py	A community override keeps an assessor-observed Group 3 control 🟩	2026-07-03 16:35:08 +00:00
package_scorer.py	feat(modelling): Score carries the scored SapResult for billing	2026-06-03 17:20:45 +00:00
scoring.py	Goal-aligned dispatch reads one enum-keyed table 🟪	2026-07-10 11:17:27 +00:00