chore: Widget 중심 위젯 브리지 소유권 지침 정리

Author: opficdev

.hermes/skills/devlog-architecture-harness/SKILL.md

@@ -75,6 +75,10 @@ Ask the user before editing when:
 - A shared type is being moved only because multiple modules need access.
 - Firebase/Auth/Firestore/Functions/Messaging-specific logic would leave Infra.
 - WidgetCore would depend on Domain, Data, Infra, Persistence, Presentation, or App.
+- DevLogWidget would depend on Domain, Infra, Persistence, Presentation, or App.
+- DevLogWidget would use WidgetKit for anything beyond the app-side widget reload bridge.
+- Widget sync ownership would move away from the preferred split: Data contracts and snapshot repositories, DevLogWidget app-side bridge/snapshot update orchestration, WidgetCore snapshot models/factories/store contracts, and WidgetExtension rendering.
+- Persistence would gain widget snapshot generation, WidgetCore, WidgetKit reload, or DevLogWidget bridge ownership.
 - Presentation would depend on Data, Infra, Persistence, or App.
 - Data would gain concrete SDK or storage implementation details.
 - Data or Presentation would expand platform SDK usage beyond the existing narrow cancellation-classification or notification-badge patterns.
@@ -122,6 +126,8 @@ After completion, report only:
 - Do not infer project-specific architecture policy from generic Clean Architecture rules when DevLog already has a concrete pattern.
 - Do not move domain entities to Core just because multiple modules need them.
 - Do not inject same-layer dependencies except from SwiftUI `View` files in `Application/DevLogPresentation` into same-layer presentation objects for UI composition.
+- Do not collapse the current DevLogWidget bridge back into Data, Persistence, App, or WidgetCore without explicit boundary approval.
+- Route app-side widget bridge and snapshot update orchestration through DevLogWidget.
 - Do not hide architecture decisions inside build-fix wording.
 - Do not broaden a modularization task into unrelated Firestore, Messaging, or UI safety edits.
 - Do not mark work complete if the diff contains unrelated project-file or lockfile churn.

.hermes/skills/devlog-architecture-harness/references/devlog-architecture-flow.md

@@ -177,7 +177,7 @@ flowchart TD
 	NewDependency{"New module dependency?"}
 	SameLayerDI{"Same-layer dependency injection?"}
 	ExternalSDK{"External SDK crosses layer?"}
-	WidgetBoundary{"WidgetCore sees app/domain/data?"}
+	WidgetBoundary{"Widget sync ownership or WidgetCore boundary changes?"}
 	BuildShortcut{"Build fix relaxes boundary?"}
 	ScopeDrift{"Outside current task scope?"}
 	Ask["Ask user before editing"]
@@ -272,16 +272,24 @@ flowchart TD
 
 ```mermaid
 flowchart LR
-	App["App runtime\nDomain/Data/Infra/Persistence"]
-	Snapshot["Snapshot generation\nPersistence + WidgetCore"]
+	App["App runtime\nsession and mutation events"]
+	WidgetBridge["DevLogWidget\nsync bus implementation\nsync/session handlers"]
+	DataContracts["DevLogData\nwidget repository/updater contracts"]
+	SnapshotInputs["DevLogData\nsnapshot input repository"]
+	Snapshot["DevLogWidget\nsnapshot generation/persistence\nWidgetKit reload bridge"]
+	WidgetModels["DevLogWidgetCore\nsnapshot models/factories/store contracts"]
 	AppGroup["App Group storage\nShared defaults"]
-	WidgetCore["WidgetCore\nSnapshot models\nFactories"]
 	WidgetExtension["Widget extension\nWidgetKit UI"]
 
-	App --> Snapshot
-	Snapshot --> AppGroup
-	AppGroup --> WidgetCore
-	WidgetCore --> WidgetExtension
+	App --> WidgetBridge
+	WidgetBridge --> DataContracts
+	DataContracts --> SnapshotInputs
+	DataContracts --> Snapshot
+	SnapshotInputs --> WidgetBridge
+	Snapshot --> WidgetModels
+	WidgetModels --> AppGroup
+	AppGroup --> WidgetModels
+	WidgetModels --> WidgetExtension
 ```
 
 Widget UI should consume snapshot data. It should not fetch app services or domain repositories directly.

.hermes/skills/devlog-architecture-harness/references/devlog-workflow-rules.md

@@ -88,7 +88,10 @@ This reference holds DevLog-specific working rules that should live with the pro
 
 - Widget UI should consume snapshot data, not app/domain services.
 - `DevLogWidgetCore` should stay free of Domain, Data, Infra, Persistence, Presentation, and App dependencies unless the user explicitly approves a boundary change.
-- Prefer an app-driven snapshot flow: app/runtime data fetch, snapshot generation, App Group storage, WidgetCore model/factory, WidgetExtension rendering.
+- `DevLogWidget` owns the app-side widget bridge: sync event bus implementation, sync event handlers, session sync handler, auth-session sync provider, snapshot generation/persistence orchestration, WidgetKit reload bridge, and `WidgetAssembler`.
+- `DevLogData` owns widget-related contracts and repository implementations, including `WidgetSyncEventBus`, `WidgetSnapshotUpdater`, and `WidgetTodoSnapshotRepository`. Data should not own concrete widget handlers, WidgetCore snapshot model/factory usage, or WidgetKit reload behavior.
+- `DevLogPersistence` owns local persistence, user defaults, image store, and non-widget app persistence.
+- Prefer an app-driven snapshot flow: app/runtime event, DevLogWidget sync handler, Data snapshot input fetch, DevLogWidget snapshot update, App Group storage through WidgetCore contracts, WidgetExtension rendering.
 - `WidgetTodoSnapshot` is a lightweight snapshot value, not a full domain `Todo`.
 - Do not make `Todo.number` or `WidgetTodoSnapshot.number` non-optional without a separate saved-vs-draft model decision.
 - If a widget sync flow needs one timestamp for multiple snapshots, capture `Date()` once and pass it through to avoid midnight or quarter-boundary drift.

AGENTS.md

@@ -79,6 +79,12 @@ Ask the user before editing when any of these are true:
 - Firebase, GoogleSignIn, AuthenticationServices, UserNotifications, LinkPresentation, Network, WidgetKit, or storage implementation details would move to another layer.
 - A repository protocol, service protocol, assembler, or DI ownership boundary would change.
 - WidgetCore would start depending on app/domain/data implementation concepts.
+- DevLogWidget would start depending on Domain, Infra, Persistence, Presentation, or App.
+- DevLogWidget would use WidgetKit for anything beyond the app-side widget reload bridge.
+- Widget sync ownership would move away from the preferred split: Data contracts and snapshot repositories, DevLogWidget app-side bridge/snapshot update orchestration, WidgetCore snapshot models/factories/store contracts, and WidgetExtension rendering.
+- Persistence would gain widget snapshot generation, WidgetCore, WidgetKit reload, or DevLogWidget bridge ownership.
+- Data or Presentation would expand platform SDK usage beyond the existing narrow cancellation-classification or notification-badge patterns.
+- Infra would add any Domain dependency, source import, or SDK service contract coupling.
 - A same-layer dependency would be injected outside a SwiftUI `View` file in `Application/DevLogPresentation`.
 - The requested change suggests cleanup outside the current issue or PR scope.