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:20 am.

ItemWhatAppsLayersStatusDaysWaits onIssues
Performance roadmap — wave 3 49
FixPERF.45 Link to PERF.45Comment on PERF.45 Website: the test suites' cleanup DELETEs are the most expensive statements on the production server (1.3 s full scans of the biggest table)

Partly built (site-11 2026-11-20). Measured again over the digests since the restart: the smoke test's two DELETEs are 65 ms and 0.56 s (was 4.6 s), email_log DELETE 39 ms x 24, form_throttle 5.8 ms x 82, hardware_reports DELETE WHERE build = 'hwtest' 46 ms x 8 (bin/test-hardware.php:23): about 4 s in all, no longer the top statements. The remaining edits are in test files: Inbox line to tests-11 (add created_at / reported_on bounds that use idx_created / idx_day; split the email_log OR into two statements). Was: Partly built (perf-site-10 2026-11-13). bin/smoke-test.php cleanup limited to the last 6 hours on the created_at index: session_activity DELETE 4,607 ms (full scan, load 27) to about 70 ms; download_events 67 ms to 7 ms; email_log narrowed the same way. The other test files' email_log DELETEs (43 ms each) are unchanged. Was: performance_schema digests over 12 days: DELETE FROM session_activity WHERE query_string LIKE ? (bin/smoke-test.php:51) ran 174 times at 1.30 s each, 225 s in all, 129 M rows examined (a full scan of the biggest table per run; the next most expensive digest on the server is COMMIT at 178 s); DELETE FROM email_log WHERE to_email LIKE ? OR (template = ? AND body_text LIKE ?) 231 runs at 43 ms scanning a mediumtext (test-resources, test-owned, test-reply-drafts, test-bidding, test-a Discord member-api); DELETE FROM download_events WHERE referrer LIKE ? 174 runs; DELETE FROM form_throttle WHERE action LIKE ? OR action LIKE ? 433 runs. These run while visitors browse. Fix: capture MAX(id) when a test starts and delete WHERE id… Verified 2026-11-20 (0.11 close-out): re-ran bin/test-hardware.php (28/0), test-mail (50/0), test-resources (269/0) and test-site-07 (203/0) as www-data; their edited cleanup DELETEs ran and cleaned up. EXPLAIN on the live DB: hardware_reports DELETE uses idx_day, the email_log DELETEs use idx_to and idx_created, smoke-test session_activity and download_events DELETEs use idx_created. No full scan of the biggest table remains.

– Tests and tooling Built · in the lab 1 – docs/0.9-sessions/perf-wave3/
Sanity checkPERF.61 Link to PERF.61Comment on PERF.61 Apps: bundled add-ons that can never load in a release are still shipped and probed at every start

In /use CivilCraft and DetailCraft the regs add-on is refused "api-newer" (the release speaks add-on API 1.3, the add-on needs 1.4), BimCraft energyplus and CivilCraft site-geocode-osm are refused "manifest"; each release ships them (0.9 to 2.3 MB) and fetches their addon.json at every start, and Settings shows greyed entries. Change: bin/release-app.php refuses or drops a bundled add-on whose manifest fails AddonCatalog::checkManifest for the release's API. Also the Library should hide packs a release cannot run (seen in wave 2). LANDED 2026-11-20 (inbox-11b) bin/addon-bundled-check.php lists the bundled add-ons a build's addons/index.json carries that the app's add-on API cannot run (a Discord member and current builds: 0 today; with --api=1.1 it finds 33). (inbox-11b)

BimCraftCivilCraftDetailCraft Tests and tooling Planned 1 Wire it into the release packaging step. docs/0.9-sessions/perf-wave3/
PlatformPERF.68 Link to PERF.68Comment on PERF.68 Server: disk at 75 % with 90 GB reclaimable (a 56 GB Rust build tree, tmp/ build trees, both 0.8 downloads, a lang-overlay cache); logs rotated monthly

Measured: / is 290 of 388 GB. desktop-shell src-tauri target 56 GB (the forks' target moved to W: on 2026-11-08; this one did not; memory rule: never rebuild forks on the VPS), stores/build 18 GB, tmp build trees about 13 GB (editions, public-repos, studio-suite-0.9-a Discord member, devshell, live-apps-www*), downloads 0.8 and 0.8.1 both on disk (2.1 GB each; 0.7 and older moved to the CDN), three byte-identical frozen copies per app (hardlinking would save about 1.3 GB), tmp/cache/lang-overlay 981 MB with no TTL; access.log 345 MB a day uncompressed for a month (2.76 GB now). Noise: mec-broker logs two lines a minute when idle, a Discord member-sandbox-sync logs the same schema drift (team_join_codes.used_at) every 10 minutes, mail-poll logs a PHP array_merge(stdClass) error every 5 minutes (a ContactMail bug). Changes: move or delete the Rust target, clean tmp/ after each release, TTL on lang-overlay, hardlink identical files across frozen versions in bin/release-app.php, publish 0.8 downloads to the CDN like 0.7, weekly (or daily access) logrotate, quiet the idle broker line, fix the sandbox drift and the mail-poll error. About 90 GB back (75 % to about 52 %). closing 2026-11-16: Planned → Owner. Server-wide logrotate and disk settings (KICKOFF § Not a session); no session work.

– Site and servicesTests and tooling Decision Time 1 Owner: /etc/logrotate.d is server-wide; tmp/downloads-replaced (4.7 GB) is the "never deleted" policy and stays. docs/0.9-sessions/perf-wave3/
Sanity checkPERF.70 Link to PERF.70Comment on PERF.70 Server: operations checks: two cron jobs without a lock, status-check's serial probes, no Apache scoreboard, static files gzipped per request

Partly built (site-11 2026-11-20). flock added to bin/upgrade-notify.php tick (cron every minute; two overlapping runs could mail twice; tested: a second run exits in 0.1 s while the lock is held). Audited every bin script a cron file runs: the others have a lock, flock in the cron line (cdn-resize, cdn-short) or run once a day. status-check keeps its 60 s cap. Owner's: the /server-status vhost rule and any cron file. Was: Partly built (perf-site-10 2026-11-13). flock added to bin/mail-poll.php and bin/a Discord member-sandbox-sync.php (tested: a second run exits at once); StatusMonitor::runChecks stops retrying failed probes after 60 s (test-status 36/0). Owner's: the /server-status vhost rule and any cron file. Was: bin/mail-poll.php (IMAP, every 5 min) and bin/a Discord member-sandbox-sync.php (every 10 min) have no flock while every other job has one; status-check runs 7 probes serially with 12 to 40 s timeouts plus 5 s retry sleeps (about 2 min worst case inside a 5-min slot; MeCentral timed out once on 2026-11-07). mod_status is on (Require local) but /server-status is rewritten to the 404 page by the catch-all .htaccess, so there is no scoreboard for bin/admin-perf.php --http or future measuring. Static JS is gzipped on every request: cadcraft.js 198 to 59.5 KB costs 9.0 ms p50 against 0.7 ms for an uncompressed file through the same .htaccess, 147 req/s at c=10 and p99 1,029 ms at c=20 (PERF.16 carries the fix: pre-compressed .br/.gz siblings and an immutable one-year cache). Changes: add the flock, run the probes with curl_multi or cap the total at 60 s, a <Location /server-status> with RewriteEngine Off in this site's vhost. Load floors for the record (c=10, keep-alive, zero failures): health 775 req/s, catalog 303, /status 189, / 80, /apps/cadcraft 58, /use/cadcraft 17.4 req/s at p50 586 ms (its 830 KB page is the throughput ceiling: PERF.2, PERF.3).

– Site and servicesTests and tooling Built · in the lab 1 Owner: the /server-status vhost block and the cron lines in the log (files under /etc/cron.d) 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/
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