Allow composition within command internal helpers
This commit is contained in:
@@ -358,6 +358,8 @@ fetch endpoint reports absence. Focused publication/wrapper tests pass.
|
||||
|
||||
### R10 — Medium: The boundary checker bans valid command-internal composition
|
||||
|
||||
Status: Resolved.
|
||||
|
||||
Category: Inadvertently strengthened architectural prohibition.
|
||||
|
||||
**Evidence:** [checkImportDirections](../../internal/apicheck/main.go), around
|
||||
@@ -381,6 +383,12 @@ turning current package inventory into a fixed future architecture.
|
||||
internal imports of command code and internal-helper imports of public facades
|
||||
remain rejected.
|
||||
|
||||
**Resolution:** The import checker identifies each executable’s internal helper
|
||||
subtree and permits collaboration inside it. Library-to-command imports,
|
||||
helper-to-controller imports, and internal-to-facade imports remain rejected.
|
||||
Positive and negative dependency fixtures and the actual compiled repository
|
||||
boundary checks pass.
|
||||
|
||||
## Remediation boundaries
|
||||
|
||||
Address these findings before treating the initial implementation as complete
|
||||
|
||||
Reference in New Issue
Block a user