Runtime Spine Composer v1
This release makes the app composition visible. XML files remain addressable blocks. Canonical models explain them. The spine binds them into an app. The composer shows and exports that binding.
Runtime hardening
declared → fetched → SHA verified → parsed → model matched → reader claimed → rendered.
Every block shows whether a reader claimed it, or whether it is visible only through fallback.
Chunks are checked for sequence and prev/curr continuity.
The browser reports verified, mismatch, unchecked, or missing for each declared source.
Composer model
XML block → canonical model → role → view hint → app-spine binding → sealed release
The Composer tab lets you adjust role, model, view hint, label, and enabled status as an overlay. It does not mutate /source.
Generated app-spine
The Generated Spine tab exports an <app-spine> XML header containing the current composition overlay. This is the exact object to carry into the next sealed release.
Routes
/apps/page-build/ /apps/interface-from-xml/ /apps/knowledge-tree/ /apps/skill-author/ /apps/compliance-audit-trail/ /apps/oracle-sql-free/ /apps/spine-suite/