- remode UI migrated to React 19 + Tailwind 4 + shadcn-style components
(tabs/toggles/tooltips/resizable/sonner); imperative kernel (SceneView,
TokenComposer, OpSuggest, PythonEditor, FeatureTreeView) bridged via refs
- composer: same op tip can be cited twice (dedupe guard removed; backspace
deletes the exact chip); capsule hover bubble is content-sized with a
560px/72vw max width
- renderer: shift+left-drag pan via TrackballControls keyState borrow
- server: submit payload never truncates user entity selections (cap
removed, regression test added)
- shared style.css imported into a cascade layer so Tailwind utilities win
Migrate the browser viewer from package schema 2.0 (objects array +
nested scene/scene.zip) to the canonical v3 layout (themed subpackages,
flat scene projection, content-addressed blob store); v2 packages are
rejected as unsupported.
- product-package.ts: v3 manifest gate plus structural validation
mirroring ProductPackage._validate_manifest (exact manifest key set,
path/hash-sorted unique records, root resolution, archive blob member
declarations, projection asset source resolution), exact member-set
closure with per-record sha256/byte_length verification, content_hash
and scene revision recomputation, and a definitions-vs-product_assets
identity multiset check. Scene geometry/entity/source assets are
materialized from blobs/<sha256> members through the projection
sources; product and feature-graph ZIP payloads are integrity-checked
as members but never re-packed, since the viewer never consumes them.
- main.ts: thread the loaded package schema into the footer label and
drop a dead constant; scene/entity sidecar 2.0 checks are unchanged.
- loader.test.ts: first viewer test suite (node:test via tsx, fixture
regenerated through prepare:example) covering the happy path and the
tamper matrix: mutated blob member, smuggled extra member, wrong
content_hash, and v2 manifest rejection.