Repository navigation
Render Tree and Terrain verbatim against fixture data #9
Description
Part of #1
Question
Get mindwalk's two scenes rendering inside apps/web against fixture data, before any adaptation. This is the known-good baseline everything else is judged against.
Copy near-verbatim from .repos/mindwalk/web/src, under the MIT notice:
scene/—CityScene.tsx(638),TreeScene.tsx(656),treeLayout.ts(169),sceneUtils.ts(144),dirLabels.ts(145),trail.ts(79),textures.ts(60)playback/—reducer.ts,recorder.ts(251 total)types.ts(271)
Do not copy App.tsx (876), state/ (123), or api/ (74) — that is mindwalk's shell talking to its Go server, and T3 has its own. Do not copy styles.css wholesale; styling is the next ticket.
Why verbatim. This code is where mistranslation renders almost right — squarified rect math, instanced-mesh buffer indexing, coordinate conventions, colour-space handling. Those cost days to bisect. A mistranslated shell just fails to compile.
Set-up constraints from charting: three.js + react-three-fiber, lazy-loaded as its own chunk, frameloop="demand" by default with a continuous loop only while playback runs. There are no 3D dependencies in the repo today, so this ticket adds them.
Reference to compare against: a local mindwalk serve renders the same repo. Compare screenshot by screenshot — Tree and Terrain both, they have equal billing. Fixture data can come from GET /api/sessions/<key>/citymap and /trace on that instance, or from the citymap service once it lands.
Resolved when both views render this repo's citymap in T3's web app and visibly match the reference.
Activity
Dillpickleschmidt commentedon Aug 1, 2026
Resolution
Both scenes render this repo's citymap inside the T3 web app and visibly match a live
mindwalk servereference. Landed on branchfeat/3d-scenes-verbatim.?map=1)Same structure, palette, labels, and camera behavior in both views. The T3 side has no HUD, timeline, or repo header — that chrome is Restyle the ported UI to T3 conventions scope.
What landed
scene/(all seven files),playback/(both files), andtypes.tsintoapps/web/src/mindwalk/, preserving relative structure so imports survived unchanged. MIT attribution inapps/web/THIRD_PARTY_NOTICES.mdplus a provenance README in the directory.App.tsx,state/,api/, andstyles.csswere not copied, per the ticket.noUncheckedIndexedAccess+exactOptionalPropertyTypes(mindwalk compiles without either), and the repo's pre-commitvp fmtautoformat. Everything erases at runtime.three@^0.182.0(mindwalk's exact minor) +@types/three./mindwalk-3d?threadId=<id>route. React.lazy splits three.js and the scenes into their own chunk; the citymap comes fromGET /api/citymap/threads/:threadIdviaPrimaryEnvironmentHttpClient. No trace yet, so playback is permanently empty and CityScene runslocHeights— exactly mindwalk's?map=1static-map mode, which is also what the reference screenshots use..city-scenefill,.scene-tipchip) copied into a scopedharness.css; the 2,452-linestyles.cssstays untouched for Restyle the ported UI to T3 conventions #10.Surprise worth recording
The map's standing decision said "three.js + react-three-fiber", but mindwalk does not use react-three-fiber — its scenes are plain three.js components driving their own
requestAnimationFrameloops (auto-rotate, damping, label easing). So no r3f was added, and theframeloop="demand"constraint doesn't map onto anything as-is. Of the three charting constraints: lazy chunk done, the other two now mean pausing mindwalk's own rAF loops when the tab is hidden or the surface inactive — sharpened in the map's fog.Verification notes
vp run dev --home-dir .t3stack seeded with a snapshot of real userdata (the t3-code preview MCP surface was down; snapshot/evaluate failed even onabout:blank)./home/dylank/Projects/t3code, so both sides mapped the identical tree.pnpm typecheckclean inapps/web.fix(web): clear the citymap when the mindwalk harness loses its threadId
fix(web): clear the citymap when the mindwalk harness loses its threadId