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
Items148
Date2026-10-21
6Fix
71Feature
2Spike
7Platform
5Site ops
18Sanity check
39Decision
≈ 21days in the planned and moved items
  • Planned 31 0.6 part 1 or part 2 list
  • Built 1 built and working in /lab (the dev builds); ships with 0.6
  • Partly built 19 part of it is built in /lab; the rest waits (see "Waits on")
  • Promised 2 the live site already says 0.6
  • Moved 1 moved from the 0.5 wishlist
  • Found 0 bug found after 0.5 shipped; 0.5.1 or 0.6
  • Candidate 47 recommended for 0.6 in a spike or session log; owner to choose
  • Community please test 14 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 33 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 37 1 – – 6 14 62
BimCraft – 24 – – – 5 10 39
ModelCraft – 14 1 – – 6 5 26
MarkupCraft – 7 – – – 2 1 10
TakeoffCraft – 5 – – – 3 3 11
CivilCraft – 8 – – – 2 3 13
DetailCraft – 5 – – – 2 2 9
PartCraft – 14 1 – – 8 8 31
Studio 2 12 – 7 1 7 8 37
SuperCadCraft – – – – – – – 0
Layers
Site and services – 9 – 3 2 – 21 35
Desktop host – 4 – 6 – 4 3 17
App shell – 3 – – – 1 1 5
App code – 28 – – – 2 9 39
Our engines – 5 1 – – 1 1 8
Vendor engines – 4 – – – – 2 6
Drawing surface – 5 – – – 1 – 6
Help and words – 4 1 – – 1 2 8
Tests and tooling – 2 1 – – – 3 6

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 21, 2026 9:10 pm.

ItemWhatAppsLayersStatusDaysWaits onIssues
Drafting and app features 14
FeatureMC-DIVIDE Link to MC-DIVIDE ModelCraft: divide a line or arc into equal parts

With an edge or arc selected, typing /n in the value box (the same /3 that spreads Move copies today) splits it into n equal edges, with a vertex at each division. An arc is divided along its curve, by equal angle, not along its chord. A curve made of many segments (a circle's or an arc's edges) is divided by length along the whole curve. Also a Divide… item on the right-click menu that asks for the number, so it works on a tablet with no keyboard. One undo step. Build it on model.js splitEdge. In the m3d kernel, so re-copy to the other apps (docs/3D-SPEC.md). Tests in bin/test-modelcraft.mjs: a line /3, an arc /4 (equal angles), a 24-segment circle /6, undo.

ModelCraft App code Planned 1 – From: Discord community (Discord) Discord, Oct 19, 2026
FeatureMC-CALC Link to MC-CALC ModelCraft: arithmetic in the value box (tape measure, Move, Push/pull)

ModelCraft was left out of DF.3 (0.6 typed arithmetic): its value box reads 2.5 but refuses 2.5/3, 4+7/16 and (2.5)/3. Give it its own copy of the DF.3 parser (cadcraft/dev/lencalc.js rules: + - * / and parentheses over lengths with units, no eval, a refusal that says where) and use it in units.js parseValue for every length, in the tape measure and every other tool. A leading /n, n x, *n and ns keep their meanings (divide copies, array, sides), so /3 is still the copy command and 2.5/3 is a length. Same in the other 3D apps that use the m3d value box. Add ModelCraft to tools/lencalc/sync.mjs. Tests: 2.5/3, 12'6"+3/4", (24'-0")/3, 2*450mm, and /3, 3x, 24s unchanged.

ModelCraft App code Planned 0.5 – From: Discord community (Discord) Discord, Oct 19, 2026
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.