A workshop for one house at a time

Can we shape one asset together while seeing each change? Implemented a local filesystem queue with bounded dimension/color requests, separate Blender app identity, immutable revision folders and a reusable personal habitat-blender-workshop skill. The original untitled Blender scene and the running Unity game were preserved. Native computer-use inspection observed 02-roof-review followed by the live 03-visible-loop save and changed roof. All three exact staged renders and metadata were individually inspected and approved; they are Blender studies, not gameplay or approved art direction. On 15 October 2026, scripts/Blender worker verification snapshot d20b4d71cb666999: 27/27 scoped pytest checks passed (15 request-boundary and 12 evidence tests); 3/3 saved revisions reopened with 4 checks each (12/12 checks), each containing 13 mesh objects; roof rises were 1.2, 0.8 and 1.0 metres, with corresponding measured source roof tops 3.84, 3.44 and 3.64 metres. Reports: [private evidence location omitted] and lifecycle-checks.json; requests and verification.json are preserved with each revision. Duplicate startup and overwrite were rejected; skill validation passed. Guards for switched scenes/outside files are installed but not interactively exercised; manual recovery is implemented but not tested with owner edits. The initial wrapper launch failed until its copied executable was locally signed; no installed app or system protection was changed. No other project chat was running in the initial inventory; no coordination acknowledgment is claimed. See docs/blender-workshop.md. Next: owner feedback on a single generic house proportion, silhouette or color; furniture and game integration remain outside this preparation.