Historical task source. The Eve task board holds current task state.
TODOS/phase-180.md (the Remote Creative Control Plane) is a synchronized
checklist. scripts/verify-phase-180-completion.mjs holds it against
docs/domains/bellona/extras/remote-control/implementation-tracker.md and
checklist-completeness-audit.md: every unchecked item must carry its
_Blocked:_ paragraph, its text must be the canonical text the tracker row
starts with, and the counts in the audit must match. So every one of its 23 open
items is, by its own law, blocked with a stated reason, and the Eve Task Board
parks the file whole.
Do not reword, tag or un-box an item of that file on its own. The task-board pass of 18 September 2026 did, and the verifier went from 0 to 40 sync failures; the file was restored byte for byte. A change to it is made in the checklist, the tracker and the audit together, and the verifier is run.
That pass did find one thing worth keeping. Nine of the open items are the
Windows host (stage 36), blocked because "neither fleet machine runs Windows".
Under the install-first rule that is a reason to try, not to park: a
GitHub-hosted windows-latest runner can build a Windows binary and run what a
CI session allows. Five of the nine can be attempted that way. The other four
cannot (36.01 needs a code-signing certificate, 36.03 interactive UAC, 36.06 an
installer signing identity, 36.08 a Windows GPU) and stay as they are.
- P180W.1 (for 180.C.36.02) Windows screen capture (DXGI Desktop
Duplication), window focus (UIAutomation) and input injection (SendInput)
at parity with the macOS primitives, in a new
apps/bellona/remote-host/windows. Verify: a workflow onwindows-latestruns unit tests that drive the focus and input paths against a launched test window and get a frame of the expected dimensions from the capture path; record the workflow file and the run URL. Pixel parity with the Mac capture on a real interactive workstation is the residue and is not claimed. - P180W.2 (for 180.C.36.04) Chrome, Chromium and Edge launch over CDP
with a managed profile and policy-isolated browser paths. Verify: on
windows-latest(Edge and Chrome are preinstalled) a test launches the browser with a fresh managed profile, connects over CDP, opens a fixture page and reads its title. - P180W.3 (for 180.C.36.05) Blender and Unreal install discovery,
version detection and plugin-installation paths. Verify: a test
resolves the install path, the version and the plugin target directory
from fixture registry entries and
Program Fileslayouts for two Blender and two Unreal versions; checking real installs is the residue. - P180W.4 (for 180.C.36.07) A Windows diagnostic bundle with the content
and redaction policy of the macOS bundle. Verify: on
windows-latesta test generates the bundle and asserts the same sections and the same redacted fields as the macOS bundle's schema test. - P180W.5 (for 180.C.36.09) Cross-platform capability parity.
Verify: a test compares the capability manifest emitted on
windows-latestwith the macOS manifest fixture and fails on any divergence in a shared command namespace. - P180W.6 Carry the results into phase 180 by its own procedure. For
each of the five items: if the attempt satisfies the checklist item, check
it and move its tracker row to
Completewith owner, changed files, verification and evidence; if it does not, rewrite the item's_Blocked:_paragraph and the tracker row's blocker to say what the runner proved and what a real workstation still has to. In the same change, correct the_Blocked:_paragraph of 180.C.26.06, which still says no macOS toolchain is available although 26.01 and 26.02 were closed on the real Mac: the one thing missing is the Apple Developer ID certificate. Update the counts inchecklist-completeness-audit.md. Verify:node scripts/verify-phase-180-completion.mjsreports no checklist, tracker or audit sync failure, and the task board's registry row for phase 180 carries the new open count.