chore(release): 0.12.59-rc.37 live Identity cutover

[adrianwebb]

Outcome

Prepare 0.12.59-rc.37 to deliver the merged live Identity migration. Version-only change; no new functional implementation.

Work authority

• Work item / Issue: Identity: independent SSO session and multiple Market API connections #101
• Proposal / decision: Platform #467; user-directed immediate local Identity cutover.
• Assignment / checkpoint: N/A — direct authorized work.
• Actor: Codex
• Human authority: adrianwebb
• Agent / capacity provider: N/A — local agent.
• Exact base ref: staging 499b3e3
• Exact head ref: codex/identity-live-rc37 717b8b2

Contributor mode (select one):

• Human-authored
• Agent-assisted under human authority
• Agent-authored under human authority

Plan

Verify exact version change, merge staging, publish/read back the candidate, and activate the coordinated composition. No purge or bootstrap reinstall.

Changes and commits

717b8b2: package.json and lockfile version only.

Verification

Admin #107, Verify 34479139118 passed. git diff --check passed. Required exact-head checks run on this PR. Reuse functional evidence; managed acceptance remains mandatory.

• I ran the narrowest relevant package verification and documented any checks that could not be run.

Risk and rollback

No installed change from this PR. After migration use a coordinated application/shared-database restore point; never activate old writers over migrated state. Preserve the current accepted rollback catalog.

Completion summary

Release preparation complete; publication and host acceptance follow the required checks.

AGPL committer authorization

Base-owned provider-author check remains authoritative where applicable.

Submission checklist

• The change is bounded to the stated work item and target repository.
• Exact base and head refs are recorded and the branch is ready for review.
• Verification and compatibility evidence are recorded above.
• No plaintext secrets, credentials, machine state, or unrelated residue are included.
• Plan, status, commits, and completion summary form a complete durable record.
• Rollback or recovery steps are documented and executable.