kjh2064
c41e5063b7
Removed entire kbx-foundation-v36 directory as it's been replaced by the new KBX Foundation v4 patterns implemented in this session: - Registry-driven screen definitions - Density-aware UI adapter components - Feature module templates (ShadowRun, Models) Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
KBX Governance
foundationIteration은 내부 구현 진화 번호이며 KBX public UX contract의 SemVer와 동일하지 않습니다.
contractVersion: KBX Business UX/AX / Design System / Reference / Implementation Contract 기준 버전.baseline: 이전 Foundation generated contract snapshot.declaredChangeLevel:none | patch | minor | major.- CI가 current manifest와 baseline을 비교하여 최소 필요한 change level을 계산합니다.
판단
- Component/Screen/Token 제거 또는 이름 변경:
major - 공개 Component/Screen 추가:
minor - Component version의 major 증가:
major - Component version의 minor 증가:
minor - Component version의 patch 증가:
patch - Semantic/Component token 값 변경:
visual-risk+ 최소patch - 내부 구현만 변경:
patch또는none
Foundation v12는 이 정책을 처음 적용하는 baseline-adoption release입니다.
v18 test governance
Canonical executable scenarios and synthetic fixture contracts live under contracts/testing/. Test scenario changes are tracked as patch-level internal contracts; they do not imply a runtime public API change.
v35 screen recipe governance
T01~T09 implementation recipes live in contracts/screens/kbx.screen-recipes.json. templateCode is a public Screen contract property. Screen type/template identity changes and recipe security-policy removal are release-impact tracked. Mutating scaffold recipes fail closed without explicit write permission.