Route availability, turnover, unit timeline, cell explain, and multicalendar asks to focused read-only reservations-melted commands.
Use this skill when the user wants availability, vacancy, arrivals, departures, turnover analysis, grid rendering, or cell-level explanation based on reservations-melted rather than apartment_attributes.
reservations-melted as the date-cell availability source of truth.apartment_attributes readiness as optional compare-only context, never as availability truth.today, tomorrow, or tonight.Run:
python3 plugins/reservations-melted-grid/scripts/reservations_melted_grid.py <command> ...
availability-summaryturnoversunit-timelineexplain-cellrender-multicalendarAvailability summary:
python3 plugins/reservations-melted-grid/scripts/reservations_melted_grid.py \
availability-summary \
--start-date 2026-04-14 \
--end-date 2026-04-14 \
--building "Noble" \
--format summary
Turnovers:
python3 plugins/reservations-melted-grid/scripts/reservations_melted_grid.py \
turnovers \
--start-date 2026-04-14 \
--end-date 2026-04-15 \
--building "Noble" \
--format summary
Unit timeline:
python3 plugins/reservations-melted-grid/scripts/reservations_melted_grid.py \
unit-timeline \
--start-date 2026-04-14 \
--end-date 2026-04-16 \
--unit PH913TN \
--format summary
Explain one cell:
python3 plugins/reservations-melted-grid/scripts/reservations_melted_grid.py \
explain-cell \
--date 2026-04-14 \
--unit PH913TN \
--with-readiness \
--format summary
Render the grid:
python3 plugins/reservations-melted-grid/scripts/reservations_melted_grid.py \
render-multicalendar \
--start-date 2026-04-14 \
--end-date 2026-04-16 \
--building "Noble" \
--format markdown
Ignore manual blocks:
python3 plugins/reservations-melted-grid/scripts/reservations_melted_grid.py \
availability-summary \
--start-date 2026-04-14 \
--end-date 2026-04-14 \
--building "Noble" \
--exclude-blocks \
--format json
Available filters:
--building case-insensitive substring on buildingName--property-id--parent-listing-id--name-contains--type-of-unit--unit for exact unit targeting on unit-timeline and explain-cellDefaults:
--type-of-unit is passed, the script defaults to unit rows: MTL_CHILD and SINGLE--exclude-blocks is passed--with-readiness is passedEvery command returns:
metadaysunits or cellsmismatchesFixed status vocabulary:
reserved, vacant, blocked, unavailablearrival_only, departure_only, same_day_turn, stayover, vacant_holdclean_but_reserved, occupied_but_vacant, dirty_but_vacant, unknown_readiness_state--with-readiness reads the current apartment_attributes_apt_ready snapshot from MySQLWhen answering, keep the structure explicit:
Do not mix readiness with availability unless the user explicitly wants compare mode.