Installed starter command evidence

Installed starter commands

Draft #171, source
55b6cf96bbe6eff3fd2280126c1a7fd0a913f966, adds project creation, native
build/run and web build/serve commands to the installed engine package.
bloom new writes a single source template, a text asset, compatible version
metadata, native-library permissions and the exact engine archive used to create
the project. Keeping .bloom/engine.tgz avoids accidentally resolving the older
registry package with the same preview version number.

Hosted Tests run 34565911332
passes all 22 jobs. PR head and hosted merge checkout have identical Git trees.
The installed CLI creates a project with its default command, verifies installed
source identity, and rejects missing-compiler and unsupported-target controls.
Default creation takes 30.672 seconds after the separate bootstrap package
installation. The resulting project references its own exact engine archive.
Native engine build, all 20 example links, both installed native rendering
modes, compiled-game browser rendering and serial Windows shared tests also pass.
The compiled browser fixture is the small #170 game, not this full starter.

Local candidate evidence retains an actual fresh installed CLI run: the unmodified
starter builds natively in 270.360 seconds. npm start then builds/runs a bounded
copy with capture, asset and cleanup observations in 10.141 seconds, rendering
the 800x450 greeting and animated square on Radeon DX12. It reads
assets/welcome.txt and cleans up once. Restoring the unmodified source completes
the full web build in 63.765 seconds. Screenshot SHA-256:
be7a32be2fb93fb24fa838370dc9c656c7b363ba19fe9b12f1681aa4b9d1acbd.
These local candidate records identify their source and later default-creation
correction separately; they are not relabeled as a final-commit runtime rerun.
The exact committed hosted packaging result and final source diff are included.

A separate fresh-package local check verifies default creation without an
explicit archive option. Cached managed-toolchain hash validation passes; it
does not prove a new machine's initial toolchain setup through this CLI.
Five behavioral tests cover errors, manifest drift, existing-directory
preservation, archive selection and the owned local HTTP server. The CLI uses
the existing qualified Perry 0.5.1220 profile. Local native rendering is headless
with SDK shader DLLs on PATH. Hosted installed rendering uses Microsoft Basic
Render Driver; Windows raster goldens skip that CPU adapter.

Visible native presentation, actual starter asset/text rendering in browsers,
macOS/Linux starter runtime, fresh-machine setup through the command, general
Windows long paths, fixed updates, hot reload and distributable shader runtimes
remain open at this exact source. Later lifecycle work is separate. #171 stays
a draft; no merge or npm release is performed. RTX-specific qualification is
unperformed and does not block continuing on the Radeon 760M.

The archive retains local/hosted logs, reports, captures, source and artifact
hashes. Installed trees and generated binaries are excluded. Publication verifies
ZIP CRC, each included payload's SHA-256 and GitHub's uploaded asset digests.