maniator / maniator/verticopolis
[Feature]: [P3] Authored base floor for elevator schedules (Set as base)
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Parked from the #464 fold-in build (spec ux-elevator-schedule-dialog-2026-07-17.md §17). The floors grid marks the DERIVED base floor (lowest served lobby, else the shaft bottom) with the ◎ glyph, but spec §4.2's Set as base affordance is unbuildable without an authored base field on the schedule model, and adding one is a save-format conversation (SAVE_VERSION bump + TDT mapping: the 1994 save may carry a related byte; check the TDT spec's elevator header when the Wine harness phase runs).
Scope when picked up: the model field + coercion, dispatch's unhomed-car fallback reading it, the grid's Set as base press, serialization + migration, and the TDT parity check.
Review lane: /gds-code-review.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with ux-elevator-schedule-dialog-2026-07-17.md, especially sections 4.2 and 17, then trace the elevator schedule model, dispatch fallback, floors grid, and save migration paths. During the Wine harness phase, inspect the TDT elevator header for parity. Done means the authored base is editable, used for unhomed-car fallback, serialized and migrated with the SAVE_VERSION change, and covered by the TDT parity check.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend, frontend, full-stack
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100