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 10:00 pm.

ItemWhatAppsLayersStatusDaysWaits onIssues
Fixes 4
Sanity checkDF.1e Link to DF.1e Won't open on Windows 11 ArtCraft’s

Our 0.4 installer on a clean Windows 11 VM, with and without WebView2. 0.4.1 bundles the runtime for the known case.

Studio Desktop host Planned in DF.1 Owner: Windows 11 VM run From: Discord community (Discord) 0.6-PART2 DF.1
Drafting and app features 14
FeatureMCP-WINDOW-IDS Link to MCP-WINDOW-IDS Studio: window ids that survive a restart

The window id from windows_list is the window's label for this run, so it changes after every restart and an assistant's saved id stops working. Give windows a stable id (for example from the file), or let assistants pick a window by file.

CadCraftStudio Planned – – From: Discord community (Discord) Discord #cadcraft, Oct 19, 2026
Discord, 0.7 batch (Oct 17–21) 31
FixD7.54 Link to D7.54 Studio updater: no nagging, every platform in the feed, clear errors ArtCraft’s

Asked: the updater fails when a release has no asset for this platform; it still nags with updates off; show Open instead of Update (5 mentions about ArtCraft's launcher and SolidCraft, #SolidCraft Oct 17, #technical-development Oct 18, #craft-apps Oct 21). Checked 2026-10-21 — real in ours: (a) the hub sets updateReady whenever the build has a feed, not when a newer version exists, so the dismissed What's new card returns at every start, even with updates off (hub.js); (b) the feed has only windows-x86_64 (build.mjs), so any other platform with a feed gets “target not found”, reported as “network:” (updates.rs); (c) the hub reads r.message from a plain-string result, so every check shows the generic text. Fix all three before UPDATES turns on.

Studio Planned 1 – Discord CSV pasted by the owner 2026-10-21
FixD7.57 Link to D7.57 Studio on Linux: guard against the WebKitGTK black window ArtCraft’s

Asked: black screen on start on Linux after an update (2 mentions, #cadcraft Oct 18, 21; about ArtCraft's app). Checked 2026-10-21: ours has no guard for the known WebKitGTK blank window (NVIDIA, Wayland); nothing sets WEBKIT_DISABLE_DMABUF_RENDERER. Also: the .deb/AppImage are named on the site but neither build.mjs nor a CI workflow builds them — find or add the Linux build. Do: set the variable before Tauri starts when it isn't set, a Linux CI job, and a clean-VM check (WIN-CLEAN-style community test).

Studio Planned 0.5 – Discord CSV pasted by the owner 2026-10-21
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.