Design approval request: PR #34 fleet/install UI

[yellowhama]

Scope

Design approval request for PR #34 UI changes:

• /download: one-line Windows installer command and post-install verification copy.
• /install: install command card and Windows-only/planned platform states.
• /fleet and /dashboard/fleet: wording changes so relay-display heartbeat is not presented as proven online/direct work routing.

Design Brief

https://github.com/yellowhama/musu-bee/blob/feat/v33-residual-finalize/docs/DESIGN_BRIEF_PR34_FLEET_INSTALL_2026_06_27.md

Artifacts

• https://github.com/yellowhama/musu-bee/blob/feat/v33-residual-finalize/docs/design-artifacts/pr34-download.png
• https://github.com/yellowhama/musu-bee/blob/feat/v33-residual-finalize/docs/design-artifacts/pr34-install.png
• https://github.com/yellowhama/musu-bee/blob/feat/v33-residual-finalize/docs/design-artifacts/pr34-fleet.png

Approval State

Approval requested. Not approved yet.

Per CONTRIBUTING.md, this still needs an explicit CEO/design approval comment before PR #34 can honestly add Design: Approved.

[yellowhama]

Current evidence refresh for PR #34 design approval:

• UI scope is documented in docs/DESIGN_BRIEF_PR34_FLEET_INSTALL_2026_06_27.md.
• PNG artifacts are committed:
  • docs/design-artifacts/pr34-download.png
  • docs/design-artifacts/pr34-install.png
  • docs/design-artifacts/pr34-fleet.png
• Local design-gate evaluator now reports the issue URL and PNG artifact links are present; the only missing requirement is Design: Approved.
• PR code/test/deploy checks are green except design-gate.
• Live install-channel verifier passes: verify-musu-pro-install-channel.ps1 -Json => ok=true, failure_count=0.
• Strict fleet audit verifier passes on the second machine: verify-fleet-audit-contract.ps1 -Json => ok=true, warn_count=0, remote_cloud_warning_count=0.

This is still not approval. If the UI is acceptable, please add an explicit CEO/design approval comment here. After that, PR #34 can honestly change Design: Pending to Design: Approved and include the approval comment URL.

[yellowhama]

Update after commit f7efdc77 (feat(site): expose fleet proof command):

• /download now shows the hosted fleet-proof.ps1 post-first-launch proof command and a two-PC direct proof variant.
• /install now shows the hosted fleet-proof.ps1 proof command as the next step after installing/opening MUSU.
• docs/design-artifacts/pr34-download.png and docs/design-artifacts/pr34-install.png were refreshed with those commands visible.
• Verification passed locally:
  • npm run test:public-release = 16/16 pass
  • npm run typecheck = pass
  • npm run build = pass
  • npm run lint = exit 0, existing warnings only
  • Playwright screenshot refresh + desktop/mobile horizontal-overflow checks = pass
• PR checks after the force-with-lease correction: Vercel, Playwright, Rust, Web build, landing gate, saas gate, and test all pass. design-gate is the only failing check.
• Local design-gate evaluator result: issue URL and PNG artifact links are present; missing requirement is only the standalone Design: Approved line.
• Live production install channel remains healthy: verify-musu-pro-install-channel.ps1 -Json returned ok=true, failure_count=0, including live /fleet-proof.ps1 checks.

This is still not approval. If the UI is acceptable, please add an explicit CEO/design approval comment here. After that, PR #34 can honestly change Design: Pending to Design: Approved and include the approval comment URL.

[yellowhama]

Update after physical hugh-main proof:

• Hosted public command passed on hugh-main:
  & ([scriptblock]::Create((irm https://musu.pro/fleet-proof.ps1))) -ExpectedNodeName hugh-main -ExpectedDirectPeerName hugh_second -RequireBrainToken -Json
• Evidence is saved in the PR branch at:
  docs/evidence/fleet-proof/1.15.0-rc.22/hugh-main-20260627T010201Z.fleet-proof.json
• Result summary: schema=musu.fleet_node_proof.v1, ok=true, fail_count=0, warn_count=0, installed package 1.15.0.22, advertised_public_url=http://192.168.1.192:4387, online_nodes=2, direct_healthy_nodes=2, expected peer hugh_second, and brain_ingest_token_acl_restricted passing.
• Follow-up musu status --json from hugh_second shows both PCs healthy via direct route.

This closes the rc.22 two-physical-machine direct proof blocker. It is still not design approval: PR #34 keeps Design: Pending until there is an explicit CEO/design approval comment here.