forge back up sync 성공 success! 333 저그 백업
ver2 isle data save back up / sync
app Isle 의/Users/rogan/Desktop/appDev/library-content-sns/11-1Isle
클라우드 백업 방식과 안내를 ㅌ동일하게 저 시스템에서 그대로 베껴와줘
-> appdev 폴더 안에 있고, 그리고 클라우드 백업 폴더에서 위치를 icloud에서 바꿀수 있는 부분을 배껴와서 앱 내에 구현해줘
앱 안의 데이터가 저장되기를 원하고, 그리고 그것을 Icloud파일 중 하나로 지정 가능한 시스템( 개인 지정 가능) 으로 만들어줘!
# Backup System Blueprint (Copy/Paste Ready)
if the backup system like this already exist, just change whatever has been added you
버전 업데이트가 진행이 되어도 이 백업 코드는 여전히 유효해야 한다 !
## Purpose
- Guarantee user data survivability even when cloud login/sync is unavailable.
- Provide portable backup/restore between reinstalls and devices.
- Prevent backup UI crashes related to keyboard/focus lifecycle timing.
Also, if it is possible create a system where when I reinstall this app and to updated version, it will automatically bring the data that I have personally put it in. It will automatically have those data move to the reinstalled version.
Make sure to use can there's a setting button where the user can actually go in and it is accessible for the user tool for the user to easier to copy the code
make sure the whole backup code is not so long to the point where you know it's like really hard for me to copy it because like there are like 200 lines of backup code. I have to scroll all the way down on my phone to finally copied like it shouldn't be like that I think it should be folded, and there should be a button where you can copy it if you want to see the whole thing you can open it wide open, but you should be able to close it with a button really fast
## Core Requirements
1. Export full app state to a portable text code.
2. Restore in two modes:
- `Replace All` (exact restore)
- `Merge` (safe merge with existing state)
3. Make backup entry point highest priority in sync/settings UI.
4. Never trap users in backup screen (always provide close/back path).
5. Survive abrupt process kill with periodic and lifecycle checkpoints.
Make sure even though the backup text is so long make sure to user. Don't have to scroll all the way down there be a copy button and also let there be a toggle button that can actually minimize that minimize all the very easily so the user don't have to scroll 5 or eight times.
---
## Data Model Strategy
Use a single canonical pack object (example fields):
- activities
- routines
- timers
- trashActivities
- trashRoutines
- purgedActivityTrash
- purgedRoutineTrash
- updatedAt
- schema
Serialization format:
- JSON -> UTF8 -> Base64 (single string backup code)
Why Base64:
- easy copy/paste in notes/password managers/chat
- avoids structural corruption from direct JSON formatting
---
## Restore Modes
### A) Replace-All Restore (default user-safe)
- Decode backup code.
- Parse pack.
- Replace in-memory state with decoded pack.
- Persist immediately.
- Use for deterministic recovery without overlap.
### B) Merge Restore (optional advanced)
- Decode backup code.
- Run deterministic merge logic (last-write-wins / tombstone-aware).
- Persist immediately.
- Use only when user intentionally wants additive merge.
---
## UI Blueprint
### Sync/Settings Sheet
- Put `Backup code export / restore` button at top.
- Keep cloud options below backup section.
- Add explicit `Close` button at top-right.
### Backup Sheet
- Sections:
1) Export code (selectable text + copy button)
2) Restore input field
3) Buttons:
- `Restore (Replace All)`
- `Restore (Merge)`
- Add explicit `Close` button.
- Add `Hide keyboard` button.
- Text input must support:
- `textInputAction: done`
- tap outside to dismiss keyboard
---
## Crash Prevention Rules (Critical)
### 1) Keyboard/BottomSheet lifecycle safety
Do NOT call context-bound focus lookup in transient sheet close race paths.
Use:
- `FocusManager.instance.primaryFocus?.unfocus()`
Safe close flow:
1. unfocus keyboard
2. wait one frame (`~16ms`)
3. pop sheet if still mounted
This prevents framework assertions like:
- `_dependents.isEmpty` related lifecycle/focus collisions.
### 2) Zone integrity at startup
Keep `ensureInitialized`, service init, and `runApp` in same guarded zone.
This prevents startup `Zone mismatch` assertion.
### 3) Process-kill survivability
Add:
- periodic checkpoint snapshot (e.g. every 25s)
- lifecycle checkpoint on `inactive/paused/detached`
---
## Backup Code Robustness
Before decode:
- remove all whitespace/newlines from pasted code
Pseudo:
- `normalized = input.replaceAll(RegExp(r'\s+'), '')`
- `decoded = utf8.decode(base64Decode(normalized))`
This prevents failures from wrapped/pasted multi-line code.
---
## Error Handling Policy
On restore:
- invalid code => show user-readable snackbar/toast
- never crash UI thread
- log failure with stack trace in persistent log
On success:
- show confirmation message
- close sheet through safe close flow
---
## Logging + Recovery Blueprint
Persistent logs should include:
- boot timestamp
- app version
- lifecycle transitions
- save/checkpoint events
- restore attempts + mode (`replaceAll`/`merge`)
- restore success/failure summary
Crash snapshot file:
- write atomically (`tmp -> rename`)
- read on boot if local data is corrupted
---
## Replication Prompt (for another AI agent)
Use this prompt in another app project:
Implement a crash-safe backup code system with these constraints:
---
## Validation Checklist
- [ ] Export code copies correctly.
- [ ] Replace-All restore does not overlap duplicate schedules.
- [ ] Merge restore preserves intended additive behavior.
- [ ] Keyboard can always be dismissed.
- [ ] Backup/sync sheets always close without crash.
- [ ] Abrupt kill still preserves latest checkpoint.
- [ ] Logs persist and include restore result details.
- [ ] Startup has no zone mismatch assertion.