chore: 같은 레이어 내부 DI 제한 지침 추가

Author: opficdev

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

@@ -79,6 +79,7 @@ Ask the user before editing when:
 - 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.
 - 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 Presentation `StorePattern` flow or reducer responsibility would change.
 - A compile fix requires relaxing the intended architecture.
 - The change is outside the requested issue or PR scope.
@@ -120,6 +121,7 @@ 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 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

@@ -130,6 +130,16 @@ flowchart TD
 | `DevLogWidgetCore` | widget snapshot models, factories, app-group keys/defaults store, deep links, pure snapshot logic | Core | Adding Domain, Data, Infra, Persistence, Presentation, App, or DevLogWidget dependency |
 | `DevLogWidgetExtension` | WidgetKit rendering and timeline plumbing | WidgetCore | Calling app/domain services directly |
 
+## Layer-internal dependency injection
+
+Do not inject dependencies between types that belong to the same layer.
+
+This rule covers initializer injection, stored-property injection, environment injection, and resolving same-layer types through `DIContainer`.
+
+The only allowed exception is a SwiftUI `View` file in `Application/DevLogPresentation` receiving same-layer presentation objects such as a ViewModel, Coordinator, or Store for UI composition.
+
+That exception does not apply to non-View files in Presentation, and does not apply to Core, Domain, Data, Infra, Persistence, Widget, App, WidgetCore, WidgetExtension, or Firebase functions.
+
 ## Presentation StorePattern flow
 
 ```mermaid
@@ -165,6 +175,7 @@ flowchart TD
 	CoreDomain{"Core vs Domain ownership?"}
 	Shared{"Moved only because shared?"}
 	NewDependency{"New module dependency?"}
+	SameLayerDI{"Same-layer dependency injection?"}
 	ExternalSDK{"External SDK crosses layer?"}
 	WidgetBoundary{"WidgetCore sees app/domain/data?"}
 	BuildShortcut{"Build fix relaxes boundary?"}
@@ -178,7 +189,10 @@ flowchart TD
 	Shared -->|Yes| Ask
 	Shared -->|No| NewDependency
 	NewDependency -->|Yes| Ask
-	NewDependency -->|No| ExternalSDK
+	NewDependency -->|No| SameLayerDI
+	SameLayerDI -->|Presentation View file| ExternalSDK
+	SameLayerDI -->|No| ExternalSDK
+	SameLayerDI -->|Other| Ask
 	ExternalSDK -->|Yes| Ask
 	ExternalSDK -->|No| WidgetBoundary
 	WidgetBoundary -->|Yes| Ask

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

@@ -57,6 +57,13 @@ This reference holds DevLog-specific working rules that should live with the pro
 - Keep project-file, lockfile, and code changes separated when the task scope requires clean review.
 - Do not broaden architecture work into unrelated Firestore, Messaging, UI, or safety edits.
 
+## Layer-internal dependency injection
+
+- Do not inject dependencies between types that belong to the same layer.
+- This includes initializer injection, stored-property injection, environment injection, and resolving same-layer types through `DIContainer`.
+- The only allowed exception is a SwiftUI `View` file in `Application/DevLogPresentation` receiving same-layer presentation objects such as a ViewModel, Coordinator, or Store for UI composition.
+- The exception does not apply to non-View files in Presentation, and does not apply to Core, Domain, Data, Infra, Persistence, Widget, App, WidgetCore, WidgetExtension, or Firebase functions.
+
 ## Data, Domain, and Infra boundary
 
 - Do not move domain entities to Core only because multiple modules need them.

AGENTS.md

@@ -53,6 +53,13 @@ Treat this repository as a Tuist-generated, workspace-based modular iOS app. The
 - `Widget/DevLogWidgetExtension`: WidgetKit UI, widget providers, entries, timelines, and extension resources. It should consume WidgetCore outputs rather than app/domain services directly.
 - `Firebase/functions`: TypeScript Cloud Functions. Deploy updated functions one by one separately.
 
+### Layer-internal dependency injection
+
+- Do not inject dependencies between types that belong to the same layer.
+- This applies to initializer injection, stored-property injection, environment injection, and resolving same-layer types through `DIContainer`.
+- The only allowed exception is a SwiftUI `View` file in `Application/DevLogPresentation` receiving same-layer presentation objects such as a ViewModel, Coordinator, or Store for UI composition.
+- The exception does not apply to non-View files in Presentation, and does not apply to Core, Domain, Data, Infra, Persistence, Widget, App, WidgetCore, WidgetExtension, or Firebase functions.
+
 ### StorePattern flow
 
 - Preserve the existing Presentation `StorePattern`.
@@ -72,6 +79,7 @@ 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.
+- 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.
 
 ### Safe mechanical changes