[wass08]

What does this PR do?

A frontier model writes a whole design as free three.js, richer than tool-by-tool building; author_scene then turns it into native, editable Pascal nodes in one MCP call. The agent reads its own module any way it likes and sends a payload: levels, walls as centerlines with openings (type, style, hinge, exact colours, or a module for a non-standard one), rooms with a seed point and a floor finish, slabs, columns, railings, every piece of furniture as an authored object with its own module, lights. Pascal compiles and stores the modules, derives rooms, floors and ceilings, paints, runs its checks and answers a gate report: defects by the agent's own ids, warnings, defaults (what Pascal filled in), snapped wall ends, an ids map, verify_scene. The module and the agent's adapter are kept with the scene. replace: true writes over a previous conversion with fresh ids.

Pascal fixes that came out of eight fresh-agent conversions (GPT-6 Astra and Claude Opus, flats, a bedroom, a two-storey house, a living room from a photo):

• Finish scripts: a room's floor and a wall face can carry a module built for exactly that polygon or face, cut by Pascal to the region and its openings, rebuilt by the structure reconcile when the room or wall changes, and measured: the report warns when a finish leaves part of the floor or face bare. The native wall skirting is exposed in the payload.
• The compiler bakes the back face of double-sided materials (the viewer draws front faces only), so a curtain built as a plane shows.
• A new door's handle hangs opposite its hinges (add_door too); a slab lying on a wall's top is its cap, never its support; a wall's room side is read from the plan; a room-edge push keeps a painted wall's finishes and children.
• verify_scene reads hosted items through their host, lets stacked things stack, and keeps a door's keep-out to its swing side.
• An authored object's glass stays Pascal's glass; exact slot colours keep the module's roughness and metalness; a light with no fixture becomes a ceiling point in its room; a wall-hosted item keeps its distance from the face.
• A preview colour for every textured library material.

The tool is MCP-first: it is not in AGENT_TOOL_CONTRACTS until the chat can run it; the private app registers it with the hosted effects.

How to test

1. bun test in packages/core, packages/mcp, packages/geometry-script, packages/nodes, packages/editor and packages/viewer/src/systems/wall: all green on this branch.
2. packages/mcp/src/tools/author-scene.test.ts runs the whole thing through a real MCP client and the real compiler: a bedroom payload with a scripted window, a glass door, a baseboard on a wall, a plank floor module laid past the room edge, a tile face module laid over a window, sage on one wall face; it reads the nodes back with get_node and get_source. Expect the room written, the floor and face builds cut to their regions, the glass slot on library:preset-glass, and a finish_gaps warning on the floor module that leaves a strip bare.
3. Against a running server (the private app with PASCAL_SERVER_SCRIPT_COMPILE=1, or a local editor with a script host): call author_scene with bench-style payload of four walls, a door, a window, a floorCode and a wallCode; open the project; expect walls, openings, a room with the scripted floor, tiled faces, skirting; move a wall and expect the floor and face scripts to rebuild. The eight converted projects on the owner's :3008 are the reference.
4. bun run check-types: two errors remain in packages/editor/src/components/systems/ceiling/ceiling-bracket-batch.test.ts, unchanged since the base commit (deps refresh [Deps] chore(deps): refresh MCP, rendering, framework and CSS dependencies #1037), not from this branch.

Screenshots / screen recording

Not added yet. (Pictures of the converted scenes beside the raw three.js renders are in the private repo's bench/author-scene/briefs/.)

Checklist

• I've tested this locally with bun dev (through the private community app on :3008 against these packages, eight agent conversions end to end)
• My code follows the existing code style (run bun check to verify)
• I've updated relevant documentation (if applicable)
• This PR targets the main branch

🤖 Generated with Claude Code

---

Note

Medium Risk
Large new conversion pipeline touches scene structure, materials, and agent tools; layout/clearance logic changes affect verify_scene behavior across furnished scenes.

Overview
Adds author_scene, a one-shot path from an agent’s three.js design payload to native scene nodes: walls (join snapping, openings, skirting, paint), rooms/zones, slabs, items, lights, materials, structure reconcile, and a detailed report (defects, warnings, defaults, stable ids). Hosts compile modules first; floor/face finish scripts are listed for post-write compilation via new setRoomFloorScript / setWallFaceScript and refreshFinishScripts.

get_source now resolves room floor scripts and wall face scripts (readableScript + optional face). Paint blocks scripted faces/floors and supports trim roles like skirting on both faces.

Layout verification is tightened: item-space transforms hosted item footprints/heights; door keepouts respect swing direction and height; rugs, wall-mounted items, and stacked host/child items are excluded from false positives. Doors default handle opposite hinges (handleSide on add_door / create-room).

Large author-scene.test.ts and related tests cover conversion, materials, lights, skirting, and script defects.

^{Reviewed by Cursor Bugbot for commit e52c6e1. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 4 potential issues.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit e52c6e1. Configure here.}

[cursor]

Duplicate payload IDs overwrite across levels

High Severity

Wall and item ids are stored in global maps keyed only by the payload id, with no level prefix and no uniqueness check. A second storey that reuses names such as north or bed overwrites the first storey’s compiled module, report.ids entry, light fixture, and face-script target, so those nodes get the wrong geometry or are skipped with no defect.

Additional Locations (2)

• packages/mcp/src/tools/author-scene.ts#L77-L85
• packages/core/src/agent-operations/author-scene.ts#L910-L915

 

^{Reviewed by Cursor Bugbot for commit e52c6e1. Configure here.}

[cursor]

Level elevation is never applied

Medium Severity

The payload’s elevation is stored only on metadata.authorScene and is not written to baseElevation or height, nor reported in defaults. Upper storeys sit on Pascal’s wall-derived stack even when the agent gave a different floor height.

 

^{Reviewed by Cursor Bugbot for commit e52c6e1. Configure here.}

[cursor]

Invalid region finish is still written

Medium Severity

When finishRef rejects a floor region colour, the code still stores the raw r.finish string on the zone. The room’s main floor finish correctly stays unset on the same error, so a bad region colour either crashes ZoneNode.parse or persists an invalid material.

 

^{Reviewed by Cursor Bugbot for commit e52c6e1. Configure here.}

[cursor]

Column colour is silently dropped

Low Severity

A column’s color is copied into metadata.authorScene and never passed through finishRef or paint. Walls, slabs, openings, and rooms in the same function apply payload colours. The column is written unpainted with no defaults or defects entry.

 

^{Reviewed by Cursor Bugbot for commit e52c6e1. Configure here.}