Record public facade boundary validation
This commit is contained in:
@@ -2,10 +2,11 @@
|
||||
|
||||
## Status
|
||||
|
||||
Complete as of 2026-07-28. The public-facade adapter boundary is established;
|
||||
the [implementation plan](implementation.md) records the completed work, and
|
||||
the [main migration roadmap](migration.md) identifies repository creation as
|
||||
the next gate.
|
||||
Complete as of 2026-07-28. The public-facade adapter boundary and its
|
||||
post-implementation error-classification, MIME-test, and dependency-guard
|
||||
corrections are validated. The [implementation plan](implementation.md)
|
||||
records the completed work, and the [main migration roadmap](migration.md)
|
||||
identifies repository creation as the next gate.
|
||||
|
||||
## Purpose
|
||||
|
||||
@@ -26,7 +27,8 @@ The CLI, HTTP handler, and prepared-run formatter now consume public engine
|
||||
values and errors. `serve` injects Scriptorium's HTTP-owned restricted artifact
|
||||
reader through the public extension point, while the root facade continues to
|
||||
compose the framework implementation inside this repository. A repository-level
|
||||
dependency test protects the direct-import boundary.
|
||||
dependency test recursively protects production adapter and formatter packages
|
||||
from framework-owned imports.
|
||||
|
||||
## Target State
|
||||
|
||||
|
||||
Reference in New Issue
Block a user