journey-planner

Run the planning round, which groups eligible courses by cohort using cohort_status.py, estimates remaining slots per course, and weights each cohort's share toward its bottleneck. The result is reported as a sequence of session slots, never calendar dates.

Use /drop <course_id>, which sets roster_state to dropped while preserving all other fields, then runs roster_check.py to activate any dormant courses the drop unblocked. Re-adding the course later resumes from where it left off.

No, capacity is expressed only as sessions_per_week and a sequence of numbered session slots. It can give rough rate-based projections like weeks remaining, but never promises completion by a specific date.

A course draws slots only if its roster_state is active or test_pending_convergence and its grounding_status is not suspended_ungrounded. Dormant, dropped, suspended, and complete courses receive nothing, as determined by cohort_status.py.

The skill asks cohort_status.py whether the course's cohort is all_complete, then walks the level ledger upward to update highest_level_cleared. Newly eligible dormant courses are woken to active, and excluded dropped or suspended courses are reported transparently.

Dropped and grounding-suspended courses are listed as excluded_members so an abandoned course cannot hold every higher-level course dormant forever. The exclusion is never silent; the learner is told which courses were left out and why.