fix: harden user-owned signing and release validation

[joeblau]

Wallet onboarding could reuse an unverified policy, compact CSS could bypass the HIG token guard, and test/release workflows could report incomplete evidence or publish from an arbitrary manual branch. This change requires each user’s own Privy app and local owner authorization, rejects unsupported signing envelopes, and makes lifecycle/release results verifiable.

Three agents reviewed the six open issues in isolated worktrees; integration adds the CSS regression and reconciles the acceptance record.

Issue	Result
#49	Fixed: declarations are checked anywhere on a line; the exact reported mutation fails docs:check.
#11	Versioned domain/network/no-export policy, owner-authorized attachment, policy revalidation, retry recovery and initialized account/network guards. Live Privy positive-sign/withdrawal-denial evidence remains pending.
#37	User-owned Privy onboarding, external approvals, resumable stages, exchange reconciliation and every documented command validated through CLI schemas. Actual coding-agent testnet session remains pending.
#39	Fail-closed nightly testnet harness, both approvals, runner RPC, reconciled order/modify/cancel, event replay/follow, rotation/revocation and audit artifacts. Dedicated QA credentials and a successful live run remain pending.
#40	Script-free packed npm global install and installed bunx verification; Node22.12/24 on macOS/Linux CI; package metadata/license corrected. Public registry installation awaits publication.
#41	Reviewed tagged-main gates, four native binary checks, exact tarball/provenance publication and registry verification. Manual dispatch only builds candidates; version dispatch uploads a validated patch under the organization’s Actions-PR restriction. Publishing configuration remains pending.

Validation: build, lint, typecheck, 103 offline CLI tests, two docs guard tests, docs build/check (16 HTML pages, 597 links/assets, 13 social cards), script-free global npm and installed bunx smoke pass. All four native executables compile locally; native macOS ARM and the Node22.12 packed install were exercised. npm publish dry-run and Changesets version/lock/skill synchronization were validated. No live account trading or package publication occurred.

Privy sees opaque Hyperliquid L1 action hashes. This policy cannot inspect per-action contents/notional; local controls and Hyperliquid API-agent permissions supply those boundaries. Production user credentials remain on user-controlled infrastructure and never pass through Bloxwap.

Fixes #49. Refs #11, #37, #39, #40, #41.