Craft Anything: understand how any software works, and craft your own.
Rust
Document headless project and engine tools (#1014)
Tomáš Doubekc18daa6e601c
diff --git a/docs/ROADMAP.md b/docs/ROADMAP.mdindex 5a8b0809..25f6354b 100644--- a/docs/ROADMAP.md+++ b/docs/ROADMAP.md@@ -230,8 +230,9 @@ only when it's green and a maintainer has fully reviewed it, code as well as worthem here- [ ] Check whether the release workflows still run actions that target Node.js 20. None is namedhere any more: every job calls `storytold/craft-common-actions@main`, so a fix belongs there-- [ ] STATUS.md's "Known limits" still says the project feed, game-engine and Ghidra installs and- launching exist only in the desktop app, which R1.6 ended: update it+- [x] Correct STATUS.md's obsolete GUI-only limit: document the shared project feed, engine+ setup, launch and preview tools, with their consent and lifetime limits — PR #1014+ — claimed: Codex, branch docs/r5.2-headless-status- [x] A spinner on screen no longer makes the window redraw at the display's rate: egui's own asksfor a frame at once every frame, ours at the animation's pace (`widgets::Spinner`, #579)- [ ] Measure #579 on Windows 11 (0.3.0 portable): the app's CPU while idle, while a build runs anddiff --git a/docs/STATUS.md b/docs/STATUS.mdindex 4b2eece9..9eecc8a0 100644--- a/docs/STATUS.md+++ b/docs/STATUS.md@@ -290,6 +290,22 @@ into #794's wgpu error went DX12 → WARP → Vulkan by itself in about 2 s, openext start, and went back to DX12 for another app version. The real #794 failure wasn't reproduced:DX12 and WARP both draw on that machine.+### Headless project and engine tools++Rebuild runs save the project's conversation in the versioned `feed.json`, including runs from+the CLI. `project_show` reads it with `offset`/`limit` paging, and `project_inbox_answer` answers+waiting questions and approvals. These tools are available through the engine, CLI and MCP.++`engines_list` reports external and game-engine readiness; `engines_install` installs Ghidra,+Godot and pinned engines. Unity and Unreal still need their vendor's installer and account:+the tool opens an installer where supported, or reports the download page and requirements.+`project_play` launches a built app or game with consent, `project_preview` serves a built website+on loopback, and `project_open_folder` opens its folder. A preview lasts for the session; use+`wait` to keep a CLI preview serving until cancellation. The desktop app calls these tools too.++Checked against the registered tool implementations and rebuild feed writer; no live install,+launch or preview was run for this documentation correction.+## Known limits- Locks: every mutex but the browser viewer's goes through `platform::sync`. A deadlock on one thread or across@@ -347,8 +363,6 @@ DX12 and WARP both draw on that machine.- Several projects build at once (`[build] parallel`, 2 by default; Settings → Builds); more waittheir turn. Queued builds start on their own as places come free, from MCP too. A build with anAPI key works alone, for now: it shares the app's session, so others wait for it and it for them.-- Some flows exist only in the desktop app: the project feed, game-engine and Ghidra installs,- and launching results (ROADMAP R1.6).- Engine gaps from the audit: Frida session tools are partly simulated; imports outside theargument-count table show only the arguments set in the calling block. See tool-status.md.