Release planning

CadCraft 0.9 impact map

Every fix and feature lined up for 0.9, and what each one touches: which apps, and which layers of the stack.

ProjectCadCraft
Sheet0.9 impact
Items273
Date2026-11-09
115Fix
147Feature
4Spike
0Platform
0Site ops
0Sanity check
7Decision
≈ 0days in the written 0.9 plans
  • Planned 0 on the plan for the release it is filed under
  • Built 271 built and working in /lab (the dev builds). Whether the public has it is its reach: "in the lab", "Live" (the last gate) or "switched off"; see docs/REACH-LIVE.md
  • Partly built 1 part of it is built in /lab; the rest waits (see "Waits on")
  • Promised 0 the live site already says it is coming
  • Moved 0 moved here from an earlier release or wishlist
  • Found 0 bug found after a release shipped; fixed in a point release or the next one
  • Candidate 0 recommended in a spike or session log; owner to choose
  • Community please test 0 built and in /use; a Discord post gives the steps and the expected result and asks people to try it on their own devices, files or know-how
  • Decision Time 0 a decision, check, file, key, flag or go only you can give; folds into the list once answered

Built means built and working in the lab. Live means the public can use it, and is the last gate: 270 Built · Live, 1 Built · in the lab.

Sheet 1 · impact areas

Where 0.9 lands

How many items touch each app and each layer, by kind. One item can touch several areas, so the rows add up to more than the item count. Pick a row to filter the schedule below.

Impact areaFixFeatureSpikePlatformSite opsSanity checkDecisionAll
Apps
CadCraft 38 36 – – – – 2 76
BimCraft 27 53 2 – – – – 82
ModelCraft 19 45 2 – – – 2 68
MarkupCraft 16 11 – – – – – 27
TakeoffCraft 18 7 – – – – – 25
CivilCraft 14 32 – – – – – 46
DetailCraft 13 13 – – – – – 26
PartCraft 18 27 1 – – – – 46
Studio 2 5 1 – – – – 8
SuperCad Studio 22 17 – – – – – 39
Layers
Site and services 7 11 – – – – 5 23
Desktop host 1 1 1 – – – – 3
App shell 2 1 – – – – – 3
App code 10 28 3 – – – 3 44
Our engines – 12 1 – – – 1 14
Vendor engines – – – – – – – 0
Drawing surface – – – – – – – 0
Help and words 1 2 – – – – 1 4
Tests and tooling – – – – – – – 0

Sheet 2 · schedule

Every fix and feature

Grouped by track. App chips carry each app’s layer colour; Studio is in ink. "Waits on" names what has to happen first; the small lines under it say who asked and where the item is written up.

Add an item Fork map (Rust and C++ forks) The roadmap

Issues sync every 10 minutes; last sync Nov 9, 2026 7:00 pm.

ItemWhatAppsLayersStatusDaysWaits onIssues
Decision Time 5
DecisionAO.8 Link to AO.8Comment on AO.8 Send the add-on posts

Approve and send the drafted "Build an add-on" and Apparel news and Discord posts.

CadCraft Site and services Built · Live – You: publish From: asked of the owner by: addons-posts-draft (Session) addons-posts-draft
DecisionLIB-PUBLIC Link to LIB-PUBLICComment on LIB-PUBLIC Make Library public

Set LIBRARY_PUBLIC=1 after the library decisions below; residential, entourage and standard-part items wait on it.

– Site and services Built · Live – You: flag From: asked of the owner by: TASKS, render, bim-residential (Session) TASKS, render, bim-residential
DecisionMEP-REL Link to MEP-RELComment on MEP-REL Release the HVAC and piping add-ons

List them on /addons; a mechanical or plumbing professional reviews the labelled defaults.

CadCraft App codeSite and services Built · Live – Review is community test MEP-REL-HAND (not blocking) From: asked of the owner by: cad-mep (Session) cad-mep
Fixes 104
FixFX.58 Link to FX.58Comment on FX.58 BimCraft wall Length in Properties (5000) differs from the plan dimension (5092) with no stated reference

Reported 2026-11-05 in Duncan's wall tool specification (page 1). In the Room 1 test the Properties panel showed Length 5000 while the plan dimension on the same wall read 5092; nothing says which reference each figure uses (location line, finish face, core, centreline, or end-to-end after joins). Wanted: both figures name their reference, and they agree or the difference is explained. Cause not investigated yet. Status: not started. Tracked as a document with status notes: /roadmap-internal, 'BimCraft wall tool specification' (docs/team-roadmap/bimcraft-wall-tool-specification.md). Source PDF: dropai.zone/d/vRSxnoBw. wall-fix 2026-11-05: CORRECTION: FX.22 already added Measure from (centre | inside | outside) to the Length field (wall-square.js lengthFrom) so 5000 vs 5092 can be explained; whether the plan dimension and the Properties field now agree by default, and name their reference, is not checked (spec test 9, decision D3). walls-09 2026-11-06: Length and the plan's wall dimension now read the same reference, named on the model bar (Measure from: centre line by default, decision D3; inside or outside face) and in Properties; spec test 9 Pass (node: both 5000 on centre line, both 5114.3 on the outside face). Cause of Room 1's 5000 vs 5092, from reading: Length read the centre line while the plan dimension read the outside face; NOT reproduced on Duncan's own file (we do not have it). The hand check is part of WT.3-HAND.

BimCraft Built · Live 1 – From: Duncan (Session) Duncan, wall tool specification 2026-11-05
FixFX.59 Link to FX.59Comment on FX.59 CadCraft 2D plan walls: joins are found by position at each edit, not stored; same edit rules as BimCraft wanted

Wall tool spec (Duncan, 2026-11-05), tracked at /roadmap-internal 'BimCraft wall tool specification'. Assessed 2026-11-05 as part of FX.57. CadCraft's plan walls (lib/plan2d/walls.js, used by app/walls-cmd.js) have their own engine. followMoves already carries a wall joined end to end and slides a T end along its own line, which is more than BimCraft's Move does. But joins are still guessed from end positions each time (no join record), there is no Disallow join or Split that keeps joins, and a typed length or a thickness change has not been checked against the five rules (joined walls follow and stay joined, selected wall moves and the reference holds, location line holds, one undo step, Length and dimension name their reference). Wanted: run the spec's nine tests (they are plan-view, they apply as written) against CadCraft, fix what fails, and share the join record with FX.60. Not tried yet; nothing changed. Page 3 check (2026-11-05): followMoves puts a shared end at the moved end and leaves the far end, so a neighbour turns when a wall is moved sideways (finding 2 applies here too: FX.63); T ends already slide (finding 3 does not apply). Move already follows joins (finding 1 does not apply). walls-plan-09 2026-11-06 (done): Built in /lab: CadCraft plan walls store their joins. Each wall has its own id and the join records (end meets start, end meets mid for a T, mid meets mid for a crossing: the same record as BimCraft, rules in lib/walls/joins.js, checked equal to BimCraft's wall-joins.js); both walls carry it, in the... see docs/0.9-sessions/walls-plan-09.md.

CadCraft Built · Live 1 Hand check is community test WTPLAN-HAND (not blocking) From: Duncan (Session) Duncan, wall tool specification 2026-11-05 (page 2)
FixFX.61 Link to FX.61Comment on FX.61 Apps that read or draw walls (DetailCraft, TakeoffCraft, CivilCraft hardscape): check what stored joins change

Wall tool spec (Duncan, 2026-11-05), tracked at /roadmap-internal 'BimCraft wall tool specification'. Assessed 2026-11-05, no change yet. DetailCraft: wallPanel frames one wall at a time (lib: framing.js); corner and T framing (extra studs, backers) would follow a join record once it exists. TakeoffCraft: scene3d wall strips and wallOutline use mitred joints for takeoff; counts should not change, but check them against BimCraft's net-of-joins quantities after FX.57. CivilCraft landscape: hardscape walls (retaining / freestanding polylines) have no join model; two garden walls meeting at a T are drawn as separate runs. Wanted: after FX.57 lands, re-run each app's wall quantities and drawings on a joined-wall file and file a row for each real difference; do not add join code to these apps by hand. ModelCraft (print-walls is wall thickness for printing), MarkupCraft and PartCraft have no joined walls. walls-plan-09 2026-11-06: Checked 2026-11-06 (read the code and measured): DetailCraft, TakeoffCraft and CivilCraft hardscape read neither the join record, nor a wall's thickness, nor CADCRAFT_WALL. DetailCraft wallPanel takes a spec (length, height, openings, stud sizes); TakeoffCraft's wallOutline is its own mitred run with a thickness it is given; CivilCraft hardscape walls are open polylines with their own thickness. Measured: a CadCraft DXF of a four-wall room opened with TakeoffCraft's and CivilCraft's readers gives 4 INSERTs and 8 LINEs in 4 anonymous blocks, extended data kept, nothing else read; so a stored join changes none of their quantities. What would change: nothing breaks. Corner and T framing in DetailCraft and joined hardscape runs in CivilCraft would be NEW features that could read the record (no row made: nothing differs today). Not run on a BimCraft IFC with join records through DetailCraft's IFC export (that it keeps the unknown relationship lines is untested).

TakeoffCraftCivilCraftDetailCraft Built · Live 1 – From: Duncan (Session) Duncan, wall tool specification 2026-11-05 (page 2)
FixFX.65 Link to FX.65Comment on FX.65 BimCraft thickness / type change: the corner follows only when exactly one straight wall meets the end

Wall tool spec page 3 (Duncan, 2026-11-05), tracked at /roadmap-internal 'BimCraft wall tool specification'. Code checked in the a Discord member source 2026-11-05 (the spec read commit a538e43). Found while checking the 'Already right, keep it' list on page 3: updateWall, the location-line shift (changes.justification not centre): neighbours are looked up and then skipped unless nbs.length === 1 and the neighbour is not curved. So a thicker wall at a three-wall node, at a T, or next to a curved wall keeps its old corner and the junction is left open or overlapped, while the two-wall straight corner case Duncan tested works. Wanted: spec test 5 (set the location line to the exterior face, thicken the wall: exterior face does not move, wall grows inward, joins clean up) at L, T, X and curved neighbours. Not reproduced yet; nothing fixed. Other apps: the same question applies to CadCraft's plan walls (thickness change) and goes into FX.59's test run. walls-09 2026-11-06: Fixed in /lab: a location line that holds now moves the centre line square with the join solver (squareMove), so the corner follows at an L, at a node of three walls, at a T (the partition comes with it) and next to a curved wall. Spec test 5 Pass: node (--walltools) and the real page (outside face held at -92.1 with 300 thickness, both corners follow).

CadCraftBimCraft Built · Live 1 – From: Duncan (Session) Duncan, wall tool specification 2026-11-05 (page 3)
FixFX.66 Link to FX.66Comment on FX.66 Wall + Move / Copy: a moved or copied group of rooms does not stretch the joined walls outside the group

Wall tool spec page 9, 'How other tools combine with the wall' (Duncan, 2026-11-05), tracked at /roadmap-internal 'BimCraft wall tool specification'. Code checked in the a Discord member source 2026-11-05. Spec: move or copy a group of rooms and every joined wall outside the group stretches to stay joined (Place in space -> Join solver -> Follow; today Partly). Cause, from reading: Move is carryJoined: false (FX.62), and a copy goes through addWall (model-modify.js), so the copied walls are new walls that are not joined to anything outside the group, and nothing stretches. Wanted: Move stretches the outside neighbours (their ends slide along their own line, FX.63 / FX.60); Copy leaves the originals alone and makes the copies joined among themselves. Acceptance: spec test 1 style on a two-room plan, one undo step. OTHER APPS: CadCraft plan walls Move already follows joins (FX.59 notes the turning problem); Copy there is not checked. Not started. walls-09 2026-11-06: Checked, no code change needed after FX.62: a Move of a group of walls (one room of two) keeps the group's corners and the walls outside stay joined; Copy leaves the originals and the copies are joined among themselves (two corners). One undo step. Test: node bin/test-bimcraft.mjs --walltools (FX.66 block). Real page: the Move tool's group move was not driven in a browser by this session.

CadCraftBimCraft Built · Live 1 – From: Duncan (Session) Duncan, wall tool specification 2026-11-05 (page 9)
FixFX.67 Link to FX.67Comment on FX.67 Wall Length and typed dimension: no choice of fixed end, no marker for the fixed side, no modifier-key drag to break a join

Wall tool spec pages 11-12 (Duncan, 2026-11-05), tracked at /roadmap-internal 'BimCraft wall tool specification'. Checked in the a Discord member source 2026-11-05. Page 11 'BimCraft must' column, three things the code does not do: (1) Changing length: 'start end fixed by default; toggle to grow from the other end or the centre'. setLength (wall-square.js) always keeps the start end and moves the end; there is no toggle. (2) Typing a dimension value: 'a marker shows the fixed side before Enter'. No marker exists; the fixed side is not shown. (3) Breaking a join: 'only by Split, Disallow join, delete, or a modifier-key drag'. No modifier-key drag breaks a join (Split and Disallow join are WT.4 and WT.5). Wanted: a Grow from control on the Length field (start | end | centre) with the fixed side drawn on the plan while the field is focused, and a modifier-key drag (Revit's Move with Disjoin) that moves a wall without carrying its joins and keeps the wall's id. Spec tests 3 and 9. OTHER APPS: CadCraft plan walls have no Length field or toggle either (FX.59). Not started. walls-09 2026-11-06: Built in /lab: Properties › Grow from (Start holds | End holds | Centre holds) next to Length; the side that holds is marked on the plan while the Length field is in use; Alt + drag of the middle grip moves the wall free of its joins (they break, the id stays). Tests: --walltools (grow from end and centre, marker point), browser-walltools (grow from end, marker, Alt-drag).

CadCraftBimCraftSuperCad Studio Built · Live 1 – From: Duncan (Session) Duncan, wall tool specification 2026-11-05 (page 11)
FixFX.68 Link to FX.68Comment on FX.68 BimCraft lab: picking a wall with Draw off threw in the Properties panel (FX.22 read the drawing data that only exists while Draw is on)

Found 2026-11-05 by suggestions-followup-09 while fixing tools/ids/browser-bimcraft.mjs: with an IFC open and Draw off, picking a wall (for example from Problems) logged "TypeError: Cannot read properties of null (reading 'walls') at propsBlock" (model-ui.js). Cause: FX.22 (wall grips, Measure from) read S.data.walls, which is null unless Draw is on; propsBlock's own data (S.data when drawing, else a snapshot of the model) is the right source. The error was caught, so the panel just lacked the wall's Measure from and Length fields. Fix: one word in model-ui.js (all = data.walls). Lab only (FX.22 is 0.9 /lab); released 0.8.1 does not have the code. Checked 2026-11-05: in the real page (lab BimCraft, house fixture, Draw off) a picked wall shows Measure from + Length and no console error; tools/ids/browser-bimcraft.mjs 30/0 (its 'no page errors' check), tools/bimcraft-test/wall-square-test.mjs 67/0, browser-wallsquare.mjs 28/0.

BimCraft Built · Live 0.1 – From: session (Session) docs/0.9-sessions/suggestions-sweep-09.md § Follow-up
FixFX.69 Link to FX.69Comment on FX.69 Two stale tests: TakeoffCraft learn.mjs expected the released build to ignore learn data; the BimCraft IDS browser test clicked a folded Undo

Found by suggestions-sweep-09 (2026-11-05), fixed by suggestions-followup-09 the same day; tests only, no app change (the app fix found on the way is the row above). (1) tools/takeoffcraft-test/learn.mjs loaded `current` as "the frozen release before learn"; current is 0.8.1 since 2026-11-02 and ships learn.js (identical to 0.8 and a Discord member). Now: the newest frozen folder WITHOUT learn.js (0.7) must ignore the section, and current (0.8.1) must read it back identical. Before 104/1, after 107/0. (2) tools/ids/browser-bimcraft.mjs clicked [data-undo] / [data-save] in the left panel's Changes section, which the shell's Auto-focus panel (app-settings.js, on by default) folds while the IDS section is open: by design, not a regression. It now asserts that fold, undoes with the toolbar Undo and with Ctrl+Z (both proven to remove the IDS reference and its 13 problems; Ctrl+Y brings them back), saves with Ctrl+S, and waits for 'Saved' before reopening (sooner is refused with 'Still working on the last one…', correct). Before 13/1 (the run stopped at undo), after 30/0.

BimCraftTakeoffCraft Built · Live 0.1 – From: session (Session) docs/0.9-sessions/suggestions-sweep-09.md § Follow-up
FixFX.71 Link to FX.71Comment on FX.71 BimCraft test "dimensions retain IDs across redo, type swaps, flips, curves and rebinds" fails (tools/bimcraft-test/wall-precision.test.mjs)

Found 2026-11-05 while running the BimCraft suites for the join record (FX.60). node bin/test-bimcraft.mjs --walls: 6 of 7 pass; this one fails at wall-precision.test.mjs:65, after Undo then Redo of a saved wall dimension its GlobalId is a different one (readWallDimensions(...)[0].guid !== d.guid). It fails the same with the join sync switched off, so it is not from the join work; cause not looked into (a redo that runs the op again and makes a new GlobalId for the dimension is the likely shape). Wanted: Redo of a dimension keeps its id, like Redo of a wall type does (the test's first redo passes). Not started. walls-09 2026-11-06: Cause found: the CODE was wrong, not the test. saveWallDimension's op (wall-dimensions.js operation) drew a fresh GlobalId each time it ran, so Redo made the dimension again under a new id. It now hands out the same GlobalIds again on Redo, as model-ops.js op() does. node bin/test-bimcraft.mjs --walls: 15/0 (was 14/1).

BimCraft Built · Live 1 – test run 2026-11-05
FixFX.74 Link to FX.74Comment on FX.74 Suggestions and roadmap items link both ways in /admin

Staff can now link a /suggest ask to the roadmap item that builds it, from either page: /admin/suggestions shows each suggestion's linked items (key, title, release) with Unlink and a Link to roadmap box (item key like FX.26, release:key, or #id); the item's edit page has a Suggestions panel (linked asks with status and votes, Link a suggestion by number, Unlink). Staff only; linking tells nobody. RoadmapSuggestions + migration 125 (roadmap_item_suggestions, nothing deleted). Checked 2026-11-06 in code: link, duplicate refusal, both-way reads and unlink against the live database. Pages linted; not yet viewed in a browser.

– Built · Live – – From: session (Session) owner request 2026-11-06
FixFX.75 Link to FX.75Comment on FX.75 Vector layout: palette icon highlight no longer spans neighbouring tools

In the Vector layout the Basic palette's icons overlapped: the pressed Select cell was highlighted across Select and Hand together, and the Tool Sets rows were squeezed. The ribbon rule for compact tools (min width 5.2rem, dense height 1.25rem) outranked the palette's own sizing, so each cell rendered 83 x 20 px. The palette rules in assets/css/app-workspace.css now sit under .vw-toolpalette and win over it: every Basic cell is a 40 x 40 square lit on its own, and Tool Sets rows keep their height. One stylesheet, so all eight apps. Checked by measuring the cells in ModelCraft in a headless browser; the screenshot showed one lit cell.

– Built · Live – – From: session (Session) owner screenshot 2026-11-06
FixFX.77 Link to FX.77Comment on FX.77 Studio and browser-edition packers: stale file lists (suite stubs, hub files, docinfo and About modules)

Found by mounts-09 2026-11-06 while building the Studio suite for the undo test. (1) studio/pack/suite-stubs.php WORKSPACE_MODULES lacked app-workspace-icons.js and app-workspace-vector.js, so node pack/suite.mjs stopped with "a plain re-render differs from the edition's index.html" for every app: a Studio rebuild could not have been made. (2) pack/suite.mjs HUB_FILES did not copy the new hub/undo-journal.js. (3) tools/shell-test/test-packed-imports.mjs failed 6 checks: devshell/edition.php and devshell/pack.php lacked docinfo.js, app-docinfo.js and app-about.js (DI.1, ABT.1), so packaged editions would have asked for files that are not there. All three lists fixed; the suite packs for cadcraft, detailcraft and takeoffcraft and the test reports "all packers list every imported shell file". The full eight-app suite was not rebuilt here.

CadCraftBimCraftModelCraftMarkupCraftTakeoffCraftCivilCraftDetailCraftPartCraft Built · Live 0.5 – docs/0.9-sessions/mounts-09.md
FixFX.78 Link to FX.78Comment on FX.78 Tests: the team button sits in a folded panel section; add-on buttons are not registry commands

mounts-09 2026-11-06: tools/bimcraft-test/browser-r5.mjs clicked [data-model-team] while the shell's panel accordion had its section folded (a person opens the section first; the test now does too). tools/shell-test/browser-input-apps.mjs's "every toolbar button is a registry command" no longer lists add-on buttons (data-addon-tool), as print-09 asked; ModelCraft's 3D Print button passes. Still failing there, not from this session: "Move the Tools toolbar" (the toolbar tear grip) and the Settings style-card radio that is not visible; and tools/civil-mount-test/browser.mjs la4 clicks the first of two "Ground modifiers" menu items, which is hidden.

CadCraftBimCraftModelCraftMarkupCraftTakeoffCraftCivilCraftDetailCraftPartCraft Built · Live 0.5 – docs/0.9-sessions/mounts-09.md
FixFX.79 Link to FX.79Comment on FX.79 ModelCraft Surfaces solids test opens the folded Surfaces section first

tools/modelcraft-test/browser-solids.mjs failed before any change of 2026-11-06: the right panel now folds its sections (app-settings.js, one open at a time), so the Surfaces button was not visible. The test now clicks the Surfaces heading when the section is folded (as a person does), and expects 9 Solids commands (+ Fillet between faces, Thicken into a solid, SU.747c); PartCraft's browser-solids.mjs the same count. Both pass (14/0, 18/0). Not fixed here: ModelCraft's browser-trim.mjs, browser-scanfit.mjs and tools/nurbs/browser-scanfit-09.mjs open the panel the same old way (listed in docs/0.9-sessions/nurbs-s3-09.md § Found).

ModelCraftPartCraft Built · Live 0.1 – docs/0.9-sessions/nurbs-s3-09.md
FixFX.128 Link to FX.128Comment on FX.128 Team member pictures: built-in defaults, upload, change

SuperCad Teams member page showed only a letter in a circle. A person now has a picture: the default is their initials on a colour, or one of 12 built-in pictures in 8 colours, or an uploaded image (cut to a 128 px square in the page, kept under 24 KB). Change it under Details > Edit. Stored on the person row (people.avatar, account DB schema 4), synced like title and company; the server and the plug-in both refuse anything that is not a built-in or a small png/jpeg/webp. Tests added (teams 310, user-teams 116). Not done: the account's own profile picture is not used as the default; no website member page picture; other-language strings still English; never opened in a real browser window.

SuperCad Studio Built · Live 0.2 –
FixFX.129 Link to FX.129Comment on FX.129 Teams page flashed an empty list for about 1.5 s before the members appeared

On a fresh load the Teams page drew its empty states until the account connected and the first sync brought the rows in. Now the page says 'Loading your teams (N teams, N people)' with a spinner while the first sync of the visit is pending. Where the count comes from, in order: (1) the account itself: app-shell.inc prints #cc-account-hints {teams:{teams,people}} for the signed-in person on /lab/supercadcraft (UserTeams::hint: two counts, never creates a database), so it works in a browser that has never synced; (2) otherwise a marker this browser kept at its last good sync. A hint of none wins over an older marker. It gives up after 15 s and tells the truth (empty, or the sync error); an account with no teams sees the empty state at once. Tests: teams 321, user-teams 118. Not done: the rows themselves are not cached locally; the hint is only printed for signed-in site sessions (a device-token-only window falls back to the browser marker); never opened in a real browser window.

SuperCad Studio Built · Live 0.1 –
Wall tool 4
FeatureWT.2 Link to WT.2Comment on WT.2 Wall tool, Draw: rectangle, rotated rectangle, polygon, arc by centre, tangent arc, pick one line, trace outline

Wall tool spec pages 4-8 (Duncan, 2026-11-05), tracked at /roadmap-internal 'BimCraft wall tool specification'. Icons: the DU.1 family (assets/js/app-workspace-icons.js: 32 grid, 1.5 round stroke, two-tone fills, Full Color or Outline). Not built (page 5): Rectangle (four walls, four corner joins, one action), Rotated rectangle, Polygon (inscribed / circumscribed), Arc by centre (centre, radius, sweep), Tangent arc (continues from the last segment), Pick lines (one line or edge at a time; Tab picks the chain; today only a whole DWG / DXF / PDF scan), Trace outline (click inside a closed area; today only 'Develop this mass'). Each is a recipe on the Place block (addWall, Wall tool, model-trace.js) ending in the join solver (FX.60); the Shape list on the Wall button holds the shapes. Icons: wallrect, wallrectrot, wallpoly, wallarcc, walltan, wallpick, walltrace. OTHER APPS: CadCraft already has rectangle and polygon as drawing tools but not as walls with joined corners: its plan walls (FX.59) should get the same recipes from one shared place. Not started. walls-09 2026-11-06 (done): Built in /lab: Wall › Shape list and the new Shapes menu (DU.1 icons wallrect, wallrectrot, wallpoly, wallarcc, walltan, wallpick, walltrace; commands wall.rect ... wall.trace): rectangle (four walls, four L joins, one undo step), rotated rectangle, polygon inscribed / circumscribed (3-64 sides), ar... see docs/0.9-sessions/walls-09.md. walls-plan-09 2026-11-06 (done): CadCraft plan walls: rectangle, rotated rectangle, polygon, arc (as 15 degree chords: plan walls are straight), tangent arc, pick lines, trace outline as WALLRECT, WALLROT, WALLPOLY, WALLARC, WALLTAN, WALLPICK, WALLTRACE, same gestures as RECTANG and POLYGON, one undo step each, corners joined. One ... see docs/0.9-sessions/walls-plan-09.md.

CadCraftBimCraftSuperCad Studio Built · Live 1 Hand check is community test WT.2-HAND (not blocking) From: Duncan (Session) Duncan, wall tool specification 2026-11-05 (pages 4-8)
FeatureWT.3 Link to WT.3Comment on WT.3 Wall tool, Set and Modify: placement offset, join on/off, edit by dimension, offset wall, box stretch, align and lock, lock dimension

Wall tool spec pages 4-8 (Duncan, 2026-11-05), tracked at /roadmap-internal 'BimCraft wall tool specification'. Icons: the DU.1 family (assets/js/app-workspace-icons.js: 32 grid, 1.5 round stroke, two-tone fills, Full Color or Outline). Pages 5-6. Partly or not built: Placement offset (a free distance off the picked line; today half a thickness), Join on / off (free-standing wall; today joins are always automatic), Edit by dimension (type a value: the selected wall moves, the reference holds; today typing does not move a wall: FX.58 / spec test 4), Offset wall (neighbours stretch), Box stretch (ends inside a marquee move, walls crossing it stretch), Align and lock (padlock holds the alignment), Lock dimension (a locked dimension holds through later edits). The last two are the new Hold block (wall-dimensions.js is the base: dimensions already know which face they measure). Icons: wallplace, walljoinsw, walleditdim, walloffset, wallbox, wallalignlock, walllockdim. OTHER APPS: CadCraft plan walls and dimensions want Hold too (it is the Revit padlock); build it once for both. Not started. walls-09 2026-11-06 (done): Built in /lab: placement offset and Join on/off in the Wall row (Wall tool and shapes); edit by dimension (type the value in a reference dimension's Properties: the second reference's wall moves square, the first holds; spec test 4 Pass); Offset (move or Copy); Box stretch; the Hold block (lib/walls... see docs/0.9-sessions/walls-09.md. walls-plan-09 2026-11-06 (done): CadCraft plan walls: placement offset and Join off in WALL (O, D), edit by dimension (WALLDIM), Offset (WALLOFFSET, Copy), box stretch (WALLSTRETCH), and the Hold block (WALLHOLD align and lock, WALLHOLDDIM, WALLUNHOLD, WALLHOLDS): stored on the wall, kept by moving the other side, refused with the ... see docs/0.9-sessions/walls-plan-09.md.

CadCraftBimCraftSuperCad Studio Built · Live 1 Hand check is community test WT.3-HAND (not blocking) From: Duncan (Session) Duncan, wall tool specification 2026-11-05 (pages 4-8)
FeatureWT.4 Link to WT.4Comment on WT.4 Wall tool, Cut: split, split with gap, delete segment

Wall tool spec pages 4-8 (Duncan, 2026-11-05), tracked at /roadmap-internal 'BimCraft wall tool specification'. Icons: the DU.1 family (assets/js/app-workspace-icons.js: 32 grid, 1.5 round stroke, two-tone fills, Full Color or Outline). Page 6-7. Not built (BimCraft's own help lists Split as not built): Split at a point or crossing wall (the two parts stay joined end to end, same type; decision D2 is whether they stay joined in line or become free ends), Split with gap (a set gap; rejoin restores one wall), Delete segment (remove the piece between two clicks). Spec test 6. Cut block today is model-trim.js (trim, extend, corner: Built). Icons: wallsplit, wallsplitgap, walldelseg. OTHER APPS: CadCraft plan walls have no Split either (FX.59 assessment); shared recipe. Not started. walls-09 2026-11-06: Built in /lab: Edit › Walls › Split (at the click or a crossing wall; Gap; Free ends), Delete segment, Rejoin (one wall again, the first keeps its id). Doors and windows go with their part, a cut through one is refused, reference dimensions follow their point. D2 default: the parts stay joined in line (Settings › BimCraft › Walls › When a wall is split: joined | free ends). Spec test 6 Pass (node and real page). Recipes in lib/walls (host-free; copied to bimcraft/a Discord member/walls by tools/walls/sync.mjs), BimCraft adapter wall-tools.js + wall-tools-ui.js. Tests: node lib/walls/test/test.mjs (59/0, known answers worked out in the file), node bin/test-bimcraft.mjs --walltools (all ok, incl. the spec's nine tests: all Pass), real page tools/bimcraft-test/browser-walltools.mjs 33/0. Help: wall-tools (en). NOT done: CadCraft, SuperCad adapter, hand check (WT.4-HAND). walls-plan-09 2026-11-06 (done): see docs/0.9-sessions/walls-plan-09.md.

CadCraftBimCraftSuperCad Studio Built · Live 1 Hand check is community test WT.4-HAND (not blocking) From: Duncan (Session) Duncan, wall tool specification 2026-11-05 (pages 4-8)
FeatureWT.7 Link to WT.7Comment on WT.7 Wall + Grid: lock walls to grid lines so they move with the grid

Wall tool spec page 9, 'How other tools combine with the wall' (Duncan, 2026-11-05), tracked at /roadmap-internal 'BimCraft wall tool specification'. Code checked in the a Discord member source 2026-11-05. Spec: snap walls to grid lines and lock them; move a grid line and its walls move with it (Hold -> Place in space -> Join solver; today Partly). Today (model-grids.js): grids are drawn, IfcGrid lines from other programs are read for display and snapping only; walls snap to them while drawing but nothing remembers the link, so moving a grid line moves no wall. Wanted: a wall end or location line can be locked to a grid line (the Hold block, with WT.3 Lock), moving the grid runs the join solver. OTHER APPS: CadCraft has grids too; build the lock once. Not started. walls-09 2026-11-06: Built in /lab: Properties › Lock to grid (a wall along a grid line, or an end on one), stored with the Hold block; Grid tool › pick a line › Move by (new: the UI could not move a grid line before) moves the line and the locked walls follow with their joined walls, one undo step; renaming keeps the lock, deleting the line drops it; moving a locked wall off its line is refused; a turned line that cannot keep the lock is refused. Recipes in lib/walls (host-free; copied to bimcraft/a Discord member/walls by tools/walls/sync.mjs), BimCraft adapter wall-tools.js + wall-tools-ui.js. Tests: node lib/walls/test/test.mjs (59/0, known answers worked out in the file), node bin/test-bimcraft.mjs --walltools (all ok, incl. the spec's nine tests: all Pass), real page tools/bimcraft-test/browser-walltools.mjs 33/0. Help: wall-tools (en). NOT done: CadCraft grids, SuperCad adapter, hand check (WT.7-HAND). walls-plan-09 2026-11-06 (done): see docs/0.9-sessions/walls-plan-09.md.

CadCraftBimCraftSuperCad Studio Built · Live 1 Hand check is community test WT.7-HAND (not blocking) From: Duncan (Session) Duncan, wall tool specification 2026-11-05 (page 9)
Suggest an item

Anyone can send one; no account and no name needed. The team reads each idea, and the ones we take on appear on this page. Please leave out web addresses.