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
Performance roadmap — wave 3 49
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.23 Link to PERF.23Comment on PERF.23 Scale: cc-ifc copies the file for the worker and keeps every mesh in memory; save is O(lines) (extends PERF.8, PERF.10)

Measured: the index scans 1.9 GB in 15.9 s and 3.3 GB in Node (linear, typed arrays, lazy per-line parse: the healthy template for the other readers). But open-async.js:33 data.slice() doubles the bytes on the page (ceiling about 1 GB in a tab), open plus geometry plus save holds 12.8 times the file (2.57 GB at 200 MB; in the browser the heap grows about 1 GB per 100 MB of IFC: 210 MB peaked at 1.99 GB, 1 GB would need 10 GB), and save() walks every line with three chunks each (model.js:232-256, 8.8 s at 115 MB). Change: transfer the caller's buffer or let the worker read from the Blob; stream meshes to GPU buffers with an LRU instead of keeping all triangles in JS; save by coalesced byte ranges into a writable stream. Pairs with the BimCraft geometry-off-the-page-thread row (PERF.8). PARTLY BUILT 2026-11-14 (bim-core-10). Built: no copy of the file for the worker when the page just read it (openIfcAsync transfer: true, opening a file from disk), meshes of an element no longer kept in the engine after the viewer copied them, typed batch arrays. Not built: streaming meshes to GPU buffers with an LRU, and the save by byte ranges into a writable stream (save still walks every line). No 115 / 201 MB numbers yet. BUILT 2026-11-21 (perf-finish-11), lane bim, in /lab (a Discord member) only: IfcFile.saveParts / saveTo save by coalesced byte ranges, byte-identical (160 / 0, 108 / 0 on workstation11a); save 115 MB 1,295 -> 87 ms, 201 MB 1,761 -> 232 ms. Streaming meshes to GPU buffers with an LRU (in the description, not the waits) is not built.

BimCraftDetailCraft Our engines Built · in the lab 4 – 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.36 Link to PERF.36Comment on PERF.36 DetailCraft: every edit recomputes everything: autopilot, a quadratic clash check, a full scene of 1,925 draw calls, two JSON snapshots, linear model scans

Measured in /use 0.8.1 and in Node (tools/perf/apps3d-detailcraft.mjs, apps3d-detail-node.mjs; 2,820-member grid24x12x5 and the new 10x grid48x30x10 with 28,500 members and 100x grid60x60x40 with 285,600 members): refresh() (detailcraft.js:354) after any change runs build 151 ms, markParts 261 ms, autopilot.propose 899 ms (18 times more for 6.2 times the members), clashCheck 10.2 s (quadratic), and rebuilds the whole three.js scene with a Mesh plus an EdgesGeometry per part (1,925 draw calls for 948 parts); Model.change stringifies the state twice (model.js:165/170; 20 MB at 10x, 197 MB at 100x) and undo re-parses all of it; Tx.addHole and addConnection find by find/some (model.js:349, :376), so pasting the 10x model took 2.6 s and building the 100x file 716 s. Change: incremental build by id, patch-based undo (the whole-document snapshot row), an instanced or merged scene, id maps in the model API, clash check through a g PARTLY BUILT 2026-11-15 (detail-10). Built: the quadratic clash check by a grid (2,820 members: 10,798 ms -> PARTLY BUILT 2026-11-20 (detail-11). Built: build(state,{cache,dirty}) keeps connection results, member parts, plate parts and footing bars by version, the model's dirtySince() names the changed chunks; markParts keeps each part's form; Tx lookups by id and hinted addHole/addCut (undo was already patch-based, lib/history). Same answer as 0.10 (test-perf-11.mjs, whole JSON, 33 checks). workstation11a, 28,500 members (uncapped), median of 5 edits, 0.10 -> lab: change+build+marks 1,180 -> 738 ms (marks 794 -> 341 ms, build 382 -> 392 ms: unchanged); 2,000 addHole 143 -> 12 ms; 2,000 addConnection 234 -> 12 ms; clash 8.4 s -> 8.9 s (still the biggest cost). NOT built: build()'s remaining O(n) passes (about 390 ms at 28,500), the clash check's cost at 28,500, the scene per changed part, a real-GPU run. readModel keeps 20,000 members: a 28,500 file opens as 20,000 (product limit, owner). In /lab (a Discord member) only, not released; not tried by a person. BUILT 2026-11-21 (perf-finish-11), lane detail, in /lab (a Discord member) only: Clash check groups parts by connection once (was 29,640 x 58,140 scans), number-keyed grid, sample points once per part; build keys parts by the connection results that drilled them and stops copying holes; the 3D scene updates only the replaced parts (updateParts, whole rebuild as fallback) and shares geometry between parts of the same shape. workstation11a, 28,500 members: clash check 7,261 -> 309 ms (no clashes), 9,523 -> 4,088 ms (3,027 clashes), identical to 0.10 at 0/1/5 mm and with a phase filter; one edit 1,112 -> 506 ms (build 352 -> 191); RTX 5070, 20,000 members: edit to next frame 573 -> 401 ms, scene and picture identical to a rebuild (16 / 0); test-detailcraft 13,111 / 0. Left: build is still one pass per edit (~190 ms); constructability ~400 ms per edit is outside this row; the app opens at most 20,000 members.

DetailCraft App code Built · in the lab 6 – docs/0.9-sessions/perf-wave3/
FixPERF.51 Link to PERF.51Comment on PERF.51 Apps: 56 to 69 % of the JavaScript fetched at start never runs; dynamic import boundaries per command, workspace and file format (extends PERF.4)

Planned (code-mains2-10 2026-11-16): not started, nothing measured (no tools/perf/startup run: nothing changed to measure). The mains are now split into modules, so each boundary has a module to put the import() at. Was: Measured with V8 precise coverage on the current releases (tools/perf/addons-coverage.mjs): 6.4 MB (CadCraft) to 10.2 MB (BimCraft) of decoded JS per start, 363 to 492 modules, and after 10 s of idle plus a first command only 31 to 44 % of those bytes have executed (CadCraft 33 %, PartCraft 35 %, DetailCraft 44 %); interaction adds 1 to 2 %. Every file of the entry's static import closure is fetched (284/284 in CadCraft, 432/432 BimCraft). Per app 23 to 33 modules ran under 15 %: 0.3 to 1.1 MB each app, for example the whole DWG/DXF save path in CadCraft (dxf.js 95 KB at 8 %, dwg/write.js 58 KB at 8 %, dxf2000.js, lisp/*), ModelCraft io.js 106 KB at 11 %, PartCraft ws-illustrate 96 KB, sketchview 79 KB, ws-script 66 KB, BimCraft res-ui 107 KB, CivilCraft eg-ui 47 KB and the river/rail/water UIs. modulepreload (PERF.4) hides latency but does not cut bytes. Change: import() boundaries at the command, workspace and file-format level (the command registry already knows each command's module, input-<slug>.js); start with the entry, the view, the model and the toolbar; keep modulepreload for what stays static. Target: 1.5 to 3 MB less to download, parse and compile before the first drawing.

CadCraftBimCraftModelCraftMarkupCraftTakeoffCraftCivilCraftDetailCraftPartCraft App code Planned 10 – docs/0.9-sessions/perf-wave3/
FixPERF.52 Link to PERF.52Comment on PERF.52 Apps: the add-on loader is serial and imports every add-on's help at activation: 13 add-ons on = 235 requests, 3.0 MB, 2.5 s of steps

addons.js (the shell copy synced into every build) awaits each bundled addon.json in turn (:390-396; 13 in CadCraft, default-off ones too), activates one after another (:381) and imports each add-on's help module at activation (:572-589; Electrical's 58 KB every start). Measured with 13 add-ons on (tools/perf/addons-load.mjs): 235 requests, 3.0 MB, 2,552 ms of serial steps, longest step 382 ms; in parallel the same work is about 0.4 s. Baseline CadCraft with nothing on: 13 serial addon.json round trips, about 0.9 s on a real line. Change: put every bundled manifest into addons/index.json at release time (one request) or Promise.all the discovery, import all entries in parallel and activate() in index order, import help lazily from api.help on F1. LANDED 2026-11-20 (bim-inbox-11) the loader with both patches (md5 1157f789) is in bimcraft/a Discord member/addons.js and in the canonical public_html/assets/js/addons.js. No page loads the canonical file (app-addons.js imports the build's own addons.js; released 0.10 builds carry their own copy), so /use visitors get nothing new. tools/addons-test/browser-loader.mjs --apps bimcraft 18/0 before and after. The other six apps still carry md5 1ceea119 until their sessions are given the copy. (bim-inbox-11)

CadCraftBimCraftModelCraftMarkupCraftTakeoffCraftCivilCraftDetailCraftPartCraft App shell Planned 3 Copy into the other six apps (sync --check fails until then); a a Discord member-build load time. docs/0.9-sessions/perf-wave3/
FixPERF.55 Link to PERF.55Comment on PERF.55 Apps: 84 to 95 % of the language keys shipped on an app page are never read; split the catalog by namespace (extends PERF.2)

Instrumented t() on the current releases: CadCraft ships 8,818 keys / 529 KB in #cc-lang, 442 are read by the end of idle and 1,024 after a first command; 70 namespaces (198 KB) are never touched in the first minute (frame 32 KB, m3d 29 KB …); BimCraft 117 namespaces / 300 KB untouched; PartCraft's script namespace 1,140 keys / 73 KB with 13 read; the shell's 1,515 keys / 82 KB with about 300 read in every app. Parsing is cheap (5 to 11 ms); the bytes are the cost, 400 to 500 KB of every page view. Change: split the catalog by namespace at build time (tools/lang), inline shell plus the entry's namespaces, load a namespace on the first t() miss or together with the module that owns it (the dynamic-import row gives the boundary); Lang::merged() key prefix is the split key.

CadCraftBimCraftModelCraftMarkupCraftTakeoffCraftCivilCraftDetailCraftPartCraft Help and wordsApp shell Planned 3 – 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.60 Link to PERF.60Comment on PERF.60 Apps: the help index is one 1.9 MB module imported on F1 (52 locale copies = most of the 103 MB offline help; extends PERF.15)

CadCraft help/help.js is 1.9 MB (BimCraft 1.7 MB), parsed whole on the first F1; the 52 compiled locale copies at 2.1 to 2.2 MB each are most of the 103 MB help folder that "Save for offline" downloads. Change: compile help as an index (titles, search terms) plus one chunk per topic group, load a topic on open; offline saves the index for every language and topics for the chosen one. bin/build-help.php, help-panel.js.

CadCraftBimCraftModelCraftMarkupCraftTakeoffCraftCivilCraftDetailCraftPartCraft Help and words Planned 3 – 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.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/
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