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
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/
PlatformPERF.53 Link to PERF.53Comment on PERF.53 Apps: 29.6 MB of byte-identical files under different URLs across the eight releases, and every new release re-downloads 98 % unchanged files

Planned (code-mains2-10 2026-11-16): not started. Baseline measured and saved (docs/results/0.10/code-mains2-10-shared-before.txt): 822 distinct contents under 2,548 URLs, 33.2 MB of extra copies. Fixing it changes released-build packaging and the 0.9 folders (rule 60: the owner's), so it needs the owner's word on the approach first. Was: tools/perf/addons-shared.mjs hashed every file of the eight current releases: 665 distinct contents under 2,163 URLs, 29.6 MB extra on the wire for a person who opens more than one app (cabinetcraft add-on in four apps 5.8 MB, dwg/ 3.0 MB, ifc schemas in four apps 2.3 MB, regs in four 2.3 MB, m3d 1.3 MB, crs-db.json 914 KB three times, host.js / addons.js / libitem.js eight times). Across releases: CadCraft 0.8.1 → 0.8.2 kept 2,084 of 2,127 files byte-identical (158 MB) and every one is re-downloaded under the new version URL; the same for every app and every "Save for offline" re-save (PERF.15). Vendor libraries are fine (one URL each, pinCurrent works). Change: a shared /assets/lib/<name>/<content-hash>/ URL for lib/* copies and shared add-ons (release-app.php pins it like vendor paths; the import map aliases ./dwg/x.js to it), or content-hashed file names so an unchanged file keeps its URL across releases. Both shrink the import map, which lists every file because ?v= busting needs an entry per module (499 entries / 48 KB in CadCraft, 772 / 78 KB in BimCraft per page view; AppBuilds.php:391-397).

CadCraftBimCraftModelCraftMarkupCraftTakeoffCraftCivilCraftDetailCraftPartCraft Site and servicesApp shell Planned 8 – docs/0.9-sessions/perf-wave3/
PlatformPERF.58 Link to PERF.58Comment on PERF.58 Apps: an installed add-on package is relinked from blob modules on every start (hvac 334 ms, plant 756 ms) and ships as base64 JSON

addons.js linkPackage turns each verified package into blob: module URLs every start: hvac 0.9.0 (193 files, 1.8 MB; 2.4 MB as base64 JSON) costs 334 ms per start (link 115, import 55, verify 6); plant 756 ms (import 447). The Ed25519 plus sha256 check is cheap (6 to 11 ms for 100 to 193 files); blob modules get no HTTP cache and no V8 code cache, so the cost repeats on every visit and grows with file count. Change: keep the signature check but serve verified packages from the service worker under a stable /addons/pkg/<sha>/<path> scope (or cache the linked texts and import() a persistent URL) so modules get code caching; stop base64 in the package JSON (binary zip, about 34 % smaller). AddonPackages.php, addons.js, sw.js.

CadCraftBimCraftModelCraftMarkupCraftTakeoffCraftCivilCraftDetailCraftPartCraft App shellSite and services Planned 3 – 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/
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
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