1. Command

$ npx news florida-aca-enrollment-crash --debug --verbose

2. Output

INFO: Initializing `healthcare-policy-monitor.sh`...
INFO: Fetching data for current enrollment period (Jan 2026).
INFO: CMS Report released: January 15, 2026.

DEBUG: Scanning `state_health_metrics.json`...
DEBUG: Florida (`FL`) processed_enrollment_count: 4,500,000.
DEBUG: Last year's Florida (`FL`) processed_enrollment_count (2025): approx. 4,750,000.

WARN: Delta detected for Florida enrollment: -250,000 users.
WARN: This represents a 5.5% decrease, highest net drop nationwide.

DIFF: Enrollment vs. Previous_Year
---------------------------------
- Florida: 4.75M -> 4.5M (-5.5%)
+ Texas: 3.95M -> 4.1M (+3.7%)
- National: 24.5M -> 23M (-6.3%)
---------------------------------

ERROR: `ACA_SUBSIDY_EXTENSION_MODULE` failed to load.
ERROR: Root cause: `congress-voting-system` returned `FAILURE` on extension efforts.
ERROR: Premium hikes for tens of thousands initiated.

INFO: National enrollment data: ~23 million total plans activated.
INFO: 2.8 million new enrollees across federal and state exchanges.
INFO: Almost 20 million returning patients.

DEBUG: `Healthcare.gov` serving Florida, no local state exchange.
DEBUG: Texas continues to defy expectations with positive growth.

"ALERT: System detected a major user exodus event following critical `SUBSIDY_CONFIG` depletion. Recommend immediate policy refactor."

3. Stacktrace (If This News Were Code)

A critical dependency, ACA_Subsidies_2026.js, encountered an unhandled rejection, leading to a cascade of user churn.

The primary fault lies within the policy_decision_maker.congress() function, which appears to have returned a false boolean for the extendSubsidies parameter. This unexpected behavior propagated, causing significant disruption in the healthcare_enrollment_service.user_onboard() flow.

Traceback (most recent call last):
  File "src/healthcare/enrollment.py", line 128, in finalize_enrollment
    premium_cost = calculate_premium(user_data, subsidies.get_current_status())
  File "src/policy/subsidies.py", line 45, in get_current_status
    raise SubsidyConfigNotFound("ACA_SUBSIDY_EXTENSION_MODULE failed to load.")
SubsidyConfigNotFound: 'ACA_SUBSIDY_EXTENSION_MODULE' was not found or failed to initialize due to 'congress.policy_decision_maker' returning an invalid state (FAILURE).
Segmentation fault? Unexpected behavior? Panic!

Essentially, the SUBSIDY_EXTENSION_HOOK was left dangling, leading to an immediate fallback to a higher premium calculation. Users, predictably, opted out rather than paying the unexpected premium_increase_factor.

4. Patch Notes

• - Fixed: Congressional GOVERNMENT_SHUTDOWN event in October has been resolved (mostly).
• - Removed: COVID-era expanded subsidies for ACA plans. (This was the core problem.)
• - Impact: Florida now has ~250,000 fewer ACA enrollees; nationwide, 1.5 million less.
• - WARN: Premium increases are now live for tens of thousands of users.
• - DEBUG: Texas's enrollment_growth_logic seems to be operating differently; further investigation required.
• - Known Bug: congress-policy-logic consistently fails to handle long-term financial planning for critical services without last-minute intervention.