[iHow1]

Summary

• prepare ihow-memory@0.1.0-alpha.32 from the merged bounded-read and managed OMP lifecycle work
• document Alpha32's exact trust and activation boundaries in English and Chinese
• update package, lockfile, rollback, Hermes package, and release-completeness version contracts

Included behavior

• memory.read defaults to a strict 8,000-character preview across Core, CLI, console, and MCP; full content requires explicit mode: "full" / --full
• OMP gains managed session-start and prompt recall, native PreCompact checkpoints, exact session switch/shutdown capture, transcript discovery, wiring verification, activation evidence, and runtime capabilities
• replayable OMP lifecycle evidence remains READY — WAITING FOR FIRST ACTIVITY with ACTIVATION_COMPLETION_UNATTESTED; it does not prove host identity or ACTIVE

Verification

• npm run typecheck
• npm run build
• npm test — parallel core 928/928; isolated integrations 209 pass, 0 fail, 2 environment skips
• npm run secret-scan
• npm run proof
• npm run release:evidence:check — release eligible; evidence bound to e11f058bbf9450350b4e43d2533ff28d8b95d1d8
• npm pack --dry-run --json — ihow-memory@0.1.0-alpha.32, 110 entries; includes dist/omp-extension.js and dist/omp-wiring.js
• git diff --check

Release boundary

This PR does not tag, publish npm, create a GitHub Release, deploy, or activate an already-running frozen runtime. DSH/Paseo ACP lifecycle support is not included.