# Progress Memory

Last updated: 2026-06-13

## Current State

- `v1.7.90-alpha` release is complete, tagged, pushed, uploaded, and verified on vps2.
- Release commit: `bb808df8` (chore: release v1.7.90-alpha).
- Feature commit:  `c800293f` (fix: bitcoin receive, AIUI pointer input, electrs self-heal, OTA timeout).
- Gitea tag: `v1.7.90-alpha` (on origin/gitea-vps2).
- Live OTA manifest on the update host (146.59.87.168) now resolves to `1.7.90-alpha`; both
  artifact download URLs (binary + frontend tarball) return HTTP 200.
- v1.7.89-alpha was already fully shipped before this session.

## What shipped in v1.7.90-alpha

- Bitcoin receive address generation fixed (correct address type, no more 400).
- AIUI/app session: on-screen pointer can click + type into app content (incl. app store
  search); "open in new tab" opens the phone browser; mobile credential modal centered.
- Electrs self-heals from a corrupt index and shows a percent/block-height progress screen.
- update.rs: retired tx1138 secondary mirror dropped (one-time migration); longer download
  timeout for slow connections.

## Verification

- Full release harness green (8 stages): git-diff, cargo-fmt, catalog-drift, release-manifest,
  ui-type-check, ui-unit-tests (80 files / 655 tests), cargo-check, cargo-test-weekly.
- Freshly built binary embeds `1.7.90-alpha` (no stale 1.7.89); frontend dist rebuilt fresh
  (new AppSession bundle); manifest sha256 + size match on-disk artifacts.

## Known gaps / follow-ups

- `gitea-local` (localhost:3000) push FAILS from this node — redirects to /login (auth).
  The v1.7.88 and v1.7.89 tags were also already missing there, so this is a pre-existing
  condition on this node, not a v1.7.90 regression. vps2 is the primary OTA mirror and is fine.
- OTA self-update verification on THIS node (.116) not yet observed this session — the node
  should auto-apply from the live 1.7.90-alpha manifest; confirm
  `update_state.json.current_version == 1.7.90-alpha` after the scheduler runs.

## Resume Context

- If a later session resumes, continue from the next active product/release task, not this
  finished release.
- Broader context: docs/WEEKLY_RELEASE_TRACKER.md, docs/RESUME.md, docs/NEXT_TERMINAL_HANDOFF.md