BitCadence interface review

Reviewed November 13, 2026. Lens: clear language, consistent meanings, details when needed, reliable feedback, and deliberate reversible actions. Findings below come from static source and routing inspection of clean main 0f9f36e plus the existing shared checkout. They are not claims that a browser interaction or production failure was reproduced. No gateway, worker, token, schedule, job, approval or GPU state was changed.

Highest-value changes

Fix misleading stop/approval feedback and cancellation behavior first. Then make administrative functions discoverable without forcing users to learn two partially overlapping web apps. The current everyday surfaces already have useful foundations: Ask previews before starting, helper repair diagnoses before confirmation, card states use words plus shapes, and Context promotion explains its future effect. Extend those patterns consistently rather than adding another flow builder or control panel.

Verified static findings

Source paths are repository-relative. Long UUID source filenames are mapped at the end. Priority indicates user impact, not a release approval.

Small copy patch for the source owner to review

This is a proposal, not an applied source edit. In ops.js, replace only these strings; rebuild the generated console bundle after normal source review. No backend authority or behavior changes are proposed here.

- setNote(paused ? "Resumed. Work will pick up again." : "Paused. Jobs in progress finish.");
+ setNote(paused ? "New work can start again. Halted jobs need Retry." : "Active attempts halted. New work is paused.");
- <b>Pause everything</b>
+ <b>Stop work</b>
- Stops helpers from taking new work. Jobs in progress finish.
+ Halts active attempts and pauses new work. Resume allows new work; halted jobs need Retry.

For every reason prompt that can cancel, the minimal behavioral fix is:

const reason = prompt("Reason for aborting run " + runId + "?");
if (reason === null) return;
// Only here submit with reason || "Aborted by operator".

The approval-role policy, kill-switch enforcement, scheduled-worker duplicate guard, tenant isolation and shadow/live-write gates must remain unchanged while simplifying wording and interaction.

Documentation corrections to integrate

The new GUI reference addresses these, but old task guides must not contradict it:

• desktop-app-and-tray.md: remove erase-~/.mco as casual uninstall/recovery, qualify external logs, explain Stop/Exit/Reload/task-handoff effects, remove nonexistent GUI port editor, distinguish readiness from end-to-end success.
• overview-dashboard.md: /dashboard is a full technical admin interface; Activity is a fetched window; sidebar Advanced is not a universal admin doorway on clean main.
• jev-routing.md: remove unsupported routing GUI, invented model-output examples and “Zero Hallucination Routing” guarantee; keep sourced advisory boundaries.
• Settings.md, approvals-and-governance.md: use actual halt semantics, explain Resume/retry and conductor pause distinction; correct evidence-download type.
• Schedules.md, scheduling-and-loops.md: name gateway-detected timezone and show the remote-host limitation.
• projects-dashboard.md: use Unassigned work and explain clearing explicit assignment can fall back to workflow grouping.
• agent-fleet-and-presence.md, job-board-and-tasks.md: distinguish clean main from pending admin doorway/reassignment repair; registration/presence is not task execution proof.
• drumline-memory.md: eligible ranked recall is not every saved entry injected into every prompt; promotion is separate from discussion and approval.

Controlled runtime checks still needed

These are checks to run against a disposable fixture gateway with synthetic jobs/tokens/configuration, never permission to operate production:

1. Capture desktop/mobile/short viewport at 100% and 200% zoom, light/dark, reduced motion, keyboard-only and screen-reader naming.
2. Exercise disconnected, connecting, Live, Offline, invalid token and each relevant scoped denial; confirm no demo fallback is mistaken for successful production recovery.
3. Use deterministic fixture responses for partial batch results, slow/error saves, duplicate clicks and dependency outside the loaded job window.
4. Test Cancel in every destructive prompt and backdrop/drawer dismissal with an unsaved draft.
5. Verify JSON evidence download, file entries and UTC date boundary handling without claiming certification.
6. Exercise browser/gateway timezone differences and a DST transition with the scheduler disabled; inspect written fixture schedule only.
7. Run desktop controller mocks for selected/all/Exit/task handoff with active ownership records; no actual worker termination needed for the UI test.
8. Model-provider Test should use a mocked response unless a provider owner authorizes a real request; service health is not a replacement for an end-to-end worker receipt.

Source key

Line numbers describe the inspected shared snapshot. Clean-main source hashes and pending-change classifications are recorded in GUI coverage; verify line positions after concurrent edits. Hidden design tools and unreachable legacy components are not counted as normal operational screens. No claim of screenshot/runtime verification is made.

Changes included in this refresh

The documentation refresh branch fixes the technical dashboard's Cancel behavior for Abort Run and batch cancellation. Cancel now returns before any request. Six JavaScript regression cases exercise cancelled, blank-confirmed and reason-confirmed paths. This source patch has not been applied to an already running gateway; installed builds may still need the update. No execution policy or approval requirement changed.

The help site now uses one task-first home, searchable sections, stable command/control anchors, progressive disclosure for secondary guides, keyboard search, copy feedback and mobile navigation. These are implemented help-site improvements, not a claim that all product recommendations above have shipped.

Apple guidance used for the review

• Design principles: keep meanings and interactions consistent, with useful feedback and room for character.
• Layout: use progressive disclosure to keep common work easy to find.
• Writing: use concise action labels and familiar terms.
• Feedback: make status visible without unnecessary interruption.
• Alerts: reserve disruptive confirmation for consequential actions; a cancelled action must remain cancelled.

Apple's guidance is a design lens, not a claim of Apple certification or an instruction to copy an Apple product.