Dokumen ini mencatat tahap implementasi pada versi yang disebutkan. Untuk status akhir seluruh fitur, baca audit implementasi.

#29 — explicit per-plan reserve exceptions

Validated 2026-09-19 on physical TECNO KF8, Android build 0.8.0-reserve.

The journey boundary persists plan identity, selected reserve, consent timestamp, input/profile snapshot, calculation state and result in a separate fixed native document. Every new plan starts at >20%. The planner exhausts its normal 90%-then-100% target search before offering >10%; a completed >10% search must fail before >5% is offered. No exception is automatically selected for speed or convenience. Exact 10% and exact 5% arrivals fail their respective strict bounds.

Accepting a lower reserve requires a current completed calculation in the active service session and a matching saved profile. Cancellation, SOC/profile change, destination or supply changes, station preferences and catalogue refresh invalidate outstanding offers. Reopening retains accepted consent but does not reactivate an unaccepted old offer; it requires recalculation. Existing accepted consent remains attached to the same plan through ordinary updates. Normal >20% alternatives are recalculated and displayed when available, with a control to return to normal policy. A new plan clears the active plan association and begins at >20% without deleting historical plans.

Durable pending state precedes asynchronous calculation. The latest request revision alone may publish a result; late/cancelled responses cannot replace a newer plan. UI reopening labels restored results with their saved time and asks the user to verify SOC and recalculate before departure.

Verification:

Search remains bounded as documented for #28. An exception is a user choice about a scenario estimate, not a guarantee of actual battery or charger availability.