[PR #213] [MERGED] fix(hopper): select verified Linux demo mode explicitly #1863

Closed
opened 2026-10-16 21:11:54 +00:00 by bsakaguchi · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/213
Author: @N0zoM1z0
Created: 7/14/2026
Status: ✅ Merged
Merged: 7/14/2026
Merged by: @morluto

Base: main ← Head: agent/integration-fixes


📝 Commits (3)

  • 04c5fd6 fix(hopper): select verified Linux demo mode explicitly
  • db202c2 test(hopper): cover verified Linux rejection
  • d93257b test(hopper): verify alternate Linux launcher path

📊 Changes

7 files changed (+254 additions, -111 deletions)

View changed files

📝 .github/workflows/real-hopper-linux.yml (+1 -1)
📝 scripts/verify-package.mjs (+125 -96)
📝 scripts/verify-real-hopper-linux.mjs (+14 -3)
📝 src/hopper/BridgeLauncher.ts (+19 -6)
📝 src/hopper/HopperProvider.ts (+8 -3)
➕ tests/bridgeLauncher.test.ts (+85 -0)
📝 tests/runtime.test.ts (+2 -2)

📄 Description

Summary

  • replace launcher-basename inference with an explicit native/verified-Linux launch mode
  • route supported Linux paths and symlinks through the pinned demo adapter
  • keep the SHA-256 allowlist fail-closed so arbitrary wrappers are never executed
  • make Linux runtime and packaged-artifact checks assert the intentional unsupported-build rejection
  • preserve successful Hopper-backed package coverage on supported native hosts

The root cause was using a filename as both a platform-mode signal and a trust decision. Launch intent is now explicit, while binary trust remains enforced by the existing content hash check.

Closes #166

Verification

  • npm run typecheck
  • npm run lint (existing warnings only)
  • npm run format:check
  • focused launcher/provider and production-runtime tests
  • npm_config_engine_strict=false npm run verify:package

Real Hopper verification was not performed in this Linux environment.


🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/morluto/rea/pull/213 **Author:** [@N0zoM1z0](https://github.com/N0zoM1z0) **Created:** 7/14/2026 **Status:** ✅ Merged **Merged:** 7/14/2026 **Merged by:** [@morluto](https://github.com/morluto) **Base:** `main` ← **Head:** `agent/integration-fixes` --- ### 📝 Commits (3) - [`04c5fd6`](https://github.com/morluto/rea/commit/04c5fd63b72e6e497363ecbde5e24088eef639cd) fix(hopper): select verified Linux demo mode explicitly - [`db202c2`](https://github.com/morluto/rea/commit/db202c2b6ac9ce771c401cc558c56ecf6d2e51ee) test(hopper): cover verified Linux rejection - [`d93257b`](https://github.com/morluto/rea/commit/d93257b50fae81272cbd2da28ba24d03647c2c99) test(hopper): verify alternate Linux launcher path ### 📊 Changes **7 files changed** (+254 additions, -111 deletions) <details> <summary>View changed files</summary> 📝 `.github/workflows/real-hopper-linux.yml` (+1 -1) 📝 `scripts/verify-package.mjs` (+125 -96) 📝 `scripts/verify-real-hopper-linux.mjs` (+14 -3) 📝 `src/hopper/BridgeLauncher.ts` (+19 -6) 📝 `src/hopper/HopperProvider.ts` (+8 -3) ➕ `tests/bridgeLauncher.test.ts` (+85 -0) 📝 `tests/runtime.test.ts` (+2 -2) </details> ### 📄 Description ## Summary - replace launcher-basename inference with an explicit native/verified-Linux launch mode - route supported Linux paths and symlinks through the pinned demo adapter - keep the SHA-256 allowlist fail-closed so arbitrary wrappers are never executed - make Linux runtime and packaged-artifact checks assert the intentional unsupported-build rejection - preserve successful Hopper-backed package coverage on supported native hosts The root cause was using a filename as both a platform-mode signal and a trust decision. Launch intent is now explicit, while binary trust remains enforced by the existing content hash check. Closes #166 ## Verification - `npm run typecheck` - `npm run lint` (existing warnings only) - `npm run format:check` - focused launcher/provider and production-runtime tests - `npm_config_engine_strict=false npm run verify:package` Real Hopper verification was not performed in this Linux environment. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
bsakaguchi 2026-10-16 21:11:54 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
morluto/rea#1863
No description provided.