Release planning

CadCraft 0.11 impact map

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

ProjectCadCraft
Sheet0.11 impact
Items799
Date2026-11-22
181Fix
383Feature
8Spike
35Platform
3Site ops
153Sanity check
36Decision
0Note
≈ 96days in the written 0.11 plans
  • Planned 45 on the plan for the release it is filed under
  • Built 449 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 32 part of it is built in /lab; the rest waits (see "Waits on")
  • Promised 3 the live site already says it is coming
  • Moved 2 moved here from an earlier release or wishlist
  • Found 2 bug found after a release shipped; fixed in a point release or the next one
  • Candidate 49 recommended in a spike or session log; owner to choose
  • Community please test 143 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 74 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: 3 Built · Live, 446 Built · in the lab.

Sheet 1 · impact areas

Where 0.11 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 checkDecisionNoteAll
Apps
CadCraft 89 154 4 10 1 51 11 – 320
BimCraft 79 178 5 10 2 70 18 – 362
ModelCraft 60 81 2 10 1 41 4 – 199
MarkupCraft 46 59 2 9 1 18 1 – 136
TakeoffCraft 50 59 2 9 1 21 3 – 145
CivilCraft 69 131 3 11 1 35 3 – 253
DetailCraft 58 61 2 9 1 26 2 – 159
PartCraft 57 78 2 9 1 37 3 – 187
Studio 12 43 3 9 1 30 5 – 103
SuperCad Studio 9 109 2 7 – 23 5 – 155
Layers
Site and services 15 25 – 10 2 2 8 – 62
Desktop host 7 22 2 10 – 7 2 – 50
App shell 25 32 – 7 – 4 2 – 70
App code 69 193 4 6 1 9 16 – 298
Our engines 8 71 3 1 – 4 10 – 97
Vendor engines – 2 – – – – 1 – 3
Drawing surface 1 – – – – 1 – – 2
Help and words 2 9 1 – – 2 – – 14
Tests and tooling 4 9 1 3 – 4 2 – 23

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 22, 2026 10:40 am.

ItemWhatAppsLayersStatusDaysWaits onIssues
Point clouds add-on (PC) 3
FeaturePC.9 Link to PC.9Comment on PC.9 Point clouds cleaned LAS 1.4 export

Built in the lab: classes and bounds re-read by our reader and laspy. Built in memory, so a huge cloud needs a streaming save. civil-points-09 2026-11-05: The cleaned LAS is written to a file chosen with showSaveFilePicker as it goes (one tile at a time); elsewhere it is gathered and downloaded with a size warning. Byte for byte equal to the gathered file, tested in the real page with a stand-in picker. pointcloud-11 2026-11-20: Streamed save of the cleaned cloud (built and tested in 0.9 with a stand-in for the browser's save window). The hand check with the real file picker and a very large cloud is PC.9-HAND; a LAZ of 2.1 GB (241 million points) now builds, so such a cloud can be opened first (PERF.25).

CivilCraft Built · in the lab 2 – From: site suggestion #935 (Suggestion) docs/0.9-POINTCLOUD-ADDON.md
Performance roadmap — wave 3 49
FixPERF.20 Link to PERF.20Comment on PERF.20 Scale: every text format reader holds the whole file as one JS string (DXF, LandXML, OBJ, DAE, ASCII STL, USDA, the native JSON documents)

Measured: a 1 GB DXF and a 692 MB LandXML die in TextDecoder.decode ("Cannot create a string longer than 0x1fffffe8"); a 358 MB LandXML needs 4.9 GB and 27 s; a 10 MB DXF needs 364 MB (38 bytes of heap per file byte, parsed twice through dxf-model.js:65). Sites: dxf-decode.js:35-49 and dxf.js:68-74, civilcraft.js:2485 and xml.js:27, modelcraft io/obj.js:84, and JSON.parse(await file.text()) for every .modelcraft/.detailcraft/.civilcraft document (modelcraft.js:3210). The caps that exist (CivilCraft 200 MB, ModelCraft 200 MB, OBJ 64 MB) are honest and stay until the readers stream. Change: byte-level tokenizers over Uint8Array fed from Blob.slice with lazily decoded values and Float64Array/Uint32Array output, the way lib/ifc scanStep already works. DXF first (the reader is 1,563 lines, L), then LandXML (M), OBJ and ASCII STL (S each). Target: 100 MB DXF under 1 GB of memory, 1 GB files open with a progress bar instead of an error. PARTLY BUILT in /lab 2026-11-14 and 2026-11-20: one shared parts reader (lib/textin); DXF, LandXML + XML parser, OBJ, ASCII STL, Collada, USD text and project JSON read from parts, byte-identical to the old readers; ws11a: a 954 MB DXF opens in 42 s, a 691 MB LandXML in 16 s (both failed at the 512 MB string limit); the tree of objects is the ceiling (LandXML 13x its size, DXF 16 to 20x). 0.11 (scale-11): CSV points (lib/layout, civilcraft patch), G-code (lib/carve) and GeoJSON (patch) read from parts: 18 M points 27.6 s, 36 M G-code lines 28.8 s, a 1 GB GeoJSON 16.7 s (all refused over 512 MB before); the Set that stopped both point readers at 16,777,216 points is gone; same speed under 512 MB; GeoJSON parts are 2.3x slower than one string, so parts only over about 400 MB. A 197 MB DetailCraft model rea LANDED 2026-11-20 (inbox-11b) scale-11 patch applied to civilcraft/a Discord member (points.js, geojson.js, landxml.js; chunks.js synced); DetailCraft openFile cap 50 to 400 MB. test-readers 488/0, test-writers 22/0, test-civilcraft 417/0. (inbox-11b) BUILT 2026-11-21 (perf-finish-11), lane scale-shell, in /lab (a Discord member) only: lib/textin joins parts under 400 M characters and hands them to JSON.parse, so callers pass parts at any size; the PartCraft and DetailCraft caps are 400 MB. workstation11a, same value: 268 MB GeoJSON from parts 4.5-5.2 s -> 1.9-2.0 s, peak 3.6 -> 2.2 GB; 197 MB DetailCraft project 1.5-1.7 s -> 0.95 s; a 1 GB GeoJSON unchanged by design (past the join limit). textin 70 / 0, test-readers 488 / 0; textin / textout / history copies in step in every app (--check clean). Not met: a 100 MB DXF under 1 GB (the object tree is 16-20x the file, not the reader).

CadCraftModelCraftCivilCraft App codeOur engines Built · in the lab 12 – docs/0.9-sessions/perf-wave3/
FixPERF.21 Link to PERF.21Comment on PERF.21 Scale: ModelCraft, DetailCraft, PartCraft and CivilCraft snapshot the whole document as JSON on every undo step and autosave

Measured: a 400 MB glTF (5 M faces) imports into ModelCraft in 17 s and 2.5 GB, then the FIRST edit calls model.js:2408 snap() (also :2223, :2230, :2272, :2331): 407 MB of JSON, 35.6 s, 9 GB peak, so the tab dies after a successful import. At 500k faces the snapshot is 3.1 s per edit. Same shape in DetailCraft model.js:169-199 (stringify before AND after every change), PartCraft part.js:504-517 and CivilCraft project.js:155. Change: command or diff undo (or per-definition dirty snapshots), meshes kept as typed buffers instead of base64 inside JSON, autosave payloads as Blobs of those buffers (the shell's IndexedDB store already takes Blobs). ModelCraft first. Extends PERF.7 with the 10x and 100x numbers. Built in /lab 2026-11-15 (session history-10; lib/history, one thin adapter per app). Undo by change records: a step holds the chunks one edit changed. DetailCraft grid48x30x10 (20,000 members): undo 62 to 6 ms, 20 steps hold 133 MB before and 0.2 MB now, an edit step 49 to 8.6 ms. CivilCraft survey-500k + 20,000 features: undo 32 to 15 ms, 56.6 MB to 1.1 MB. PartCraft features-750: 3.8 MB to 0.1 MB. ModelCraft was already by deltas (MD.1): at 5 M faces an edit and an undo take 0.1 ms and 0.3 MB; the 36 s / 9 GB figure of the wave-3 report is not the a Discord member build. Tested: 878 + 15 library checks, a Discord member a BUILT 2026-11-21 (perf-finish-11), lane civil, model, scale-shell, in /lab (a Discord member) only: CivilCraft: hot edit callers (grips, profile points, 35 Properties edits, feature replace/delete, point moves) name their chunks; lib/history keeps its id index between hinted calls. 500k points + 20,000 features: grip drags 62-87 -> 0.14-0.20 ms, feature after an undo 66 -> 6 ms, delete 110 -> 32 ms, same records (809 / 0 with every hint checked against the full look, 6 / 0 real page). ModelCraft: 400 MB glTF on quiet workstation11a graft 1 ms, first mesh edit 0 ms, undo 1 ms (wave 3: 36 s / 9 GB); the first autosave copy of such a model is still 12.6 s / 6.6 GB peak, in the worker.

ModelCraftCivilCraftDetailCraftPartCraft App code Built · in the lab 10 – docs/0.9-sessions/perf-wave3/
FixPERF.22 Link to PERF.22Comment on PERF.22 Scale: cc-dwg keeps 35 bytes of heap per file byte, clones the drawing out of the worker, and the writer is super-linear (extends PERF.5, PERF.9, PERF.10)

Measured at 10x (a 76 MB R2004 drawing, 1.4 M entities): readDwg 19.9 s and 2.6 GB after read (one object per entity and per vertex, objects-read.js:608-613 and :1105), the worker reply structuredClone adds 1.06 GB and 14.6 s (read-async.js:67), writeDwg 66 s (33 s from a fresh model), exponent 1.3. A 760 MB drawing would need about 27 GB: it does not fit anywhere. Browser ceiling today about 55 to 110 MB. Change: a struct-of-arrays entity store with lazy per-entity decode from the object map (the map and section locators are small; readDwg(bytes) at read.js:30 becomes openDwg(blob) with byte-range decoding), the worker reply as transferable typed buffers (or decode on the page from the transferred bytes), and a writer that streams sections to a FileSystemWritableFileStream. Reader L, writer M. The four apps carry byte copies of lib/dwg. Partly built (dwg-perf-10 2026-11-14): Writer half and worker hand-off built (see PERF.5, PERF.9): the worker copy is no longer cloned. Reader heap measured at 16.1 B per file byte (heapUsed after a GC, Plans.dwg and the 130k and 1.3 M generated drawings alike; the row's 35 was not reproduced), 15.6 now: one string per owner saves 0.5, the rest is 1.14 M objects and 2.5 M boxed numbers the model shape needs. Log docs/0.10-sessions/dwg-perf-10.md. PARTLY BUILT 2026-11-20, scale-11: measured on a prototype outside the apps (tools/scale-11/proto-table.mjs, lib/dwg/model-pack.js as the table): the reader holds 15.2 to 15.6 B of heap per file byte (not 35); keeping the entity lists as typed arrays: Plans.dwg 128 MB to 49 MB (2.6x), 1.3 M entities 1,150 MB to 346 MB (3.3x), all lists back as objects in 0.43 s per 1.3 M; the proposal (shape, each app's adapter, risk) is in the log under For the owner. A bug that read objects past 256 MiB as empty was fixed in the reader. No model changed.

CadCraftBimCraftModelCraftCivilCraft Our engines Built · in the lab 12 The owner's yes on the typed-array entity table (docs/0.11-sessions/scale-11.md, For the owner) docs/0.9-sessions/perf-wave3/
FixPERF.24 Link to PERF.24Comment on PERF.24 Scale: autosave rewrites the whole document every couple of seconds of editing, in every app (extends PERF.5)

Measured and read: CadCraft autosave writes a full DWG (dwg-autosave.js:39 saveDwg; 4.8 s today, 66 s at 10x), BimCraft the full IFC bytes (bimcraft.js:585 to model.js save), MarkupCraft the whole PDF Blob (markupcraft.js:4715; TakeoffCraft stops at 64 MB, takeoffcraft.js:4313), ModelCraft the JSON (modelcraft.js:3883). On a big file autosave is the longest task the person sees while working. Change: journal autosave, keeping the opened file's bytes or handle plus the edits map (IfcFile already holds exactly that in memory), snapshots taken in a worker from transferred buffers, and a clear cap with a message above a size. Shared piece in the shell's app-autosave.js, one snapshot function per app. Built in /lab 2026-11-15 (session history-10). The shell's autosave has a journal mode: the first copy is the whole document, then only what changed; a failed write loses nothing, a crash between writes leaves the… history-11 2026-11-20: CadCraft and BimCraft built in /lab. CadCraft (dwg-journal.js): the copy is the DWG once, then the objects, blocks, layers and settings that the a Discord member's own undo ops touched, in order, named by their file keys; anything it cannot follow (3D model, layouts list, draw order, a block editor, a version bump with no step) writes a new base. 100,000 objects: next autosave after one edit 9,663,404 bytes / 6,606 ms to 169 bytes / 1 ms. BimCraft (history/ifc-journal.js): the copy is the opened IFC bytes plus the edit map, t BUILT 2026-11-21 (perf-finish-11), lane scale-shell, model, bim, in /lab (a Discord member) only: MarkupCraft: real /lab page with a 10.3 MB 200-sheet PDF, renderer killed mid-edit: base once, then +1,100 bytes a copy, Recover reopens the edit (5 / 5). ModelCraft: an edited mesh is written as its edits (one edit 5.9-24 MB -> 2,048 bytes; 400 MB glTF 305 MB -> 2,200 bytes; recovers 122 / 0). BimCraft: models with pictures use the journal, pictures as files only when they change (next copy 9,718 -> 130 bytes; big pictures now recover; 88 / 0).

CadCraftBimCraftModelCraftMarkupCraftTakeoffCraftCivilCraftDetailCraftPartCraft App shellApp code Built · in the lab 4 – docs/0.9-sessions/perf-wave3/
FixPERF.25 Link to PERF.25Comment on PERF.25 Scale: point clouds pass 2 GB, but the octree merge is single-threaded, LAZ copies the whole file into WASM and E57 is one 512 MB buffer (extends PERF.10)

Large point clouds: tiled by a worker pool, LAZ read chunk by chunk, E57 page by page, every point kept. 0.10 (pointcloud-10): tile pass on up to 4 workers, byte-identical to the serial build; LAZ chunk reader (heap 3 MB, not the file); E57 page reader. pointcloud-11 2026-11-20: a LAZ of 2.10 GiB and 241,100,000 points (made once, registered in testfiles/LARGE-FILES.md, made-up terrain) builds in 268.5 s with one decode thread and no tile workers, 207.3 s with 8 tile workers, 94.9 s with 4 LAZ decode threads (each its own laz-perf, results in file order: byte-identical cloud, tested), the merge of the upper nodes in the worker pool and the build folder cleaned 32 files at a time (2.54 M points a second, peak RSS 6.1 GB, workstation11a). The old whole-file reader cannot read that file ("not enough memory"). An E57 of 600 MB (22.1 M points) builds in 18.8 s, every point kept, 0.95 GB. Not done: a browser tab with a 2 GB file; the files are made-up data and the E57 writer was never opened in another program. Results: docs/results/0.11/pointcloud-11-perf25.md.

CadCraftBimCraftCivilCraft Our engines Built · in the lab 4 – docs/0.9-sessions/perf-wave3/
PlatformPERF.26 Link to PERF.26Comment on PERF.26 Scale: text writers return one string, so exports stop at 512 MB and hold twice the output

DXF (dxf.js:1324, dxf2000.js:437), LandXML (landxml.js:227), OBJ, DAE, USDA (usda-write.js:33), GeoJSON and gcode writers each build one string and return it; a 1,000,000-entity DXF export is near the V8 string limit and the string plus its Blob is twice the output in memory. Change: writers that yield chunks into a WritableStream (createWritable on a file handle when the host offers one, else a Blob built from parts), with the same report object. Pairs with the streaming readers row. Partly built (dwg-perf-10 2026-11-14): lib/textout/chunks.js (TextChunks: parts, Blob, pipe, string only while it fits): equal to lines.join at every size around a part, and 686 MB of text written without a string (peak RSS 1.7 GB). A ready patch for the DXF writer is docs/0.10-sessions/dwg-perf-10-dxf-chunks.patch. Log docs/0.10-sessions/dwg-perf-10.md. PARTLY BUILT 2026-11-20, scale-11: TextChunks gained push(); the LandXML and GeoJSON writers (patch for civilcraft/a Discord member) and the G-code writer (lib/carve, done) write past 512 MB: LandXML 9 M points 706 MB in 11.6 s, peak 3.2 GB (the string version fails: Invalid string length); 6 M points peak 5.7 GB to 2.2 GB; GeoJSON 4.8 M features 661 MB (fails as one string); G-code 40 M moves 767 MB (fails as one string). Same text as before on 62 checks. The DXF patch of 0.10 still applies: posted to cad-11. docs/results/0.11/scale-11-text-ws11a.txt. LANDED 2026-11-20 (inbox-11b) LandXML and GeoJSON chunked writers in civilcraft BUILT 2026-11-21 (perf-finish-11), lane scale-shell, cad, civil, model, in /lab (a Discord member) only: lib/textout TextChunks.output() (a string to 300 M characters, a Blob past that). CadCraft DXF 2000 save at 1 M objects works (was "Invalid string length": 538 M characters in parts, 12.5 s); CivilCraft LandXML and GeoJSON export in chunks (Blob past 300 MB), GeoJSON import from parts; ModelCraft OBJ, Collada, USDA write in parts, byte-identical 33 / 0; carve G-code check 29.8 -> 0.45 s (261 / 0). Copies synced (--check clean).

CadCraftModelCraftCivilCraft App codeOur engines Built · in the lab 4 – docs/0.9-sessions/perf-wave3/
FixPERF.33 Link to PERF.33Comment on PERF.33 CivilCraft: opening a project is one 27 to 41 s main-thread task, and every chosen .json is read and parsed whole twice

f.text() then parse then buildSurface then scene run synchronously in one task (27 to 41 s at 500k; LandXML 69 MB becomes a 1.2 GB element tree). Files over 200 MB are refused by design (civilcraft.js:2320), which is honest, but ifc-native-ui.js:112 reads and JSON.parses every chosen .json whole first to sniff it (6.8 s and 751 MB for a 240 MB file that is then refused), so every project is parsed twice; the LandXML reader cannot take the 692 MB 5 M-point file (over V8's largest string) and fromJSON caps at 2 M points. Change: a 4 KB sniff, the parse and surface build in a worker returning typed arrays by transfer, a streaming LandXML reader (the scale readers row), and progress in the status line. The LAS terrain import is the model to follow: 10.6 M points streamed in 2 MB pieces, thinned to 106k, 2.3 s, no long task (wave 2 stopped at the elevation-unit dialog; Import stays disabled until it is answered). PARTLY BUILT in /lab 2026-11-14: open of the 500k project 37.1 s to 5.0-6.4 s; the pair check no longer parses the project (sniff in pieces), so it is parsed once; integer vertex keys. Not built: Worker, streaming LandXML, progress. PARTLY BUILT in /lab 2026-11-20 (civil-11): a project of 20,000 points or more triangulates its surface in a module Worker (points go as typed arrays, the surface comes back by transfer and is put into p.eg()'s memo): no long task on the page while it runs (real page, 40,000 BUILT 2026-11-21 (perf-finish-11), lane civil, in /lab (a Discord member) only: One Worker reads and parses the project, builds line-code figures, the surface (points or TIN), stats, outline and first-scene contours; streaming LandXML TIN reader landxml-lists.js; each closed contour drawn as its own path (identical pixels). 500k project (23 MB) longest task 2.0-2.5 s -> 0.38-0.55 s, 500k LandXML TIN (69 MB) 30-40 s -> 0.88 s; 110 Node checks equal to the page build, 13 / 0 in the real page; test-civilcraft 417 / 0. Not done: LandXML survey points still use the old reader.

CivilCraft App code Built · in the lab 4 Owner: keep the 2,000,000-point cap, or ask for typed-array points with point undo by change (each point-edit undo step copies the array today) docs/0.9-sessions/perf-wave3/
FixPERF.56 Link to PERF.56Comment on PERF.56 Apps: the shell costs 154 to 257 ms of main thread per start, and three document-wide MutationObservers fire 100+ times a second while drawing

Measured per app: app-phone.js 17 to 56 ms running the phone layout on a desktop viewport; app-boot.js 10 to 73 ms with a body-subtree MutationObserver whose say() rewrites the DOM on every mutation (app-boot.js:82-83) and never settles while the pointer moves (141 to 221 boot-step rewrites in 3 s of drawing); three observers cascade (app-shell.js:477-482, app-phone.js:421 and :483; CadCraft 360 observer callbacks in 3 s of drawing); app-settings.js 15 to 65 ms; app-devices-ui.js 26 ms. Shell bytes: 1.35 MB fetched, about 780 KB never run (app-addons-account.js 59 KB when signed out, calc.js, ai-*.js, app-devices-ui.js, app-propgrid.js). Change: app-phone returns after the matchMedia check on wide pointer-fine screens and attaches its observers only when cc-phone is on; app-boot ignores mutations inside output-like elements and disconnects on settle; app-shell observes dialog additions only (or an attributeFilter without childList on the whole tree); dynamic-import addons-account, calc, ai-*, devices-ui on first use. PARTLY BUILT 2026-11-20 (inbox-11). Shell side done by shell-start-11 (app-start-tip.js 96.1 to 2.1 ms). Workspace side: app-workspace-icons.js watchAppGlyphs schedules its pass only when a record adds an app glyph; app-workspace-popout.js watches only the attributes sync() copies; app-panels.js skips a body class write that leaves the class unchanged; app-dock.js follows only the Arrange class. Measured with tools/perf/she BUILT 2026-11-21 (perf-finish-11), lane scale-shell, in /lab (a Discord member) only: app-popfit.js observer callback does only the cheap name test; the style check and anchor lookup wait for the next frame. Fair A/B on workstation11a (3 runs, alternating): CadCraft 17.8-19.0 -> 3.6-4.7 ms (+0.7-0.9 ms frame work), MarkupCraft 6.4-7.0 -> 1.4-2.3 ms; same menus fitted (browser-popfit 19 / 0); real pop-out and Arrange runs on the VPS (pop-out observers 1-2, dock 1-3 fires in 8 s). The pop-out rerun on workstation11a did not run (signed-out page).

CadCraftBimCraftModelCraftMarkupCraftTakeoffCraftCivilCraftDetailCraftPartCraft App shell Built · in the lab 3 – docs/0.9-sessions/perf-wave3/
FixPERF.57 Link to PERF.57Comment on PERF.57 Apps: start-up work for panels nobody opened: BimCraft massing 191 ms, ModelCraft swatches 182 ms plus 650 ms idle tasks, CivilCraft plants seed, exr table

BimCraft massingOptions() runs 191 ms inside mountProgram (design-ui.js:77); ModelCraft paints a swatch per library material from 128 px procedural textures at start (modelcraft.js:557, :581; 182 ms) and is the only app with long tasks during idle (650 ms); CivilCraft fetches and cleans plants-seed.json (198 KB) at start (landscape-ui.js:117); exr/util.js builds a 65,536-entry half-float table at import (exr/util.js:38-46); three.module.js top level is 65 to 94 ms. Change: compute on first open of the panel or first paint of the palette (IntersectionObserver or the tab event), fetch plants on first Landscape use, build the half-float table lazily. 0.2 to 0.4 s of blocking per start in the 3D apps. MODELCRAFT PART BUILT in /lab 2026-11-14: the library's texture swatches are drawn only once the material list shows (they were all drawn in the first second, while the list is laid out before its panel folds it). Start-up in /lab: 1.37 s blocking in 9 long tasks, quiet in 4.6 s (load 7.8) to 0.49-0.64 s in 3-4 tasks, quiet in 2.3-3.1 s (load 1.6-3.4); drawSwatches gone from the start profile; opening Materials draws them (page test). BimCraft massing was already lazy (bim-core-10). Log docs/0.10-sessions/model-part-10.md, docs/results/0.10/model-part-10.md. PARTLY BUILT in /lab 2026-11-14, CivilCraft only: the plants seed loads on first use or when idle. No browser start-up number was taken. CIVILCRAFT PART MEASURED 2026-11-20 (civil-11): /lab start-up, 5 loads each, alternated, medians: plant seed loaded in the start-up task 9 long tasks / 1,075 ms blocked until read BUILT 2026-11-21 (perf-finish-11), lane bim, model, in /lab (a Discord member) only: BimCraft: massing code 0 ms in start-up (5 loads on workstation11a), the panel builds when asked for (93 ms). ModelCraft: start on workstation11a 1 long task of 54-56 ms, 0 idle long tasks in 12 s. exr: half-float table built on first use, module import 7-14 -> 1.5-2 ms (exr test 172 / 0). CivilCraft plants seed was done in civil-11.

BimCraftModelCraftCivilCraft App code Built · in the lab 2 – docs/0.9-sessions/perf-wave3/
PlatformPERF.59 Link to PERF.59Comment on PERF.59 Apps: no service worker until someone clicks "Save for offline"; every repeat visit is a cold start minus the 7-day HTTP cache

app-offline.js:160 registers /sw.js only on the click, and sw.js:46 installs nothing on its own; the PWA manifest promises more than the page delivers. Every visit refetches the 830 to 940 KB app page (PERF.2, PERF.3) and relies on the HTTP cache for the 300 to 500 module files (which Vary: Referer defeats, see the server rows). Change: register /sw.js on every /use page; cache-first for immutable URLs (?v= and pinned vendor/app folders: the worker already knows the rule, sw.js:33-40), stale-while-revalidate for the page; "Save for offline" stays the explicit full copy. Pairs with the shared-URL row (a shared lib URL is cached once for all apps) and the installed-package row. Built behind PERF_SW_RUNTIME (off): the worker is registered as /sw.js?rt=1 and keeps versioned /assets/ files (?v=, versioned vendor and release folders, hashed catalogs) in cc-runtime:v1, newest 2,500; the first visit hands it what it loaded (MarkupCraft: 170 files kept on the first visit). Rules in the head of sw.js: GET, same origin, /assets/ only, 200 only, never a lab a Discord member build, never a page, so nothing with a CSRF token or account data. Without ?rt=1 the cache is deleted. Repeat-visit time is not measured yet (Playwright's second visit already hits the HTTP cache). (perf-start-10 2026-11-13: docs/0.10-sessions/perf-start-10.md; numbers docs/results/0.10/)

CadCraftBimCraftModelCraftMarkupCraftTakeoffCraftCivilCraftDetailCraftPartCraft App shell Built · in the lab 3 Owner: flip PERF_SW_RUNTIME=1 (or lab) in .env docs/0.9-sessions/perf-wave3/
FixPERF.71 Link to PERF.71Comment on PERF.71 Code: eight app mains are one closure of 2,500 to 5,800 lines each; split by topic

Partly built (code-mains2-10 2026-11-16). Every one of the eight app mains is now split once, each app whole, in /lab only (no live code, rule 62). Main lines before to after: DetailCraft 2,704 to 1,950, CadCraft 3,410 to 2,441, TakeoffCraft 4,808 to 3,820, PartCraft 4,015 to 3,102, MarkupCraft 4,985 to 4,459, CivilCraft 3,209 to 2,378, ModelCraft 4,037 to 3,299, BimCraft 6,317 to 5,874; 31 new modules (mountX(ctx)). Each app has a guard test, tools/<app>-test/browser-main-10.mjs (real dialogs, downloads and imports; fails on any console or page error), run on the ORIGINAL main and on the split one: 27/0, 14/0, 12/0, 13/0, 7/0, 10/0 (TakeoffCraft, PartCraft, MarkupCraft, CivilCraft, ModelCraft, BimCraft) both times, plus DetailCraft 31/0 and CadCraft 15/0 from code-mains-10. The apps' existing browser suites give the same counts before and after, except rows that flip between runs on the original too (listed in the log). The guards found three bugs in tools/perf/main-extract.mjs, all fixed and every earlier module re-audited: a canvas ctx parameter shadowing the mount's ctx, a module-level const read before it was set, a module-level let left bare, plus a duplicate edit. Packed browser editions built and checked per app (rule 56). Still in the closures, reading 15 to 65 variables each: the pointer / touch state machines, act / command switches, the Properties renderers (some), openIfc / openFile, drawOverlay, the BimCraft Issues / Card / DWG / 3D code. Next: a second round on the big closures, with the state moved into one object first. Was: Partly built (code-mains-10 2026-11-16). Two of the eight mains split, each as a whole app, in /lab only. DetailCraft: detailcraft.js 2,704 to 1,950 lines (start() 2,605 to 1,854), eight modules (export-ui, mitre-ui, xf-ui, clipboard-ui, drawings-ui, ifc-import-ui, footing-stair-ui, clash-ui). CadCraft: cadcraft.js 3,410 to 2,441 (init() 3,199 to 2,239), six modules (plot-ui, save-ui, open-ui, text-edit, blocks-ui,… BUILT 2026-11-21 (perf-finish-11), lane r2: bimcraft, cadcraft, civil-detail, model-part, markup-takeoff, in /lab (a Discord member) only: Round two in all eight mains: closure lets into one state object (tools/perf/main-state.mjs), then topic code into mountX(ctx) modules (main-extract.mjs; no statement runs earlier than before). init()/start(): BimCraft 5,654 -> 1,129 lines (56 modules), CadCraft 2,287 -> 1,369 (16), MarkupCraft 4,349 -> 1,118 (31), TakeoffCraft 3,771 -> 848 (27), ModelCraft 3,230 -> 956 (12), PartCraft 2,995 -> 1,260 (12), CivilCraft 2,260 -> 1,381 (8), DetailCraft 1,878 -> 1,408 (7). Each app: a real /lab page guard (fails on any console/page error) and its bin/test-<app>.mjs equal before and after, other page tests equal (rows that already failed fail on the same lines); packed browser editions build and every import resolves (FX.440 fixed the packer). Duplicate lines from multi-statement lines checked and removed in every app.

CadCraftBimCraftModelCraftMarkupCraftTakeoffCraftCivilCraftDetailCraftPartCraft App code Built · in the lab 20 – docs/0.9-sessions/perf-wave3/
FixPERF.72 Link to PERF.72Comment on PERF.72 Code: 4,300 one-line functions that only pass arguments on (forwarder adapters rebuilt per sub-UI, help: () => t() closures)

Partly built (code-mains-11 2026-11-20). tools/perf/forwarders-rewrite.mjs (scope walk, arity kept) rewrote the object-literal forwarders `say: (m) => say(m)` that point at a hoisted function declaration, in the eight app mains, /lab only: CadCraft 13 of 30, BimCraft 44 of 114, ModelCraft 14 of 25, PartCraft 78 of 106, CivilCraft 81 of 175, TakeoffCraft 11 of 30, MarkupCraft 22 of 38, DetailCraft 20 of 35 (283 in all). Kept: wrappers of const/let/import (they exist because the target is not defined yet), functions that declare more parameters than the wrapper passes, functions using this/arguments. Result: all eight browser-main-10 guards unchanged (civil 13/0, model 7/0, bim 10/0, takeoff 27/0, markup 12/0, part 14/0, cad 15/0, detail 31/0, before and after); parse+compile median 4.6 to 4.0 ms civil, 5.0 to 5.2 part, 8.9 to 8.4 bim = noise, bytes -0.1 to -1.1 %. Waits on: the const-bound forwarders (move their targets to function declarations or pass late getters), the other files (commands.js 147 help closures, landscape-ui.js, sub-UIs). Was: Planned (code-mains2-10 2026-11-16): not started. Baseline measured and saved (docs/results/0.10/code-mains2-10-forwarders-before.txt): 4,000+ one-line forwarders; civilcraft.js 190 forwarders, bimcraft.js 152, partcraft.js 117, commands.js 147 help closures. A safe rewrite must keep arity (a wrapper (m) => say(m) is not the same as say when say takes a second argument) and only pass names of hoisted function declarations. Was: tools/perf/quality-forwarders.mjs: 2,299 forwarders plus 2,007 thin wrappers, 278 getters, 401 constant-return functions, 2,683 one-use helpers. Worst: civilcraft.js 182 forwarders (units: () => units(), say: (m) => say(m), row: (...x) => row(...x) rebuilt for four sub-UIs, lines 157-165), bimcraft.js 143, partcraft.js 117, landscape-ui.js 52 (the same {edit, LS, U} trio six times), commands.js 147 help: () => t('…') closures plus seven ask wrappers. This is read and parse cost and noise… BUILT 2026-11-21 (perf-finish-11), lane r2: all app lanes, in /lab (a Discord member) only: Forwarders and help closures: 161 removed in round one (const-to-function.mjs + forwarders-rewrite.mjs), then per app in round two: CadCraft commands.js 150 help closures are language keys (command list identical in en and es-MX); CivilCraft 51 -> 10, DetailCraft 15 -> 3, MarkupCraft 7 -> 4, TakeoffCraft 5 -> 3 (+9 in other files), ModelCraft 10 more gone (1 left), PartCraft 19 more gone (8 left), BimCraft mount-result forwarders gone with the split. The ones left change what their target receives (arity) or point at a name made later in start-up, so removing them would change behaviour. Guards and suites equal.

CadCraftBimCraftCivilCraftDetailCraftPartCraft App code Built · in the lab 3 – docs/0.9-sessions/perf-wave3/
FixPERF.73 Link to PERF.73Comment on PERF.73 Code: copies that drifted and hand copies with no sync tool (six inflate implementations, xlsx.js in four variants, input-mouse.js in eight apps)

Partly built (code-shared-11 2026-11-20). bin/test-sync-copies.mjs: 15 drifted to 4 (150 in step); the 4 left are language files (rule 57). Synced: SuperCad Studio copies (engineer, field, furnish, hull, photo-material, photosketch), modelcraft bcf.js, shell engines (live/read.js etc.), civilcraft bcf, cadcraft cfd/lbm3d, chunks.js x4, m3d view3d.js. New copy groups in tools/copies: wheel-pad (9 places), keynotes, pdf-snap, presence-pump. lib/ifc/step.js stepString/stepList/stepBool: CivilCraft ifc-civil + DetailCraft ifc.js use it, same bytes (1,776 checks, tools/ifc-test/test-step-string.mjs). Not done: crc32 in 14 libs, PartCraft ifc-export and Landscape ifc-landscape S (no lib/ifc copy / written 'no library'), takeoffcraft snap.js vs pdf-snap.js (deliberately different), language-file drift. Was: Partly built (code-shared-10 2026-11-16). bin/test-sync-copies.mjs runs every sync tool with --check (148 tools, hosts read from each tool's usage line): 134 in step, 14 drifted. Synced this session: dwg writer copies (4 apps), ifc (civilcraft, takeoffcraft), terrain tin.js, envir, engineer report, fem frame-model, process thermal, photosketch, scanbim, trusscraft, hull, printstage, office-standard, schematic/plant.js, CadCraft m3d kernel (FX.143 cause: m3d-sync refused the arcs import; now rewritten to ../arcs/arcs.js). New one-source tools: tools/zip (one zlib for lib/exr, 3dm, chip), tools/copies (input-mouse x8, handoff x7, panes, params, framing, bcf, render-tools, carbon-factors, libitem, font, lod, chip hdl: 23 unowned groups), CadCraft's 3 add-on xlsx.js now byte copies of lib/tables/xlsx.js. Suites after: cadcraft 2906/0, civilcraft 417/0, takeoffcraft 1260/0, detailcraft 13111/0, modelcraft 1556/0, partcraft 2917/1 (sketch arcs lang, not from this), bimcraft sweep 836 of 837 (the 1 GB DXF, scale-10). Not done: STEP S/E/L/B into lib/ifc/step.js, pdf-snap vs takeoffcraft snap, crc32 in 14 libs, the 8 SuperCad Studio copies (field, furnish, hull, ph… BUILT 2026-11-21 (perf-finish-11), lane code, in /lab (a Discord member) only: STEP helpers shared in lib/ifc/step.js and the SuperCad / pdf-snap groups added to tools/copies by code-shared-11 (pdf-snap.js and TakeoffCraft snap.js stay two files on purpose: different behaviour). crc32: the 14 lib copies stay (each lib syncs into the apps as a self-contained folder) and tools/zip/test-crc32-copies.mjs (19 / 0) fails if any copy drifts or a new one appears. bin/test-sync-copies.mjs is the guard for the rest.

CadCraftBimCraftModelCraftMarkupCraftTakeoffCraftCivilCraftDetailCraftPartCraft App codeTests and tooling Built · in the lab 4 – docs/0.9-sessions/perf-wave3/
FixPERF.74 Link to PERF.74Comment on PERF.74 Code: shared utilities written hundreds of times: vector math 2,088 implementations, csv cell 431, point-in-polygon 243, esc 198, uid 188, download 163

Partly built (code-shared-11 2026-11-20). lib/geom2d pointInPolygon now also in CadCraft xclip.js and TakeoffCraft geom.js + pickpath.js (hosts cadcraft, takeoffcraft in tools/geom2d/sync.mjs) and CivilCraft parking.js + sections.js. Kept inline on purpose: lasso-core.js (import-free, 5 byte copies) and vpclip.js (no imports). Not done: the lib/ synced copies (envir, landscape, wind), the other clusters, vector math, csv cell, esc, uid, download, shell util.js, shell-mount, ui-util, live-state. Was: Partly built (code-shared-10 2026-11-16). lib/geom2d/geom2d.js pointInPolygon (identical to the 18-copy cluster, test against the old text on a half-unit grid) + tools/geom2d/sync.mjs; CivilCraft's 11 inline copies now call it (civilcraft 417/0, the 14 per-feature suites 0 new failures). Not done: the other 7 copies in that cluster and the 9 other point-in-polygon clusters (each needs its host's geom2d copy), vector math (2,088), csv cell, esc, uid, download, shell util.js, shell-mount, ui-util, live-state. Was: tools/perf/quality-utils.mjs counted 6,943 implementations of 24 utility names (21,260 lines): vector math 2,088 (516 distinct bodies in 1,094 files), area 299, point-in-polygon 243 (identical clusters of 17, 12, 9, 8 and 6), bbox 190, lerp 69, clamp 68; text and bytes: esc 198, uid 188, download/saveBlob 163, csv cell 431, base64 59. The shell exports none of these; lib/units is the one shared table that is used everywhere. Change: lib/geom2d (vec, bbox, area, point-in-polygon, lerp, clamp) and a shell util.js (esc, uid, download, csv, base64) synced into the builds like host.js; mechanical replacement guided by the cluster list, with the quality scripts kept as the check so the count only goes down. Also shell-mount.js (a 48-line block identical in seven apps) and ui-util.js (eight variants of one 45 to 76 line file) become synced shell files, and the Studio Live stateCore plus diff and invert hand-copied in three apps and joinFromPage in six bec… BUILT 2026-11-21 (perf-finish-11), lane r2: util, in /lab (a Discord member) only: Shared files with one canonical copy, synced as byte copies into all eight apps: assets/js/ui-util-core.js (makeEl reproducing each app's own el() rules, fillDl, bytes, num, fmt, frame), assets/js/util.js (esc, escXml, csvCell, uid, download), assets/js/shell-mount-core.js (the mount block seven apps had copied), lib/geom2d geom2d.js (pointInRing, signedArea, ringArea) + geom-vec.js (2D/3D vector helpers, affineMul); tools/shell/sync.mjs and tools/geom2d/sync.mjs cover them. 295 helper copies in 135 files replaced only where the syntax tree equals the shared function (tools/perf/util-copies.mjs, scope-checked): test-util-copies 315 / 0 (2,000 seeded inputs a copy, Object.is), browser-ui-util-core 158 same / 0 different, test-shell-mount-core 42 / 0, geom2d 26 / 0; every app's page guard and suite equal to its baseline. Left on purpose: copies that are not the same function (uid schemes stored in files, download helpers that clean names, esc variants, TakeoffCraft csvCell), title-svg.js ("No imports"), ModelCraft io.js (the m3d kernel copy).

CadCraftBimCraftModelCraftMarkupCraftTakeoffCraftCivilCraftDetailCraftPartCraft App codeApp shell Built · in the lab 6 – docs/0.9-sessions/perf-wave3/
FixPERF.75 Link to PERF.75Comment on PERF.75 Code: deep clones by JSON round trip (205 sites, some inside merge loops) and 24 timers polling faster than once a second

Partly built (code-shared-11 2026-11-20). The 33 ms presence timers (cadcraft live.js, markupcraft live-ui.js) are now presence-pump.js: a push soon after a pointer, wheel, touch or key event or a view invalidate (at most 30 a second), plus a 250 ms safety net; idle 30 asks a second to about 4 (tools/live-apps-test/test-presence-pump.mjs 16/0). Markup page check: browser-mount live strip section 31/0. countall-ui.js 20 ms worker poll is a waiting queue. JSON clones stay (measured in 0.10: not faster). Not done: hazard-ui animation 33 ms, plc-ui 50 ms, CadCraft live UI in a real page. Was: Measured (code-shared-10 2026-11-16), nothing changed. structuredClone is NOT faster than JSON.parse(JSON.stringify()) on plain objects of this shape (Node 24: 50,000 clones of a 40-point symbol, 420-445 ms JSON, 460-493 ms structuredClone), so the 205 sites are not swapped. takeoffcraft learn.js merge loops are bounded by LEARN_LIMITS (100 symbols, 50 sets, 500 assemblies), a clone per merged item: not a cost. The 33 ms presence timers (cadcraft live.js:763, markupcraft live-ui.js:71) still wait for a dirty-flag design. Was: Perf-relevant sloppiness confirmed by reading the top sites. Clones: 205 JSON.parse(JSON.stringify()) plus 112 clone helpers; takeoffcraft/a Discord member/learn.js clones inside merge loops (11 sites), clipboard.js and dwg-keep.js clone document-sized objects: structuredClone or a cloneDoc that copies only what changes. Timers: cadcraft live.js:763 and markupcraft live-ui.js:71 setInterval(push, 33) build presence and JSON.stringify it 30 times a second while idle; hazard-ui and people-ui animate with setInterval 33; countall-ui waits on a worker with a 20 ms poll; plc-ui 50 ms; 250 to 500 ms pollers elsewhere. Change: event-driven pushes with a dirty flag, requestAnimationFrame for animation, promise-based worker replies; a check that lists any setInterval under 1 s. Also: a console.log in bimcraft fem/frame-push.js:155 inside the solver loop, 12 new RegEx… BUILT 2026-11-21 (perf-finish-11), lane code, in /lab (a Discord member) only: Shared Live presence layer (assets/js/live-presence.js, synced to all eight apps): the 33 ms poll for the whole session became pointer/key events plus a 250 ms safety ask; idle work 61 -> 8 calls in 2 s, identical sends (browser-presence-layer 9 / 0, test-presence 53 / 0); a change made by code with no user event reaches others up to 250 ms later. BimCraft hazard and people playback on requestAnimationFrame at the same pace (15 / 0, 19 / 0); ModelCraft PLC timers only while a controller is attached (26 / 0). tools/perf/interval-lint.mjs: every setInterval under 1 s needs a written reason (75 / 75 allowed, a new one fails). JSON clones kept: structuredClone measured 1.5-2x slower than the JSON round trip at every document size (Node and Chromium).

CadCraftBimCraftModelCraftMarkupCraftTakeoffCraftCivilCraftDetailCraftPartCraft App code Built · in the lab 2 – docs/0.9-sessions/perf-wave3/
FixPERF.76 Link to PERF.76Comment on PERF.76 Code: O(n squared) searches in kernel code (ModelCraft mesh ops, the shared m3d model, CivilCraft LandXML) and render functions that rebuild whole panels

Built (code-shared-11 2026-11-20, with model-part-11 for the kernels). CivilCraft LandXML writer: structures x pipes, pipes x structures and profile points x curves became one index each: 6,000 structures 1,359 ms to 96 ms, 20,000 PVIs 93 to 29 ms, file hash identical (tools/civilcraft-test/bench-quadratic-011.mjs). TakeoffCraft clipboard copy of 20,000 items 1,996 ms to 34 ms, 20,000 marks 1,525 to 86 ms, Live reorder op 765 to 7 ms (tools/takeoffcraft-test/bench-quadratic-011.mjs). Render-function rebuilds are a separate row's work. Was: Not started (code-shared-10 2026-11-16): kernel Sets (modelcraft mesh/ops, m3d model, landxml) and render-function rebuilds wait for a next session. Was: Nested-loop searches with includes/some inside N by N loops: modelcraft mesh/ops.js:421 subdivide (also :471, :820, :915), m3d model.js:693, :778, :1637, :1957 (in both ModelCraft and CadCraft's copy), civilcraft landxml.js:298-322. These are the places a 10x model turns into a 100x wait; the 3D track's numbers (ModelCraft push/pull and undo at 500k faces) land here. Change: Sets and Maps keyed by vertex or id, measured before and after with tools/perf/scale-bench.mjs and the apps3d scripts. Render functions that rebuild and re-query the DOM on every call (196 querySelectorAll and 315 addEventListener inside render functions; takeoffcraft.js sheet list on every sheet switch, shell app-workspace.js, supercadcraft.js, cadcraft renderLayers and renderSelTotals): keyed children and incremental updates, measured on the 2D track's 2,000-sheet set. MODELCRAFT AND THE M3D MODEL BUILT in /lab 2026-11-20 (model-part-11), same machine, results identical by hash: slideRails on a 1,001-vertex loop of a 4 M half-edge mesh 27.1 s to 0.09 s (the open half-edges by head built once), healCollinear on a 6,000-vertex polyline 2.53 s to 0.05 s (vertex map kept in step, edge-face map only after a merge), edgeChain on 6,000 edges 37 ms to 18 ms, insetFaces on 22,500 faces 4.4 s to 2.3 s…

CadCraftModelCraftTakeoffCraftCivilCraft App codeOur engines Built · in the lab 4 CivilCraft landxml.js (civil-11's); the render functions that rebuild whole panels (the 2D apps') docs/0.9-sessions/perf-wave3/
FixPERF.78 Link to PERF.78Comment on PERF.78 Code: dead modules and exports, god functions and cyclomatic hotspots beyond the mains

Partly built (code-shared-11 2026-11-20). Re-ran tools/perf/quality-dead-exports.mjs: 17 orphan modules and about 30 dead exports left, every one with a reader outside the import graph (tests, worker entry points, the cheat-sheet and numerics tools, super-engineer under test-super-core), so nothing deleted. Not done: the bundler dry run (no tool), god functions. Was: Partly built (code-shared-10 2026-11-16). Deleted the stale cadcraft addons/windows/lib/cutlist/cutlist.js (nothing imported it; tools/cutlist WINDOW_FILES updated; windows add-on 93/0). Checked and kept: skin-gpu.js (browser-skin-gpu.mjs test), compute/parity.js (bin/test-compute.mjs, the accuracy register), trusscraft layout.js (accuracy register), partcraft eng-data/eng-units (doors, import map names unverified). Not done: the 32 dead exports, the bundler dry run, god functions. Was: Confirmed dead: cadcraft addons/windows/lib/cutlist/cutlist.js (190 lines, a stale copy nothing imports), addons/trusscraft/lib/layout.js in four apps (tests only), modelcraft anim/skin-gpu.js, compute/parity.js twice, partcraft eng-data and eng-units stubs; 32 dead exports (about 54 KB: partcraft worker solvers, the openfoam runner) plus 26 orphan modules (about 141 KB). Name-level dead code across the 5,020 namespace and dynamic imports needs a bundler dry run (one tree-shake pass per app as a report, nothing shipped bundled). Hotspots: 120 functions over 300 lines and 618 with cyclomatic complexity 40 or more: readFamily 234, writeDwg 769 lines at 214 (plus convert 195, buildModelParts 182), vla-host get 207, validateItem 194, buildSite3D 190, dxf entityFrom0 187 and writeDxf 159, pdf-write writeMarkedUp 182, writeCivilIfc 702 lines, model-ui mountModel 1,804 lines, res-ui 1,407, shell app-panels 1,742 and app-settings 1,521. Change: table-driven dispatch for the entity switches, one module per panel section, delete the dead files; each behind the existing tests. BUILT 2026-11-21 (perf-finish-11), lane r2: all app lanes, in /lab (a Discord member) only: Table-driven switches and one module per panel section, worst first per app: CadCraft DXF entity switch a table (readDxf identical on 85 texts), Properties 837 -> 343 lines in 7 modules; BimCraft dwg-compile entity switch a handler table (identical on 410 drawings), model-ui 1,903 -> 434 and res-ui 1,593 -> 404 lines in 10 section modules each; CivilCraft IFC writer 753 -> 166 and 3D builder 333 -> 91 (37/37 + 3/3 IFC, 66/66 scenes identical); DetailCraft Properties one module per section, two type switches tables (175 build() calls identical); MarkupCraft 72-case act switch a table, writeMarkedUp one writer per kind (3/3 PDFs byte-identical); TakeoffCraft estimateSheets one builder per sheet (8/8 workbooks identical); ModelCraft 60-case act switch a table, Info panel nine sections; PartCraft run() two command tables, swmacro switch a map (16 runs byte-identical). Dead-exports report re-run (33 exports, 14 orphans, none safe to delete). Still large: ModelCraft readGltf and openRenderDialog, PartCraft step-exact, BimCraft views-ui and render-ui.

CadCraftBimCraftModelCraftCivilCraftDetailCraftPartCraft App code Built · in the lab 4 – docs/0.9-sessions/perf-wave3/
Interface roadmap — wave 1 26
PlatformUI.4 Link to UI.4Comment on UI.4 Studio: torn-off windows are real windows, placed on the right monitor and remembered, on Windows, macOS and Linux

In CadCraft Studio a window.open becomes a real Tauri window through on_new_window in desktop-shell src-tauri/src/lib.rs (built on about:blank; the engine loads the asked page into the window it is handed). This path has crashed Studio on Windows before (TakeoffCraft pop-up, 0.6 report) and the 0.8.1 hand-off was never tested on a Windows build. This row: the window service (UI.2/UI.3) in Studio = one Tauri window per torn-off piece with the app's icon and a title, placed on the monitor the person dragged to (Tauri monitor list, no Window Management permission prompt), its place remembered with the window ids that survive a restart (MCP-WINDOW-IDS), restored at start without a click (the desktop may do what the browser may not), closed with the main window, and a startup log line per window (PERF.18's log). Test on ws11a (two monitors) and the owner's Mac; tablets stay without pop-ups (the shell's mobile rule). studio-10 2026-11-14: Written in desktop-shell (source only, not built, not run in a window): every torn-off block is a real Studio window (the about:blank hand-off of the 0.6 crash is kept and now has a source test); its place (position, size, screen scale) is kept per app + block title in popup-windows.txt, put back on the next start when a connected screen still shows it (a gone screen leaves it where the system put it), the pop-ups close with their app window, and cadcraftDesktop.popups.restore() lists the block titles that were out, once, for the page to reopen without a click. The place logic is std-only and tested alone (7 tests, rustc --test); the bridge and the source contracts are in node test/bridge.test.mjs (117) and test/handoff.test.mjs (14). Not done: building it, the two-monitor hand test on Windows, macOS and Linux, and the page calling popups.restore. studio-11 2026-11 SEEN 2026-11-20 (studio-checks-11): two real app windows (CadCraft, BimCraft) opened by windows.open on Windows. Nothing was dragged to a second monitor. (studio-checks-11)

CadCraftBimCraftModelCraftMarkupCraftTakeoffCraftCivilCraftDetailCraftPartCraftSuperCad Studio Desktop host Built · in the lab 3 Studio build with it (studio session); check: UI-HAND (two monitors, restart, windows come back). docs/0.9-sessions/interface-wave1/SUMMARY.md
FeatureUI.14 Link to UI.14Comment on UI.14 One icon family everywhere: the CadCraft set in every layout's ribbon, toolbar, toolbox, menu and palette, and the missing tools drawn

Today the set shows only in Duncan's tool rows and the Vector/Sketch palettes; the ribbon, the classic toolbars, the menu styles, the toolbox, the File menu, the pet palette and the status bar still show Bootstrap Icons or the app's own drawings, and about 270 specialist tools (the 2026-11-05 count: BimCraft MEP and families, CivilCraft alignments and water, DetailCraft connections, PartCraft features, MarkupCraft and TakeoffCraft marks) have no drawing in the set at all. Change: (1) the engine's tool() and the input registry's icon lookup ask the set first for EVERY block and the classic toolbars (iconKey → iconNode; Bootstrap only as the last fallback, logged in the lab so the missing list is real); (2) draw the missing tools in sets per app, each set reviewed on the UI.13 sheet, one agent per app with the rules, about 30 icons a day; (3) the eight apps' own toolbar drawings (CadCraft's 1.6 px line icons, BimCraft's, …) retire where the set covers them, kept under Settings › Icons "Each app's own drawings" for people who prefer them; (4) add-ons name icons from the set by key (api.icons) so an add-on's tools match. Measured at the end: zero Bootstrap fallbacks in the eight apps' default toolbars and ribbons in the lab; the number of set icons in the release note. Owner addition the same day (UI.22): the drawings themselves, the inventory and the icon repo are UI.22, the library; this row is wiring that library into every block, layout and app so one family shows everywhere. NOTE 2026-11-20 (inbox-11): the api.icons patch (docs/results/0.11/icons-addons-api-icons.patch) touches a Discord member/addons.js, the one loader copy of eight app sessions, not a shell file: not landed by the shell; the line is now to cad-11 (with PERF.52, same file) in the closing board.

CadCraftBimCraftModelCraftMarkupCraftTakeoffCraftCivilCraftDetailCraftPartCraft App shellApp code Built · in the lab 8 Owner: look at the drawings (UI.22). Measured: 8 apps x 2 layouts, 6 add-on buttons, 6 set drawings, 0 Bootstrap, 0 misses. docs/0.9-sessions/interface-wave1/SUMMARY.md
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.

Top