KBX v30 Validation Report

자동 검증 명령

node scripts/validate-kbx.mjs

최종 정적 Governance 결과

Design Tokens: 143
Component Definitions: 84
Core Component APIs: 34
Component Catalog Entries: 56
Screen Definitions: 20
Navigation Entries: 16
API Operations: 66
Permissions: 54
Canonical Fields: 51
Canonical Test Scenarios: 27
Fixture Sets: 16
Fixture Refs: 37
Golden Screen Coverage: 10 / 10
TypeScript/Vue Script Units: 290
DB Migrations: 16
Design Debt: 286

v30 전용 Gate

validate-template-navigation-v30.mjs가 다음을 확인한다.

T01~T09 coreComponents / completionChecks
KbxFormSection tokenization과 KbxFormGrid/KbxFormSpan
실제 T02/T03 화면의 FormGrid adoption
9개 Screen Type Scaffolder canonical mapping
Home buildKbxHomeWorkbench()와 중복 제거 IA
ScreenId route capability / safe workspace path
catch-all Not Found recovery
AccessDenied metadata secure-default
Global Header module selector
Header↔SideNav focused module synchronization
profile action propagation
신규 Public API export

전체 Gate

API, Authorization, Integration, Provider, External Data, Configuration, Migration Safety, Deployment, Telemetry, Experiment, Test Governance, Scaffolder, TypeScript/Vue syntax, Architecture, Operations, Production Readiness, Application Shell, T01~T09 Template, Interaction, Grid Productivity, T04/T05 Golden, T02/T03 Lifecycle, v29/v30 Navigation, Component Catalog, Design/Figma parity, Release Governance를 모두 통과해야 한다.

Runtime validation boundary

현재 artifact 환경에는 .NET SDK, 실행 PostgreSQL/API, 설치된 pnpm dependencies, Playwright browser runtime이 보장되지 않는다. 따라서 ASP.NET Core runtime, 실제 DB migration, Vitest runtime, Playwright browser 실행 완료를 주장하지 않는다.

반면 Node 기반 KBX Governance Gate와 TypeScript/Vue syntax transpile은 실제 실행하여 PASS한다.

2.0 KiB Raw Blame History