Slice 1: Create vv1.89.1 branch — license unlock on v1.89.1, image builds + boots locally

[utarn]

Parent

• PRD: Upgrade fork to v1.89.1 (preserve license unlock; verify migration + passthrough cost) #1

What to build

Create the vv1.89.1 branch on the fork, frozen at the immutable upstream v1.89.1 tag, carrying only the fork-specific license/premium unlock. Cherry-pick the single license commit onto v1.89.1; drop the two UI hunks that targeted the old local-useState premium pattern (v1.89.1 routes premium state through the useAuthorized hook, which the kept hook change already forces to premium_user = true); accept the proxy-server hunks with context-fuzz fixes only; and update the CI image-build workflow's push trigger from the old branch name to vv1.89.1. The six-commit Anthropic passthrough custom-pricing cost fix is NOT carried — upstream v1.89.1 already contains equivalent logic.

Then prove the branch is coherent end-to-end at the thinnest level: build the native arm64 image and boot the proxy against a fresh (empty) local Postgres, confirming premium is unlocked and the proxy is healthy, and run the existing Anthropic-passthrough cost unit suite on the branch. The local arm64 image is throwaway — it is not pushed to the registry or to modelharbor.

Acceptance criteria

• vv1.89.1 exists at the upstream v1.89.1 tag and contains exactly one local commit (the license/premium unlock)
• The obsolete page.tsx premium hunks are dropped; the useAuthorized hook change is kept
• The CI image-build workflow triggers on vv1.89.1 (old branch name removed)
• A native arm64 image builds successfully from the branch
• The proxy boots against a fresh local Postgres and reports as healthy
• Premium is unlocked (license short-circuit active; premium_user = true via the hook)
• The Anthropic-passthrough logging-handler unit suite passes on the branch
• The local arm64 image is not pushed to the registry or modelharbor

Blocked by

None - can start immediately