docs:update

Author: MeikoMei16

README.md

@@ -92,6 +92,12 @@ Still in progress:
 - downloader flow beyond the current scaffold / persistence layer
 - more complete local-first and offline-friendly browsing flows
 
+Persistence status note:
+
+- SQLite exists today as schema/bootstrap groundwork, not as the primary source of truth for browse/detail data
+- database-backed resource persistence is intentionally deferred until the UI and local-first flows that consume it are defined more concretely
+- for now, only persist data with a clear local ownership story such as renderer UI restore state, auth/session artifacts managed by the main process, download tasks, local file links, and future user-authored metadata
+
 ## Documentation
 
 - [docs/README.md](docs/README.md)

docs/architecture.md

@@ -254,6 +254,14 @@ Status note:
 
 - The schema is broader than currently shipped UI features.
 - Some tables support planned local-first capabilities that are only partially wired today.
+- Database-backed resource persistence is intentionally deferred for now; the app still treats upstream API responses as the source of truth for homepage browsing and detail loading.
+- Do not treat the presence of a table as a requirement to persist that upstream resource yet.
+- Near-term persistence should stay narrow and local-first:
+  renderer UI restore state
+  main-process auth/session artifacts
+  download queue state
+  local installation/link metadata
+  explicitly user-authored local metadata once that UI is implemented
 
 ## Current Feature Status
 
@@ -281,6 +289,7 @@ Status note:
 - Local metadata cache usage is still limited
 - Downloader is scaffolded, not full end-to-end
 - Offline-first search is not yet the main browse path
+- Deciding which upstream resource payloads deserve durable SQLite storage is still deferred work, not a settled requirement
 
 ## Important Constraints
 

docs/decisions.md

@@ -265,6 +265,31 @@ Reason:
 
 - users expect “退出高级模式” to return to ordinary browsing immediately, not only flip an internal mode flag
 
+## Local Persistence
+
+### SQLite scope is intentionally deferred
+
+Rule:
+
+- do not assume every upstream resource or detail payload should be persisted just because a schema/table exists
+- upstream TouchGal browse/detail responses remain the source of truth for now
+- add durable SQLite persistence only when a concrete local consumer is defined, such as offline browse, cache invalidation, download orchestration, local library linking, or user-authored metadata
+- when in doubt, prefer not persisting a resource payload yet
+
+For now, safe persistence targets are:
+
+- renderer UI restore state such as homepage query/page and interaction preferences
+- main-process auth/session artifacts
+- download tasks and related local execution state
+- local file/library links
+- future personal notes, play state, and other user-authored metadata
+
+Reason:
+
+- the current database layer is broader than the shipped product surface
+- persisting upstream resource payloads prematurely creates schema obligations, sync questions, and invalidation work before the app has a settled local-first read path
+- narrowing persistence scope keeps the current implementation aligned with the actual product state
+
 ### Advanced filter execution is button-driven
 
 Rule: