Release planning

CadCraft 0.9 impact map

Every fix and feature lined up for 0.9, and what each one touches: which apps, and which layers of the stack.

ProjectCadCraft
Sheet0.9 impact
Items273
Date2026-11-09
115Fix
147Feature
4Spike
0Platform
0Site ops
0Sanity check
7Decision
≈ 0days in the written 0.9 plans
  • Planned 0 on the plan for the release it is filed under
  • Built 271 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 1 part of it is built in /lab; the rest waits (see "Waits on")
  • Promised 0 the live site already says it is coming
  • Moved 0 moved here from an earlier release or wishlist
  • Found 0 bug found after a release shipped; fixed in a point release or the next one
  • Candidate 0 recommended 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

Built means built and working in the lab. Live means the public can use it, and is the last gate: 270 Built · Live, 1 Built · in the lab.

Sheet 1 · impact areas

Where 0.9 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 38 36 – – – – 2 76
BimCraft 27 53 2 – – – – 82
ModelCraft 19 45 2 – – – 2 68
MarkupCraft 16 11 – – – – – 27
TakeoffCraft 18 7 – – – – – 25
CivilCraft 14 32 – – – – – 46
DetailCraft 13 13 – – – – – 26
PartCraft 18 27 1 – – – – 46
Studio 2 5 1 – – – – 8
SuperCad Studio 22 17 – – – – – 39
Layers
Site and services 7 11 – – – – 5 23
Desktop host 1 1 1 – – – – 3
App shell 2 1 – – – – – 3
App code 10 28 3 – – – 3 44
Our engines – 12 1 – – – 1 14
Vendor engines – – – – – – – 0
Drawing surface – – – – – – – 0
Help and words 1 2 – – – – 1 4
Tests and tooling – – – – – – – 0

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

ItemWhatAppsLayersStatusDaysWaits onIssues
Decision Time 5
DecisionEG.24 Link to EG.24Comment on EG.24 Students and classrooms: free student mode and classroom licences?

Should students get a free mode, and schools classroom licences (pricing, how a school is verified, what a student file may be used for)? Owner's review list 2026-10-27 (duplicates removed). Plan docs/0.8-PART5.md.

– Site and services Built · Live – owner From: owner (Owner) Owner, 2026-10-27 (engineering gaps list, add to 0.8)
Platforms and stores 2
FeatureRL.1 Link to RL.1Comment on RL.1 /download: "Where we release" with current and planned release streams

A tabbed section on /download (#release-streams): Current release streams (this page, the browser at /use, updates inside Studio, GitHub releases) built from Downloads, so a channel shows only with real files; Upcoming and planned streams (Microsoft Store, winget, the signed Windows package, npm/npx, Apple App Store, Homebrew, Google Play, Flathub), no dates. Source: Catalog::releaseStreams() + RELEASE_STREAMS_PLANNED; component core/components/release-streams.inc. TestFlight is not a release stream (owner). Tests: bin/test-product.php.

Studio Site and services Built · Live – – From: owner (Owner) owner 2026-11-01
FixRL.2 Link to RL.2Comment on RL.2 /download notices brought up to date for 0.8

The Windows notice and the requirements table no longer say automatic updates are off: the Windows installer, .deb and AppImage check for updates (from the release's updates.json). The WebView2 notice says fixes arrive with each Studio version. The Spanish and Indonesian notices became one: every app offers the machine-made draft languages (count read from the CadCraft build), getting-started help only. Mac and Android still say updates are off (not in the feed).

Studio Site and services Built · Live – – From: owner (Owner) owner 2026-11-01
Fixes 104
FixFX.8 Link to FX.8Comment on FX.8 Studio Live invite links opened to everyone (LIVE_PUBLIC on)

The invite link (Studio Live from anywhere, through the relay at wss://getcadcraft.com/live/relay) was built and tested since 0.5 but held behind .env LIVE_PUBLIC=0, so /studio, the pricing/FAQ copy and the apps' help said "not open yet". Owner said do it now: LIVE_PUBLIC=1. The site copy follows the switch by itself (/studio Live row, Invite link card, FAQ). a Discord member help for the eight apps (work-live) and MarkupCraft's not-built-yet list updated and compiled. Rules unchanged: the host needs a Team Cloud Plan seat, guests join free, 5 open rooms per host. Checked: relay test 26/26, paid-live gate 10/10, live-rooms 98 of 99 (the one failure, 'no Join in the browser while no public build takes live sessions', was failing before the switch and looks stale because 0.8.1 builds accept live). NOT checked: an invite link run end to end between two real Studios on different networks; the frozen 0.8.1 in-app help and Tutorials pages still say invite links are not open yet until the next release.

– Site and servicesDesktop host Built · Live – – Owner, 2026-11-03
FixFX.14 Link to FX.14Comment on FX.14 Student Program: applications stay out of the inbox; every program email shows its Brevo status

When the verify step was added, StudentProgram::apply still created a normal Contact message, so each application landed in /admin/messages, mailed staff and sent an acknowledgement next to the verify email. Now the form's words are kept as an archived message (Contact::submit ctx quiet), with no staff note and no acknowledgement. /admin/students has a Last email column and a notice for verify emails that did not get through; /admin/student has an Emails section (status, opened, clicked, the refusal reason), from email_log. The resend message says the email was handed to Brevo, not that it was sent. Found through a school (itcgalilei.edu.it) whose mail server refuses our mail with 550 5.7.1; that applicant cannot verify at that address. Tested with bin/test-student-program.php (91 pass) and by rendering the pages on real rows; no new application has gone through the live form since.

– Site and services Built · Live – – Owner, 2026-11-03
FixFX.44 Link to FX.44Comment on FX.44 Student Program: tell applicants what to do when the verify email never arrives

Some school mail servers refuse outside mail (seen: itcgalilei.edu.it, 550 5.7.1), so an applicant at such a school waits for a link that never comes and we cannot email them to explain. The notice after applying and a new "No email from us?" item beside the form on /education now say to check spam, then apply again with another address. Since FX.24 another address gets the license on the click, with no approval. The staff alert discussed with this fix was not built: no application waits for approval any more. Tested with bin/test-student-program.php and the live page; no one has yet applied after seeing the new words.

– Site and services Built · Live – – Owner, 2026-11-05
Developer API 8
FeatureAPI.1 Link to API.1Comment on API.1 Developer API: keys for licensed accounts, api.getcadcraft.com/v1, categories

The CadCraft API for people's own systems, on its own host. Licensed accounts make keys on /account/developers: scopes per category, one-workspace limit, expiry, allowed addresses, roll and revoke; the key is shown once. Categories: account, licenses, education, library, storage, projects, meta. Rate limits per key, Idempotency-Key on writes, cursor paging, and a log of each key's calls. Thin wrappers over the same services the website uses, so a key can never do more than its account. Test bin/test-a Discord member-api.php --http.

– Site and services Built · Live – – From: owner (Owner) Owner, 2026-11-03: "the cadcraft api"
FeatureAPI.2 Link to API.2Comment on API.2 Developer area: /developers overview, guides, generated reference, console, changelog

Public docs at /developers, in the footer, sitemap and llms.txt. The reference is generated from the one endpoint catalogue the server routes by, with curl, PHP, Python and Node samples. The console makes real calls with your own key, run on our server so the browser never calls the API; a live key needs a tick before it changes anything.

– Site and services Built · Live – – From: owner (Owner) Owner, 2026-11-03: "the cadcraft api"
FeatureAPI.3 Link to API.3Comment on API.3 API: seats and license counts (Team Cloud Plan + SuperCad Studio)

License counts per workspace; list Team Cloud Plan seats; assign, unassign, or give a seat to an email address (invited with the seat held). SuperCad Studio: list seats and move one under the website's waiting-time rule. Buying or removing seats stays on the website.

– Site and services Built · Live – – From: owner (Owner) Owner, 2026-11-03: "the cadcraft api"
FeatureAPI.4 Link to API.4Comment on API.4 API: cloud storage use and project lists

A workspace's space and use plus the account's own folder; projects, one project with members, and its drawings (names, apps, versions and sizes, never the files).

– Site and services Built · Live – – From: owner (Owner) Owner, 2026-11-03: "the cadcraft api"
FeatureAPI.5 Link to API.5Comment on API.5 Teachers enroll a class: invite, active on the click (API + /account/students)

An active teacher in the Student Program enrolls a list, on /account/students or POST /v1/education/students (the same service): up to 200 a call, 500 invites a day, 300 students unless staff raise it. Each student gets one email; /education-join needs a real click, then the license is active with no staff review, prices locked as at apply. Invites expire after 30 days. List, edit, resend, CSV; a student can say "This isn't for me" and is not invited again. Taking a student off the list: an unanswered invite ends; someone who joined keeps the versions covered until then and new versions stop, and they can answer a new check if they are still a student. Real mail to a student has not been sent yet (tests only log it).

– Site and services Built · Live – – From: owner (Owner) Owner, 2026-11-03: "the cadcraft api"
FeatureAPI.6 Link to API.6Comment on API.6 API: upload library blocks, choose what to add, see where they stand

POST /v1/library/uploads takes a DWG, DXF or library .json (50 MB, 20 an hour, as on the website) and answers with the blocks found; commit the ones to add with a category, license, source and the rights confirmation, or abandon. Public items wait in the same staff review as website uploads; team library items need a seat in force. Also lists the account's items with their versions and review state. Tested over HTTPS with the DXF fixture; a real DWG has not been sent through the API.

– Site and services Built · Live – – From: owner (Owner) Owner, 2026-11-03: "the cadcraft api"
FeatureAPI.7 Link to API.7Comment on API.7 API: a sandbox of your own for cck_test_ keys

Sandbox keys run every call against a practice team, class, SuperCad Studio license and projects in a second database: real writes, but no mail is sent, nothing is charged and uploads never reach the real Library. Each developer's sandbox is apart from everyone else's. Helpers read its mail, play a student or the reviewer, and start over; page /account/developers/sandbox.

– Site and services Built · Live – – From: owner (Owner) Owner, 2026-11-05: "yes v1, build the sandbox next then webhooks"
FeatureAPI.8 Link to API.8Comment on API.8 API: webhooks, so we call your server when something happens

Add an endpoint on /account/developers or with POST /v1/webhooks and hear students join, seats move, SuperCad Studio seats change and library reviews finish. Signed, retried for about 2.7 days, paused with one email when an endpoint keeps failing. Sandbox endpoints hear the sandbox, so you can build against it first. Private addresses and our own server are refused.

– Site and services Built · Live – – From: owner (Owner) Owner, 2026-11-05: "yes v1, build the sandbox next then webhooks"
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.