Dokumen ini mencatat tahap implementasi pada versi yang disebutkan. Untuk status akhir seluruh fitur, baca audit implementasi.
#30 — ordered multi-day itinerary
Validated 2026-09-19 on physical TECNO KF8, Android build 0.9.0-itinerary.
The agenda accepts up to five ordered destinations, departure time, stay duration, lodging permission/connection/power, and optional return to origin. Reordering or editing invalidates the previous calculation. The planner preserves mandatory destination order while searching charging stops within each section. SOC and elapsed time carry through the whole journey and across midnight.
Overnight stays never reset SOC. Lodging charging requires explicit permission, compatible connection confirmation and positive supplied power; charger/profile limits still apply. Charging and stay overlap using their maximum duration, an assumption disclosed in the result. A round trip includes the return to origin; a one-way trip includes a verified routing/energy estimate to a candidate charger after the destination. Candidate facility availability remains conditional.
The day-grouped table reports road distance, elevation gain/loss, departure/arrival time, consumption, both SOC scenarios and charging duration/power. Nonzero exit journeys appear as complete final rows. Saved plans retain the full agenda and restore it after process restart. Missing terrain in older saved results is labelled unavailable rather than shown as flat.
Verification:
- 44 Node tests pass, including continuous SOC/time across midnight, no implicit overnight charging, confirmed lodging enabling the return, reordered mandatory destinations, stored agenda order, and exit schedule/terrain/both SOC values.
- Native JVM tests, debug assembly and Android lint pass.
- TECNO controlled UI scenario: two destinations, 120-minute first stay, 600-minute lodging stay with confirmed 800 W supply, and return to origin. Calculation succeeds; destination reorder recalculates and persists; force-stop/reopen restores the same plan and ordered agenda.
- Device checks use synthetic routes, not personal vacation data or calibration samples. Native profile/catalogue/prediction/plan documents and network conditions are restored after checks. Ignored evidence:
research/runtime/issue30-device.json. - Standards review found no blocking violations. Spec review identified an incomplete exit table row; this was corrected and independently re-reviewed with no remaining findings.
Search remains bounded to six intermediate charging candidates and 24 routed connections; results do not claim a global optimum or guaranteed station access. Full offline navigation remains deferred.