fix(den-web): clarify installer download feedback

[reachjalil]

Summary

• remove the synthetic five-second installer download spinner and timer
• show immediate, honest “Download requested” feedback
• direct users to the browser Downloads menu for real progress while retaining a retry action
• narrow the matching coded eval to prevent the fake loading/completion states from returning

Root cause

The install page still modeled the older server-side installer preparation flow. The current flow redirects directly to a normal release asset, but the UI continued to display a fixed five-second “Preparing” state and then claimed “Download started” without observing the browser. That made a healthy browser-managed download look stalled or broken.

User impact

Selecting any installer platform now produces immediate guidance that matches what the app can actually know. Download progress remains owned by the browser instead of being represented by a fake app-level spinner.

Verification

• pnpm --filter @openwork-ee/den-web typecheck — passed
• pnpm evals:typecheck — passed
• pnpm evals --flow install-download-feedback --cdp-url http://127.0.0.1:45603 against the isolated local Den stack — passed on a055183cb (1 passed, 0 failed, 0 skipped)
• confirmed the current macOS ARM64 and Windows x64 generic installer release assets resolve successfully

The reporter supplied a screen recording reproducing the misleading spinner behavior. The corrected behavior has not yet been manually confirmed by the reporter.

Risks and remaining gaps

• No download URL, server route, token handling, or installer artifact behavior changed.
• The coded UI flow intentionally prevents navigation so it can assert the status panel; it does not download the installer artifact through the browser.
• Cross-browser placement and wording of native Downloads menus may vary, but the page no longer claims to know native download completion.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
openwork-landing	Ready	Preview, Comment, Open in v0	Jul 22, 2026 10:09am

[vercel]

@reachjalil is attempting to deploy a commit to the Different AI Team on Vercel.

A member of the Team first needs to authorize it.

[reachjalil]

fraimz — ✅ PASSED

1 passed · 0 failed · 0 skipped — run 2026-07-22T10-13-36-362Z

Full frame proof with validated screenshots: evals/results/2026-07-22T10-13-36-362Z/fraimz.html (re-run: pnpm fraimz --flow install-download-feedback)

✅ install-download-feedback — Installer downloads hand progress off to the browser clearly

User-facing flow demo

1. Choosing a platform immediately confirms the request and points to browser progress

   🎙 When I choose my platform, the page immediately confirms the request, points me to my browser's Downloads menu for real progress, and keeps a retry available without a fake spinner or success countdown.

   • 📸 install-download-feedback-01-browser-download-feedback.png — 8 validations passed
   
   • ✅ Script frame 1 narrated: "When I choose my platform, the page immediately confirms the request, points me to my br"

[reachjalil]

Closing during the 2026-07-27 repository-progress reconciliation. Superseded by the merged organization install work in #3084 and #3099 on the same install-screen journey. No unmerged branch is being treated as delivered; any residual gap must be reproduced before new implementation.