Local-first Android product workspace for a private image calendar app. This repo is operated as an LLM-maintained second brain plus SDD implementation project.

Image Calendar is a personal mobile app for recording daily photos, short notes, and emotion tags by date.

Core constraints:

• No server
• No login
• No social graph, feed, likes, comments, follows, or sharing
• All records stay on the current device
• Backup/export is always an explicit user action

Product promise:

내 폰 안에만 조용히 쌓이는 하루 사진 캘린더

Latest verified slice:

• 2026-05-01 - MVP completion: onboarding, archive, settings backup/delete, restart verification

Implemented:

• Onboarding with local-only value proposition and start/skip actions
• Calendar tab with month grid, today highlight, local-only badge, and record marker
• Empty-date add CTA from Calendar
• Add tab with gallery picker entry, debug QA fixture, required photo validation, date validation, memo, emotion tags, and local save
• Day Detail view after save
• Day Detail edit dialog for date, memo, and emotion metadata
• Day Detail delete confirmation and repository-backed record deletion
• Archive tab with month grouping, memo/date search, emotion filters, no-result state, and Day Detail navigation
• Settings tab with local trust card, backup zip export, restore follow-up row, app info, danger zone, and delete-all confirmation
• Room database schema export under app/schemas/
• Internal image copy and thumbnail generation
• Backup zip export with manifest.json, originals, and thumbnails
• Full data deletion for local records and internal entry assets
• Repository rollback cleanup on metadata insert failure
• Repository cleanup failure detection on record deletion
• Android CLI-friendly content descriptions and test tags for touched controls

Not yet implemented:

• Camera capture
• Restore/import
• Stable long-term backup migration contract
• Automated Android CLI smoke script

• Project Overview
• Current State
• MVP Scope
• Design Output Review v2
• Architecture
• Data Model
• Test Strategy
• Implementation Log
• Git Conventions
• Project Custom Skills
• Meeting Index
• Wiki Index

Verification rules:

• Every meaningful UI verification must store screenshots, layout JSON, annotated screenshots, action log, and findings under raw/verification/.
• Android CLI is the official install/launch/layout/screenshot tool for device verification.
• Local ignored artifacts/ can be used temporarily, but durable evidence must be copied into raw/.

./gradlew assembleDebug
android describe --project_dir=.
android run --apks=app/build/outputs/apk/debug/app-debug.apk --activity=.app.MainActivity

Capture evidence:

android layout --pretty --output=raw/verification/<date-topic>/assets/screen-layout.json
android screen capture --output=raw/verification/<date-topic>/assets/screen.png
android screen capture --annotate --output=raw/verification/<date-topic>/assets/screen-annotated.png

Before a feature is considered done:

• ./gradlew assembleDebug passes.
• Official android run can install and launch the app.
• Screen evidence is saved under raw/verification/.
• Layout JSON exposes useful content descriptions or test tags for key actions.
• Source scan shows no INTERNET, account, upload, sync, cloud, share, or social concepts.
• The relevant specs/*/tasks.md, wiki/06-project/implementation-log.md, and wiki/log.md are updated.

Post-MVP sequence:

1. Convert the Android CLI MVP journey into a reusable smoke script/checklist.
2. Run external designer review against the MVP screenshot evidence.
3. Review backup/delete copy with privacy/legal perspective before public release.
4. Decide whether Camera capture or restore/import is the next product increment.