feat(platform): sprint 11.5 standardization
Some checks failed
Architecture Governance / architecture (push) Has been cancelled
Some checks failed
Architecture Governance / architecture (push) Has been cancelled
This commit is contained in:
@@ -64,6 +64,30 @@ All new work must comply with this foundation.
|
||||
If an implementation conflicts with these rules, implementation must be adjusted.
|
||||
If a rule must change, an ADR update is required first.
|
||||
|
||||
## Sprint 11.5 Standardization Audit (2026-07-09)
|
||||
|
||||
Platform-wide standardization was executed before Admin Platform work.
|
||||
|
||||
### Completed Standardization
|
||||
|
||||
- Verified and enforced container/facade/domain/infrastructure boundaries across active website features.
|
||||
- Removed remaining legacy variant naming in application-layer templates/styles.
|
||||
- Removed duplicate legacy search-history implementation in catalog feature module.
|
||||
- Standardized design-token surface with explicit spacing, radius, shadow, and transition tokens.
|
||||
- Added widget metadata support for title/subtitle/visibility/layout/animation/style/permissions in shared contracts and dynamic rendering path.
|
||||
- Converted remaining identified hardcoded UI strings in audited runtime pages/components to translation keys.
|
||||
|
||||
### Bootstrap/Configuration Gaps Identified
|
||||
|
||||
- Widget permission model supports auth gating but role/permission enforcement is limited by current auth session shape (no role list in session model).
|
||||
- Popular search defaults are currently facade-local and should be moved to bootstrap-configurable catalog search settings.
|
||||
- Storage key naming conventions for local persistence are platform-scoped but still static constants; optional bootstrap override could improve tenant isolation.
|
||||
|
||||
### Validation Baseline
|
||||
|
||||
- Build and architecture checks are required for acceptance of this sprint.
|
||||
- Final details and file-level changes are tracked in `Platform-Standardization-Report.md`.
|
||||
|
||||
## Mandatory Phase Order
|
||||
|
||||
Implementation must proceed only in this order:
|
||||
|
||||
Reference in New Issue
Block a user