v0.3.2

chore(main): release 0.3.2 (#563)

:robot: Release Please generated the 0.3.2 release metadata.

##
[0.3.2](https://github.com/jason931225/console/compare/v0.3.1...v0.3.2)
(2026-08-04)

### Bug Fixes

* **consolidation:** stabilize the post-pivot restart boundary
([#562](https://github.com/jason931225/console/issues/562))
([4f58ecf](https://github.com/jason931225/console/commit/4f58ecf138fdc1e829fbe520a45d2ede2de7d837))

## Signed release authority

- Protected base `B`: `4f58ecf138fdc1e829fbe520a45d2ede2de7d837`
- Release Please generated commit `G`:
`28c949306e1272b668df3086cf04597679c3256c`
- Signed candidate `C`: `0075bba955410f7e9b8b30efd4efc5159a6643f2`
- Signed ledger-only authority tip `T`:
`05d6b6cefd72cddad8251251ae75842ad7aa3d5f`
- Local protected-main synthetic merge `M`:
`8399ff3757fb090de7f7fc45d5cd31ee8a93711b`

`B..G` changes only `.release-please-manifest.json` and `CHANGELOG.md`,
advancing `0.3.1` to `0.3.2`. `G..C` changes only the canonical
disk-wipe handoff to record the owner-directed solo-repository merge
policy. `C..T` adds only
`docs/program/ledger/2026-08-03-release-0-3-2-authority.md` as a regular
mode-100644 file. Both `C` and `T` verify against the repository-pinned
ED25519 authority.

## Verification and review

- Protected-main bootstrap simulation: PASS.
- Authenticated candidate checks: 74/74 PASS.
- Complete exact-`T` local verifier: PASS.
- Two independent adversarial exact-object reviews of the final tuple:
PASS with no unresolved findings. An earlier tuple was rejected for a
fresh-session policy contradiction; that result was not carried forward,
and the canonical handoff was repaired before resealing and re-review.
- Hosted exact-`T` authority, CI, and Security checks: PASS. All 16
GitHub Actions app-bound required contexts passed on exact `T`
(authority run `30870705918`, CI run `30870706935`, Security run
`30870706921`).

## Solo repository policy

The owner corrected the incompatible two-person setting for this
solo-development repository. Protected `main` requires zero GitHub
approvals and `require_last_push_approval=false`. Strict up-to-date
checks, stale-review dismissal, conversation resolution, admin
enforcement, two independent exact-object reviews, and all 16 app-bound
contexts remain in force.

## Boundaries

This source release does not authorize production promotion or disk
erasure. Product, jurisdiction, Korea-control, production-exposure,
deployment, and readiness conclusions remain `HOLD`. Signing identity,
restricted inputs, infrastructure recovery material, business inputs,
and local-only state outside Console remain separate custody blockers.

---
Generated release metadata remains attributable to [Release
Please](https://github.com/googleapis/release-please).

---------

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Jason Lee <jason19931225@gmail.com>