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

#35 — Selected trip export and deletion

Android 0.14.0-trip-data, implemented 2026-09-19. The recording history exposes independent selection checkboxes, a JSON share action, and a two-step delete confirmation showing the selected trip times. Only completed trips can be deleted; active records can be exported as snapshots.

Export and sharing

Schema version 1 includes selected profiles, actual SOC observations, GPS samples, charging sessions and immutable pre-leg prediction snapshots. Units, recording provenance and export time are explicit; original timestamps and synthetic/mock flags remain. An explicit data field vocabulary excludes unrelated account/transport fields, including credentials nested in fixture profiles, model metadata or route headers.

A private UTF-8 JSON file is written and synced before launching the Android chooser. A scoped FileProvider exposes only cache/trip-exports/, with temporary read permission. No arbitrary app file path is accepted from JavaScript. Failure to serialize, write or launch sharing never deletes source records; chooser cancellation is not reported as delivery. Reference: Android FileProvider documentation.

Deletion and calibration

After explicit UI confirmation, the recorder validates the complete selection, invalidates derived calibration, revokes/removes private exported copies and atomically deletes selected event rows. Memory is reconstructed only after database deletion succeeds. Other trip events remain unchanged. A failed precondition or database operation preserves source records, although calibration may require rebuilding because invalidation deliberately happens first.

The calibration report explicitly requests a rebuild from remaining history, with the base scenario used meanwhile. Existing pre-leg predictions remain historical snapshots. Previously shared copies held by other apps cannot be recalled; the confirmation states this limitation.

History snapshots carry a native revision. Model publication verifies that revision under the recorder lock before its document compare-and-write, preventing a stale activity from reintroducing deleted history. Export snapshot creation and private file publication hold the same recorder lock used by deletion, so an older exporter cannot recreate a deleted trip's private copy afterward.

Verification

Device helper/evidence are ignored under research/runtime/check-trip-data-device.py and issue35-device.json. Integration fixtures are synthetic and do not establish field battery accuracy or energy savings.