Portable installed web command evidence
Pre-release
Portable installed web command - PR #166
Source: f30ebd0067b4dba9d4bb25c5e0ac9cb366a06c0b, stacked on #165.
PR: #166
The installed command previously invoked /bin/bash through npm on Windows.
The Bash build also masked wasm-pack failures behind a tail pipeline and could
assemble stale output. A shared Node command now preserves subprocess failures,
requires fresh compiler outputs and assembles the Perry game, engine and assets.
Bash and Python compatibility entry points delegate to it.
Validation
The initial candidate passes a full installed build on local Node 24.21.0 but
its hosted Windows regression process exits 3221226505 during directory-copy
assembly. The original failure remains in this archive. The runner image lists
Node 22.23.2; that initial run did not print its runtime version. A similar
Windows Unicode cpSync failure is documented in
Node issue 59636. This is a likely
match, without an independently captured native stack establishing identity.
The final command awaits asynchronous directory copies. All nine regression
checks pass locally and on hosted Windows Node 22.23.2, whose version is now
recorded directly. These checks cover actual subprocess failure propagation,
stale/missing output, spaces and Unicode paths, repeated assembly, optional and
failing optimizers, engine-only mode and unsupported Perry HTML. Their fake
compiler fixtures qualify orchestration, not real compilation or rendering.
A fresh actual package at the exact final source installs and completes a real
Perry 0.5.1220 plus wasm-pack web build in 46.109 seconds. It produces a
7,839,664-byte engine WASM, the gated game page, bindings and copied assets in
an output path containing spaces. WASM SHA-256:
d58f28fadb2974608dbf655600d86b6287c5940e5e0fa6ee261ac79e46dc1e62.
The original splicer and new implementation agree on actual Perry output after
newline normalization. The local toolchain uses the qualified source-built
Perry runtime profile and a Cargo build cache; this is not a cold-machine test.
Hosted Tests run 34556841600
passes all 22 jobs, including the required Windows pack/install/help check,
native engine build and all 20 native example links. The PR head and hosted
merge checkout have identical Git trees. Hosted Windows raster goldens skip
the CPU adapter; their nominal pass count does not qualify physical rendering.
Scope and archive
This proves installed command execution, compilation and assembly. Real
compiled-game browser rendering, the shared lifecycle and one-command starter
remain open. Native installed startup is handled separately in draft #167.
Stable npm 0.4.16 still contains the old Bash entry point; no npm release or PR
merge is part of this evidence publication. Named RTX hardware remains unavailable.
The archive retains failures, candidate patches, full build logs, output hashes,
hosted artifacts and exact source files. Candidate v1's retained installed tree
was later used for native diagnostics; its original archive/logs are unchanged,
and the final v2 proof uses a new clean install. The initial installed-source
receipt concerns the earlier synchronous-copy candidate, not final f30ebd0.
Package archives, generated executable/WASM/HTML output, installed dependency
trees and private diagnostic projects are excluded. Every included payload is
hashed, and ZIP CRC plus all payload and uploaded asset digests are verified.