[ukimsanov]

What

• Studio app, Linux: the install steps lead with the .deb (sudo apt install ./HyperFrames-amd64*.deb), with the AppImage kept as the portable option.

Why

The download page hands Linux browsers the .deb by default (hyperframes-internal packages/demo-next/src/app/studio/download/route.ts: a Linux browser with no os parameter gets deb). The docs still told people to chmod +x an AppImage they never received.

Split out of #5933. The finder rows and a CI check for them are in #5938.

Test plan

• File names checked against the live release feed (from ci(docs): catch docs that drift from the CLI #5933)
• lefthook: format, commitlint

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated
hyperframes	🟢 Ready	View Preview	Oct 21, 2026, 11:41 PM

💡 Tip: Enable Automations to automatically generate PRs for you.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[jrusso1020]

Leading Debian/Ubuntu users to the .deb matches the download route’s Linux default, and the portable AppImage option remains available.

Blocker — the install commands do not match the files the linked page downloads (docs/studio-app/index.mdx:42,49,60–61). I followed the live HEAD redirects: https://www.hyperframes.dev/studio/download?os=deb serves .../HyperFrames-amd64.deb, and os=linux serves .../HyperFrames-x86_64.AppImage; both files return 200 without a Content-Disposition filename override. The new HyperFrames-amd64-*.deb and HyperFrames-x86_64-*.AppImage patterns match neither filename. Thus a fresh download followed by the documented command fails. The feed’s versioned artifact URL is not the fixed-name URL the browser download route returns. Please use the actual fixed names (or explicitly instruct users to substitute their downloaded filename), update the prose and verify both paths.

No packages installed or downloaded in full; validation used route source, live HEAD responses and filename matching.

Verdict: REQUEST CHANGES
Reasoning: The primary Linux installation instructions fail for the files served by their own link. Approval also needs James’s go or a trusted stamper’s request.
— hf-review

[jrusso1020]

Re-review at eebf5574809961c285e79d0142b315ccedf916c3: the original filename finding is fixed in docs/studio-app/index.mdx:42,49,60–61. The prose names HyperFrames-amd64.deb; both new glob patterns include the website's fixed filenames. Bash expansion controls also match browser-renamed copies containing spaces and build-suffixed artifacts. The rest of the guide is unchanged.

No package installation or full artifact download performed. The earlier review established the fixed-name route/CDN behavior; this pass checks the exact documentation delta and shell filename expansion. The PR body's command example still has the old extra hyphen; please align that description with the repaired file.

Verdict: COMMENT
Reasoning: The blocking installation mismatch is resolved; no remaining code blocker found. This is not an approval: James’s go or a trusted stamper’s request is still required for a stamp.
— hf-review

The filename blocker is resolved at eebf557. Superseded by my exact-head COMMENT re-review; this dismissal is not an approval or merge authorization.

[jrusso1020]

Approval at exact head eebf5574809961c285e79d0142b315ccedf916c3, unchanged since my code review. James directly authorized approval in the originating Slack thread; no new code findings were added in the refreshed review/comment history.

Linux commands now match the fixed-name downloads, including browser-renamed copies and build-suffixed artifacts. The installation blocker and stale body example are resolved.

Validation and limits: Source/live HEAD checks from the initial review plus Bash filename expansion controls; no installation or full artifact download.

Verdict: APPROVE
Reasoning: The reviewed code remains clear under the stated scope and collection contract; earlier blocking findings are resolved where applicable. No merge, deployment or publication performed by me.
— hf-review