Release planning

CadCraft 0.7 impact map

What is left from 0.6 and what comes next: every item that was not finished when 0.6 shipped moved here with its status, plus new requests. 0.6 itself keeps what was built.

ProjectCadCraft
Sheet0.7 impact
Items115
Date2026-10-26
10Fix
88Feature
3Spike
3Platform
2Site ops
9Sanity check
0Decision
≈ 0days in the planned and moved items
  • Planned 0 0.6 part 1 or part 2 list
  • Built 115 built and working in /lab (the dev builds); ships with 0.6
  • Partly built 0 part of it is built in /lab; the rest waits (see "Waits on")
  • Promised 0 the live site already says 0.6
  • Moved 0 moved from the 0.5 wishlist
  • Found 0 bug found after 0.5 shipped; 0.5.1 or 0.6
  • Candidate 0 recommended for 0.6 in a spike or session log; owner to choose
  • Community please test 0 built and in /use; a Discord post gives the steps and the expected result and asks people to try it on their own devices, files or know-how
  • Decision Time 0 a decision, check, file, key, flag or go only you can give; folds into the list once answered

Sheet 1 · impact areas

Where 0.7 lands

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

Impact areaFixFeatureSpikePlatformSite opsSanity checkDecisionAll
Apps
CadCraft 4 38 – 2 – 4 – 48
BimCraft 3 34 1 2 – 6 – 46
ModelCraft – 21 3 2 – 3 – 29
MarkupCraft – 16 – 2 – 2 – 20
TakeoffCraft 1 15 – 2 – 2 – 20
CivilCraft – 34 – 2 – 3 – 39
DetailCraft – 16 – 2 – 2 – 20
PartCraft – 23 2 2 – 4 – 31
Studio 2 8 – 1 1 – – 12
SuperCad Studio – – – – – – – 0
Layers
Site and services – 4 – – – – – 4
Desktop host – – – – – – – 0
App shell 1 13 – 2 – – – 16
App code 2 28 – – – – – 30
Our engines – 4 – – – – – 4
Vendor engines – 2 – – – – – 2
Drawing surface 3 4 – – – – – 7
Help and words – 3 – – – 1 – 4
Tests and tooling – – – 1 – 3 – 4

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 Oct 26, 2026 10:50 pm.

ItemWhatAppsLayersStatusDaysWaits onIssues
One lineup (consolidation) 12
FeatureLC.3 Link to LC.3 Registering scans

Covers ReCap. Several scans placed by targets or point pairs, refined by ICP with the error shown, saved as one project, exported as E57 or LAS. Suggestions 2026-10-22: Asked on /suggest (#857, Oct 20): a reality-capture tool for scans (with a mechanical CAD app the person knows better than the usual one: PartCraft, D7.61). Owner 2026-10-22: planned for 0.7 (suggestion #857, Inventor Pro and ReCap).

CadCraftBimCraft Our enginesApp code Built 4 PF.1, RS.7 From: owner (Owner) 0.6-PART3 LC.3
Owner requests (Oct 22) 1
FeatureUNITS Link to UNITS Units of measure in every app: many more units, each on or off in Settings, starred default

Owner, 2026-10-22: many more units in every app (CivilCraft will use them most), and a Settings section where each unit is turned on or off for the dropdown lists, with a star for the default. One shared table, lib/units/ (canonical, copied byte for byte into each app by a sync script, like lib/shapes), in place of the five separate lists in cadcraft, civilcraft, markupcraft, modelcraft and takeoffcraft units.js (bimcraft, detailcraft and partcraft have none). Exact factors; the international foot and the US survey foot stay two different units. - Length: nm, µm, mm, cm, dm, m, dam, hm, km; mil (thou), in, ft, ft-in, US survey ft, yd, rod, link, chain, furlong, mile, US survey mile, nautical mile, fathom; point and pica for sheets. - Area: mm², cm², m², are, hectare, km²; in², ft², yd², square (100 ft², roofing), rood, acre, sq mi. - Volume: mm³, cm³, mL, L, m³; in³, ft³, yd³ (CY), US gallon, imperial gallon, board foot, acre-foot. - Angle and slope: degrees, deg-min-sec, gons (grads), radians; percent, H:V, rise:run. Settings › General › Units (the shell's, so every app gets it): one list per kind; each unit has an on/off switch and a star. Every unit dropdown shows only the units turned on, and the starred one is the default for new drawings, measures and items. The settings never change a file: a drawing or project keeps its own unit (DWG $INSUNITS, a CivilCraft project's ft / m / US survey ft), and a unit the file uses shows in its dropdown even when turned off. Typed values take any unit's mark (3 ac, 2.5 mi, 400 nm, 12'6"). Build on bimcraft PR #4 (yisraelk, closes GH.3): its toolbar selector and model-units.js (six units, getDisplayUnits/setDisplayUnits, localStorage bimcraft.model.units) become BimCraft's use of the shared table and Settings list; keep the work and credit, carry the saved choice over. Words in en, es-MX and id. Tests: each conversion against its legal definition, parse ↔ format round trips, the copies byte-identical.

CadCraftBimCraftModelCraftMarkupCraftTakeoffCraftCivilCraftDetailCraftPartCraftStudio App shellApp codeOur enginesHelp and words Built 6 bimcraft PR #4 merged and brought in first From: owner (Owner) Owner in a Claude session, 2026-10-22
Hardware specs (Track HW) 1
FeatureHW.2 Link to HW.2 Hardware specs from the other six apps

The six apps without the compute probe get it (or a light probe) and send the same report under the same switch. Plan docs/0.7-PART9.md; log docs/0.7-sessions/workspace-layouts.md. Built 2026-10-24 (closing part 2): the shell loads assets/js/app-hardware.js for the six dev builds (manifest "hardware"); light probe lib/compute/probe-light.js (WebGPU adapter + limits, no device, no WebGL) + the same report.js and switch; tests tools/compute-test/light-probe.mjs, browser-share.mjs.

CadCraftMarkupCraftTakeoffCraftCivilCraftDetailCraftPartCraft App shellOur engines Built 0.5 – From: owner (Owner) owner 2026-10-24
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.