Mission Control is TroveFill's offline demo and developer console — a dashboard, practice forms, and a tiny verification server that records what a form actually received. Unplug the machine and it runs identically. Here's how to use every part of it.
Starts the loopback server on port 4173, opens the dashboard, and starts TroveFill (building it first if needed). Prerequisites: the .NET 10 SDK pinned by global.json + Node.js. That's the whole setup.
One button stages the synthetic statement on the clipboard — exactly as if you'd pressed Ctrl+A Ctrl+C on the real thing.
Seven forms to choose from — plain, React, legacy table, shadow DOM, iframe. The review panel appears; confirm the fill.
You click the form's own button. Then watch the flight log.
The log entry is parsed from what the verification server truly received on POST /submit — server-side truth, not what the page claims.
Feed FormScaffold a text file of your form's field captions; it builds a fillable copy served right on the console, with a coverage bar: auto-fill · review-only · teach-once.
Snip a practice scan with Win+Shift+S, then Ctrl+Shift+V on any form. Pixels are OCR'd in memory — never written to disk — and any value the checksum math can't vouch for arrives as amber CHECK & TYPE; on the practice scans, that's every field.
The console lists the exact commands that rebuild, retest, and rescore everything from source.
# scaffold your own form from a captions file, then open it on the console dotnet run --project tools/FormScaffold -- my-form-captions.txt
# build + every automated test + corpus scoring — the one-liner for IT
powershell -ExecutionPolicy Bypass -File tools\audit.ps1# the honest end-to-end: real gestures in, every field read back via UIA dotnet run --project tools/Smoke -- "Stop & Reissue" stmt-0001
# serve the forms yourself (loopback only, zero dependencies)
node mock/serve.mjs 4173Every submission a practice form makes lands in mock/echo/submissions.jsonl and
renders in the dashboard's flight log. If TroveFill had ever auto-submitted, it would show here — the log's
silence between your fills is the proof.
node mock/serve.mjs 4174 — any port works; the dashboard follows the one you start.
Something else owns Ctrl+Shift+V. TroveFill fell back — hover the tray icon to see the active combo.
The form window lost foreground. That's the safety guard, not a bug — refocus and press again.
Yes, aggressively: the server binds 127.0.0.1 only, and the app has no networking code at all. Pull the cable and re-run the demo.
The complete workbench — scaffolder, corpus,
scorer, audit tooling and this guide's full text — ships with the source under mock/demo/ and tools/.