[iHow1]

Summary

• promote the verified Alpha.34 Core surface to stable ihow-memory@0.1.0
• move current English and Chinese user commands from @next to the unqualified stable install path
• preserve the runtime evidence boundary: single-machine smoke/dogfood is not production certification, replayable activation remains ACTIVATION_COMPLETION_UNATTESTED, frozen runtimes and dsh-ihow-memory still require separate upgrade/restart/verification
• align package, lockfile, changelog, package contracts, Hermes metadata, and rollback assertions with the stable version

Verification

• node --test tests/package-completeness.test.mjs tests/hermes-package.test.mjs tests/upgrade-skew.test.mjs — 14/14 pass
• npm run build — pass
• npm run typecheck — pass
• npm run proof — pass
• node bin/ihow-memory.mjs --version — 0.1.0
• npm pack --dry-run --ignore-scripts --json — ihow-memory-0.1.0.tgz, 110 entries, 397154 bytes
• git diff --check — pass
• npm view ihow-memory@0.1.0 version --userconfig /dev/null — expected 404; stable version is not already occupied
• local npm run secret-scan fails closed because the CI-only IHOW_PUBLIC_BOUNDARY_DENYLIST secret is intentionally unavailable locally; PR CI owns the authoritative scan

Release boundary

This PR prepares the immutable stable candidate only. Merge, tag, npm publication, registry readback, and loaded-runtime upgrade remain separate gates.