Add a review handover (Claude→future Claude: branch state, commit map, dual-session isolation facts, and the owner-triggered landing procedure) plus an owner UI QA checklist for the flows the harness can't verify (touch-drag, interactive photo add/delete/reorder). Update the frontend-entry-edit plan status: implementation + code-review done; only owner QA + landing remain. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Mpdu3Dt1iVoozHwAMyjrbn
docs/
If you're Mischa
Doing something operational? → guides/
- Posting a journal entry
- Managing GPX files
- Switching to a new trip
- Rebuilding local dev from scratch
Checking project status? → working/
Design or architecture decisions? → reference/
If you're Claude
Always-loaded project rules → CLAUDE.md (repo root)
Active specs and plans → working/specs/ and working/plans/
Stable facts → reference/
Raw research input → research/