pushframe 5.0.2__tar.gz → 5.0.4__tar.gz

{pushframe-5.0.2 → pushframe-5.0.4}/.github/workflows/release.yml

@@ -36,7 +36,7 @@ jobs:
     outputs:
       version: ${{ steps.version.outputs.version }}
     steps:
-      - uses: actions/checkout@v4
+      - uses: actions/checkout@v7
       - name: Assert tag == pyproject == pushframe.__version__
         id: version
         run: |
@@ -56,8 +56,8 @@ jobs:
     runs-on: ubuntu-latest
     environment: release
     steps:
-      - uses: actions/checkout@v4
-      - uses: astral-sh/setup-uv@v5
+      - uses: actions/checkout@v7
+      - uses: astral-sh/setup-uv@v10.2.0
         with:
           enable-cache: true
       - name: Build sdist + wheel
@@ -70,8 +70,8 @@ jobs:
     needs: check
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v4
-      - uses: astral-sh/setup-uv@v5
+      - uses: actions/checkout@v7
+      - uses: astral-sh/setup-uv@v10.2.0
         with:
           enable-cache: true
       - name: Install uv-managed standalone python (the deb's runtime)
@@ -94,8 +94,8 @@ jobs:
     runs-on: ubuntu-latest
     environment: release
     steps:
-      - uses: actions/checkout@v4
-      - uses: astral-sh/setup-uv@v5
+      - uses: actions/checkout@v7
+      - uses: astral-sh/setup-uv@v10.2.0
       - name: Restore the APT signing key from the secret
         env:
           PUSHFRAME_APT_SIGNING_KEY: ${{ secrets.PUSHFRAME_APT_SIGNING_KEY }}
@@ -126,8 +126,8 @@ jobs:
     runs-on: ubuntu-latest
     environment: release
     steps:
-      - uses: actions/checkout@v4
-      - uses: astral-sh/setup-uv@v5
+      - uses: actions/checkout@v7
+      - uses: astral-sh/setup-uv@v10.2.0
         with:
           enable-cache: true
       - name: Build sdist + wheel

{pushframe-5.0.2 → pushframe-5.0.4}/.github/workflows/tests.yml

@@ -9,10 +9,10 @@ jobs:
   offline-suite:
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v4
+      - uses: actions/checkout@v7
 
       - name: Install uv
-        uses: astral-sh/setup-uv@v5
+        uses: astral-sh/setup-uv@v10.2.0
         with:
           enable-cache: true
 

{pushframe-5.0.2 → pushframe-5.0.4}/.planning/MILESTONES.md

@@ -1,5 +1,30 @@
 # Milestones
 
+## v5.0 — Distribution & Rename: pushframe packages (Shipped: 2026-09-29)
+
+**Phases completed:** 3 phases (20-22), 4 plans — the first milestone
+about *shipping the tool itself* rather than its features.
+
+**Key accomplishments:**
+
+| Phase | Delivered | Proof |
+|-------|-----------|-------|
+| 20 — Rename & repo switch | `auraframes`→`pushframe` (module, binary, config migration), env `PUSHFRAME_*` primary, standalone repo `coredmp95/pushframe` (not a fork), MIT LICENSE + provenance | 407 tests green through the rename; live migration validated; name cleared on PyPI + trademark-adjacency checked |
+| 21 — Debian + APT | Hermetic `.deb` (embedded CPython 3.14, lintian 0E/0W, clean removal), signed APT repo live on GitHub Pages, container journeys for both channels | bytecode-ownership defect caught by our own container test and fixed for every user; live-URL journey exit 0 |
+| 22 — PyPI + releases | Trusted publishing (OIDC, zero PyPI tokens), tag-triggered release workflow, `--version` single-sourced, OPERATOR-STEPS + CHANGELOG | v5.0.2 run all-green 5/5 jobs; v5.0.3 carries the Changelog URL |
+
+**Shipped releases:** 5.0.0 → 5.0.1 (page metadata) → 5.0.2 (first
+pipeline-complete) → 5.0.3 (changelog URL) — each on PyPI + TestPyPI +
+APT + GitHub Releases simultaneously. First real deployment:
+venus.coredmp.net via the signed APT repo (human-driven: keyring →
+sources → install).
+
+**Known gaps carried forward:** 5.0.0 remains on PyPI (empty page,
+immutable) — yank candidate; `AURA_*` env vars in a one-release
+deprecation window; credentials still live in env vars/.env (v5.1's
+charter: config wizard + token-first sessions).
+
+
 ## v4.0 Local Google Photos Album Sync (Shipped: 2026-09-29)
 
 **Phases completed:** 4 phases (16-19), 10 plans, offline suite 349 → **401 tests**

{pushframe-5.0.2 → pushframe-5.0.4}/.planning/PROJECT.md

@@ -364,3 +364,5 @@ sequences write-path reliability first, then Google account linking → album di
 album-to-frame mirroring via a pruned local cache, then the carried debt. Biggest open
 unknown: whether Google's post-March-2025 Photos API still permits enumerating a user's own
 albums, or whether album selection has to go through the Picker API.*
+
+**Current Milestone:** v5.1 — Operations: Config, Sessions, Multi-frame & Scheduling (started 2026-09-29)

pushframe-5.0.4/.planning/REQUIREMENTS.md

@@ -0,0 +1,118 @@
+# Requirements: pushframe — v5.1 Operations: Config, Sessions, Multi-frame & Scheduling
+
+**Defined:** 2026-09-29
+**Core Value:** `pushframe` becomes *operable unattended*: configuration is a
+conversation (`pushframe config`) instead of env-var archaeology, the Aura
+password never touches disk (token-first sessions), mirrors run on a schedule
+without root (systemd user timers), one album can mirror to every frame
+(named mappings), and every command that needs a machine prerequisite fails
+with the remedy instead of a traceback.
+
+## Requirements
+
+### Config wizard (CFG)
+
+- [ ] **CFG-01**: `pushframe config` (interactive) asks for and stores: Aura
+  email, Aura secret, default frame name, and the tool's non-secret settings
+  (default album, write-budget override, debug) — prompts are masked for
+  secrets (getpass-style), values are validated (email shape; login test on
+  request), and the result is written to `~/.config/pushframe/config.json`
+  with mode `0600`. Re-running edits in place (existing values shown
+  redacted, Enter keeps).
+- [ ] **CFG-02**: precedence is `env var > config file > built-in default`
+  everywhere the CLI reads configuration; the env vars keep working exactly
+  as today (deprecation window opened in 5.0.0 stays honored); `pushframe
+  config show` prints the *effective* configuration with secrets redacted
+  and the source of each value (env/file/default).
+- [ ] **CFG-03**: `pushframe config import` migrates an existing `.env`
+  (or exported `PUSHFRAME_*`/`AURA_*` set) into `config.json` without
+  retyping; the command reports what it took from where and never stores
+  what it could resolve from the environment instead.
+- [ ] **CFG-04**: `pushframe config path` prints the config file location;
+  `pushframe config set <key> <value>` / `get <key>` exist for scripts;
+  unknown keys fail with the list of known keys.
+
+### Credential handling (SEC — token-first)
+
+- [ ] **SEC-01**: the Aura password is **never persisted** — not in
+  `config.json`, not in env files the tool writes. `pushframe config`
+  authenticates once, stores the returned `auth_token` (0600) plus the
+  account email, and discards the password when the process exits.
+- [ ] **SEC-02**: every command that needs the API uses the stored token
+  (header auth) and falls back to interactive password login **only** when
+  the token is absent/expired/revoked, after which the new token is
+  persisted; a `--password` / `PUSHFRAME_PASSWORD` override still wins
+  (CI/script path) but is documented as discouraged for humans.
+- [ ] **SEC-03**: `pushframe logout` deletes the stored token (and only the
+  token); token material never appears in logs, output, or the history
+  ledger (existing redaction stays enforced by tests).
+
+### Scheduling (TMR — systemd user)
+
+- [ ] **TMR-01**: `pushframe schedule add <job>` installs a systemd **user**
+  timer + service unit under `~/.config/systemd/user/` for the supported
+  jobs (`google-sync --apply` for a named pair, directory `sync`) with a
+  prompted or `--every` schedule; no root anywhere; `pushframe schedule
+  list` shows installed jobs with next-run times (from `systemctl list-timers`).
+- [ ] **TMR-02**: `pushframe schedule remove <job>` uninstalls cleanly
+  (units + timer state); installed units are named `pushframe-<job>.service/.timer`
+  and never collide with system units.
+- [ ] **TMR-03**: unattended correctness: a scheduled run uses only
+  stored configuration (no prompts), honors SAFE-02's removal threshold
+  (a run that would exceed it **skips and logs** rather than fails the unit),
+  writes a per-job log (`~/.local/state/pushframe/<job>.log`), and the
+  docs cover `loginctl enable-linger` for headless machines (venus).
+
+### Multi-frame (MTF — GSF-01 closed)
+
+- [ ] **MTF-01**: named **album↔frame mappings** live in config: one album
+  may mirror to N frames and one frame may receive from N albums
+  (`pushframe config` manages them; `--pair <name>` selects one,
+  `--all` selects every pair).
+- [ ] **MTF-02**: `google-sync` resolves a pair the same way it resolves the
+  current single pair today (dry-run default, `--apply` gated, SAFE-01..04
+  per pair); **state is per-pair** — the manifest and staging cache are
+  sharded by pair so two pairs never share dedupe memory.
+- [ ] **MTF-03**: the write budget is **account-wide and shared** across
+  pairs within one run (`--all`), preserving SAFE-02 semantics at account
+  level; per-pair reports stay exact (pairs list what they did, and a
+  skipped pair never blocks the others).
+
+### Preflights & error quality (PRF)
+
+- [ ] **PRF-01**: commands with machine prerequisites check them up front
+  and fail with per-item remedies — `google-link` (playwright package,
+  Chrome/Chromium, profile dir) ships in 5.1's first cut (already
+  implemented on master), extended to: `google-sync` (vault present),
+  `schedule` (systemd user session available, `loginctl` linger status),
+  and `sync`/`push` (target dir exists/contains images).
+- [ ] **PRF-02**: no user-facing command may end in an unhandled traceback
+  for a foreseeable condition (missing module, missing browser, missing
+  vault, ambiguous frame, multi-arch notice): each maps to a named,
+  one-screen error with the next action. A test sweep asserts the
+  traceback-free contract for the documented failure modes.
+
+## Non-Goals
+
+| Feature | Reason |
+|---------|--------|
+| OS keyring storage (gnome-keyring/Secret Service) | headless servers (venus) lack a keyring session; file-0600 token is the contract, keyring is a later nicety |
+| Encrypting config.json with a user passphrase | circularity (where does the passphrase live?); token-first removes the high-value secret anyway |
+| Cron support | systemd user timers are the modern path; cron adds a second code path for no new capability |
+| Real deletion exposure on the Google verb | unchanged posture from v2.0/v4.0; hide-not-delete stays |
+| Many-to-many with per-pair schedules | each pair is its own scheduled job — same capability, simpler model |
+
+## Traceability
+
+Every v5.1 requirement maps to exactly one phase; numbering continues from
+Phase 22.
+
+| Requirement | Phase | Status |
+|-------------|-------|--------|
+| CFG-01..04 | Phase 23 | Pending |
+| SEC-01..03 | Phase 24 | Pending |
+| PRF-01..02 | Phase 24 | Pending |
+| MTF-01..03 | Phase 25 | Pending |
+| TMR-01..03 | Phase 25 | Pending |
+
+**Coverage:** v5.1 requirements: 14 total — no orphans, no double-mapping.

pushframe-5.0.4/.planning/ROADMAP.md

@@ -0,0 +1,105 @@
+# pushframe Roadmap — v5.1 Operations: Config, Sessions, Multi-frame & Scheduling
+
+**Defined:** 2026-09-29
+**Ships when:** a fresh machine goes from `apt install pushframe` to a
+scheduled, unattended, multi-frame Google mirror with **zero** hand-edited
+config files and **zero** stored passwords.
+
+## Milestone Goal
+
+Make pushframe *operable* the way it is *installable*: one conversational
+command (`pushframe config`) to set everything up, password-free sessions
+(token-first), `pushframe schedule` for root-less systemd user timers,
+named album↔frame mappings with per-pair mirror state, and preflights that
+always fail with a remedy.
+
+## Phases
+
+### Phase 23: Config Wizard & Precedence (CFG-01..04)
+
+**Goal**: `pushframe config` replaces env-var archaeology — interactive,
+masked, validated, `0600`; env vars keep working; `show` prints effective
+config with sources; `import` swallows an existing `.env`.
+
+**Success Criteria**:
+
+1. On a fresh machine, `pushframe config` → `pushframe status` works with
+   no env vars set at all (file-only path), verified in a clean container.
+2. With env vars set, they override the file — proven by a test that flips
+   both and asserts which value each command sees.
+3. `config show` never prints a secret value (redaction test); `config
+   import` on a real `.env` reproduces the same effective config as the
+   env-var path (golden diff test).
+
+**Depends on**: nothing (master already carries the google-link preflights
+that started this work).
+
+### Phase 24: Token-First Sessions & Preflight Sweep (SEC-01..03, PRF-01..02)
+
+**Goal**: the password is used once at login and never stored; the token
+drives every subsequent command with transparent re-login on expiry; the
+preflight pattern from google-link covers every command's machine
+prerequisites; no foreseeable condition ends in a traceback.
+
+**Success Criteria**:
+
+1. `pushframe config` + login → `~/.config/pushframe/` contains a token,
+   no password, mode 0600 (file-content test).
+2. A token-expiry simulation (mocked 401) transparently re-logins once and
+   retries the request; a second consecutive failure surfaces the login
+   error (no loops).
+3. The traceback-free sweep passes: every documented foreseeable failure
+   mode maps to a named error with a remedy (parametrized test).
+
+**Depends on**: Phase 23 (config file is where the token lives).
+
+### Phase 25: Multi-frame Mappings & systemd User Scheduling (MTF-01..03, TMR-01..03)
+
+**Goal**: GSF-01 and GSF-02 close — named album↔frame pairs (N:M),
+per-pair mirror state with an account-wide shared write budget, and
+`pushframe schedule` installing systemd **user** timers that run pairs
+unattended (SAFE-02 skips-and-logs, per-job logs, linger documented for
+headless hosts like venus).
+
+**Success Criteria**:
+
+1. Two pairs (one album → two frames) sync in one `--all` run, each with
+   its own manifest/cache shard, the shared budget capping the total, and
+   per-pair reports exact (container + fake-API proof).
+2. `schedule add/list/remove` round-trips units in
+   `~/.config/systemd/user/` (unit-content assertions in a container with
+   systemd available); a scheduled google-sync run is prompt-free and
+   logs to `~/.local/state/pushframe/<job>.log`.
+3. SAFE-02 behavior under scheduling: a pair whose plan exceeds the
+   removal threshold is skipped-and-logged, the unit exits 0, and the
+   other pairs still run.
+
+**Depends on**: Phase 24 (scheduled runs read token sessions, not
+passwords; preflights guard scheduled contexts).
+
+## Progress
+
+**Execution Order:** 23 → 24 → 25
+
+| Phase | Plans Complete | Status | Completed |
+|-------|----------------|--------|-----------|
+| 23. Config Wizard & Precedence | 0/? | Not started | - |
+| 24. Token-First Sessions & Preflight Sweep | 0/? | Not started | - |
+| 25. Multi-frame & systemd User Scheduling | 0/? | Not started | - |
+
+## Requirement Coverage (v5.1)
+
+| Phase | Requirements | Count |
+|-------|--------------|-------|
+| 23 | CFG-01..04 | 4 |
+| 24 | SEC-01..03, PRF-01..02 | 5 |
+| 25 | MTF-01..03, TMR-01..03 | 6 |
+| **Total** | | **15 / 15** |
+
+No orphaned requirements; no requirement mapped to more than one phase.
+
+## Backlog
+
+- Yank 5.0.0 from PyPI (empty-page release, superseded by 5.0.3).
+- OS keyring token storage (Secret Service) as an optional backend.
+- Ubuntu 26 runner observation after 2026-10-19 (deb job toolchain).

pushframe-5.0.4/.planning/STATE.md

@@ -0,0 +1,22 @@
+# pushframe — State
+
+**Milestone:** v5.1 — Operations: Config, Sessions, Multi-frame & Scheduling
+**Started:** 2026-09-29
+
+## Current Position
+
+Phase: 23 — Config Wizard & Precedence
+Current Plan: Not started
+Total Plans in Phase: 0
+Status: Ready to plan
+
+## Milestone Roadmap (v5.1, Phases 23-25)
+
+- [ ] Phase 23 — Config Wizard & Precedence (CFG-01..04)
+- [ ] Phase 24 — Token-First Sessions & Preflight Sweep (SEC-01..03, PRF-01..02)
+- [ ] Phase 25 — Multi-frame Mappings & systemd User Scheduling (MTF-01..03, TMR-01..03)
+
+## Completed Milestones
+
+- v4.0 — Local Google Photos Album Sync (2026-09-29)
+- v5.0 — Distribution & Rename: pushframe packages (2026-09-29)

pushframe-5.0.2/.planning/REQUIREMENTS.md → pushframe-5.0.4/.planning/milestones/v5.0-REQUIREMENTS.md

@@ -1,3 +1,12 @@
+# Requirements Archive: v5.0 v5.0
+
+**Archived:** 2026-09-29
+**Status:** SHIPPED
+
+For current requirements, see `.planning/REQUIREMENTS.md`.
+
+---
+
 # Requirements: Aura Frames Python Client — v5.0 Distribution & Rename: pushframe packages
 
 **Defined:** 2026-09-29

pushframe-5.0.4/.planning/state.json

@@ -0,0 +1,32 @@
+{
+  "contract": "1.0.0",
+  "flavor": "core",
+  "milestone": {
+    "version": "v5.1",
+    "name": "Operations: Config, Sessions, Multi-frame & Scheduling",
+    "started": "2026-09-29"
+  },
+  "phases": [
+    {
+      "number": "23",
+      "name": "Config Wizard & Precedence",
+      "status": "pending"
+    },
+    {
+      "number": "24",
+      "name": "Token-First Sessions & Preflight Sweep",
+      "status": "pending"
+    },
+    {
+      "number": "25",
+      "name": "Multi-frame & systemd User Scheduling",
+      "status": "pending"
+    }
+  ],
+  "next": {
+    "command": "/gsd:progress --next",
+    "label": "Advance to the next step",
+    "reason": "Phase 23 of 3 \u00b7 0% \u00b7 ready to plan"
+  },
+  "updated_at": "2026-09-29T13:27:41.229Z"
+}

pushframe-5.0.4/CHANGELOG.md

@@ -0,0 +1,167 @@
+# Changelog
+
+All notable changes to `pushframe` are documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+Each release ships simultaneously to [PyPI](https://pypi.org/project/pushframe/),
+the [signed APT repository](https://coredmp95.github.io/pushframe/), and
+[GitHub Releases](https://github.com/coredmp95/pushframe/releases) — one tag,
+every channel.
+
+`pushframe` is an unofficial community CLI for Aura Frames digital photo
+frames; it is not affiliated with Aura Frames Inc.
+
+## [5.0.2] — 2026-09-29
+
+### Fixed
+
+- **PyPI project page** — 5.0.0/5.0.1 shipped no package description: the
+  wheel metadata now carries the README (`readme`), a one-line summary with
+  the not-affiliated disclaimer, and Homepage/Repository/Issues URLs.
+- **Release pipeline, APT job** (CI-only, no code change vs 5.0.1): the
+  signing-key fingerprint is derived with gpg instead of a grep over the
+  ASCII armor, and the gh-pages orphan commit runs with an explicit git
+  identity — first release where all five jobs (check, pypi-test, deb,
+  apt, pypi) are green end-to-end.
+- **CI actions** — `actions/checkout@v7`, `astral-sh/setup-uv@v10.2.0`
+  (Node 24): clears the Node.js 20 deprecation warnings on the runners.
+
+## [5.0.1] — 2026-09-29
+
+### Fixed
+
+- Wheel/sdist metadata: `readme = README.md`, `description`, and
+  `project.urls` declared (the 5.0.0 PyPI page rendered empty; versions
+  being immutable on PyPI, the fix ships as a new release).
+
+## [5.0.0] — 2026-09-29
+
+The first distribution release — and the first version published outside
+git tags. Aligns with the v5.0 milestone (« Distribution & Rename »).
+
+### Added
+
+- **Debian packaging** (`scripts/build-deb.sh`): hermetic `.deb` embedding
+  its own CPython 3.14 under `/usr/lib/pushframe/` — no system Python is
+  used or modified; lintian-clean (0 errors, 0 warnings); removal leaves
+  no residue (bytecode is package-owned, `PYTHONDONTWRITEBYTECODE` at run
+  time); verified in clean `ubuntu:26.04` containers.
+- **Signed APT repository** at `https://coredmp95.github.io/pushframe/`
+  (dedicated no-passphrase GPG key, InRelease/Release.gpg, keyring +
+  one-line sources entry), plus container tests proving the full user
+  journey: `apt update` signature-clean → `apt install pushframe` →
+  working CLI.
+- **PyPI distribution** via GitHub Actions **trusted publishing** (OIDC)
+  — no PyPI token exists anywhere; TestPyPI rehearsal gates every real
+  upload.
+- **Release automation** (`release.yml`): pushing a `v*` tag builds the
+  wheel/sdist, the `.deb` (attached to the GitHub Release), republishes
+  the APT repository, and uploads to PyPI — with a version-consistency
+  gate (tag == pyproject == `pushframe.__version__`).
+- **Install journeys as tests**: clean-container proofs for all three
+  channels (`.deb` file, APT, `uv tool install`).
+- `pushframe --version` prints `pushframe <release>` (single-sourced,
+  lockstep-guarded by tests and the release gate).
+
+### Changed
+
+- Project renamed **auraframes → pushframe** (module, binary, config):
+  the old name collided with an existing PyPI package and is
+  trademark-adjacent; config migrates automatically
+  (`~/.config/auraframes/` → `~/.config/pushframe/`, non-destructive).
+- Environment variables: `PUSHFRAME_*` is primary; `AURA_*` still read
+  for one release as a deprecation window.
+
+### Deprecated
+
+- `AURA_*` environment variables (read until 5.x; set `PUSHFRAME_*`).
+- `aura-cli` as an installed command: removed in favor of the single
+  `pushframe` binary.
+
+### Security
+
+- Repository moved to a standalone repo (not a fork); MIT LICENSE with
+  provenance; GitHub security features enabled (secret scanning + push
+  protection, Dependabot, CodeQL).
+
+## Pre-distribution history (git tags only, never published to a package index)
+
+Milestone summary — see `.planning/MILESTONES.md` for the full retros.
+
+- **v4.0 — Local Google Photos Album Sync** (phases 16–19, 2026-09):
+  `google-link` (dedicated Chrome profile, cookie vault `0600`),
+  `google-album` (full walk, exact byte counts), `google-sync`
+  (hide-by-default mirror semantics, pruned cache + persistent manifest,
+  SAFE-01..04 guards); live UAT two-run proof (upload run → zero-upload
+  steady state); debt closeout (AWS config out of code, single logger
+  per process, transport seam).
+- **v3.0 — direct transport rewrite**: `Client` over `httpx` (HTTP/2),
+  boto3 S3/SQS upload path, offline test harness (mocket), full offline
+  suite; the server-side relay approach was abandoned this milestone.
+- **v2.0 — read path hardening**: `status`/`inspect`/`sync`/`push`
+  verbs, asset lifecycle states, anti-abuse paced writes, staged
+  uploads with cleanup on failure.
+- **v1.1 — client transport fixes** (the original author's last tag;
+  revived and extended by the current maintainer in 2026).
+- **v1.0 — initial upstream release** by zmanowar (2023).
+
+## [Unreleased]
+
+- (v5.1 work will land here)
+
+## [5.0.4] — 2026-09-29
+
+### Fixed
+
+- google-link preflight on the uv-tool install path: remedy for a missing
+  playwright now matches every install shape (`uv tool install
+  'pushframe[google-browser]' --force` for uv tools — `pip install
+  --user` targets the wrong interpreter there); stray duplicate quote in
+  the message fixed.
+
+### Added
+
+- google-link zero-config: dedicated Chrome profile defaults to
+  `~/.config/pushframe/chrome-profile` (created on demand); the env var
+  becomes an override. A near-miss env name (e.g. a truncated
+  `USHFRAME_…`) is called out explicitly instead of looking like "unset".
+- google-link preflight: missing prerequisites (playwright package,
+  Chrome/Chromium) fail with the exact remedy instead of a traceback
+  (`ModuleNotFoundError: playwright` was the whole output before).
+
+### Changed
+
+- `PUSHFRAME_PROBE_CHROME_PROFILE` is no longer required to run
+  `google-link`.
+
+- google-link zero-config: the dedicated Chrome profile defaults to
+  `~/.config/pushframe/chrome-profile` (created on demand); the env var
+  becomes an override. A near-miss env name (e.g. a truncated
+  `USHFRAME_…`) is called out explicitly instead of looking like "unset".
+- google-link preflight: missing prerequisites (playwright package,
+  Chrome/Chromium) now fail with the exact remedy instead of a traceback
+  (`ModuleNotFoundError: playwright` was the whole output before).
+
+### Fixed
+
+- `google-link` preflight on the uv-tool install path: the message for a
+  missing playwright package now matches every install shape (`uv tool
+  install 'pushframe[google-browser]'` for uv tools — `pip install
+  --user` targets the wrong interpreter there), and the leftover
+  duplicate browser-detection line was removed.
+
+### Changed
+
+- `PUSHFRAME_PROBE_CHROME_PROFILE` is no longer required to run
+  `google-link`.
+
+## [5.0.3] — 2026-09-29
+
+### Added
+
+- `CHANGELOG.md` — every release now traced in Keep a Changelog format
+  (Added / Changed / Deprecated / Fixed / Security), exposed as a
+  `Changelog` project URL on PyPI and referenced from the README.
+- `arch=amd64` in the documented APT sources entry: silences apt's
+  i386 notice on multi-arch machines (the repo is amd64-only).

{pushframe-5.0.2 → pushframe-5.0.4}/PKG-INFO

@@ -1,10 +1,11 @@
 Metadata-Version: 2.5
 Name: pushframe
-Version: 5.0.2
+Version: 5.0.4
 Summary: Unofficial community CLI for Aura Frames digital photo frames (sync a local folder or a Google Photos album; not affiliated with Aura Frames Inc.)
 Project-URL: Homepage, https://github.com/coredmp95/pushframe
 Project-URL: Repository, https://github.com/coredmp95/pushframe
 Project-URL: Issues, https://github.com/coredmp95/pushframe/issues
+Project-URL: Changelog, https://github.com/coredmp95/pushframe/blob/master/CHANGELOG.md
 License: MIT License
         
         Copyright (c) 2026 Fabrice DIDIERJEAN (coredmp95)
@@ -91,6 +92,9 @@ Any advice or issues are welcome.
   environment, dependency, and interpreter management.
 - A live Aura account (email + password) for any command that actually hits the API.
 
+Release history lives in [CHANGELOG.md](CHANGELOG.md) (Added / Changed /
+Deprecated / Fixed / Security per release, Keep a Changelog format).
+
 ## Install (Ubuntu/Debian)
 
 Pre-built `.deb` packages embed their own Python 3.14 runtime under
@@ -135,8 +139,9 @@ sudo install -d -m 0755 /etc/apt/keyrings
 curl -fsSL https://coredmp95.github.io/pushframe/dists/pushframe.asc \
   | sudo gpg --dearmor -o /etc/apt/keyrings/pushframe.gpg
 
-# 2. add the sources entry
-echo "deb [signed-by=/etc/apt/keyrings/pushframe.gpg] https://coredmp95.github.io/pushframe stable main" \
+# 2. add the sources entry (arch=amd64: the repo is amd64-only — on
+#    multi-arch machines this silences apt's i386 notice)
+echo "deb [arch=amd64 signed-by=/etc/apt/keyrings/pushframe.gpg] https://coredmp95.github.io/pushframe stable main" \
   | sudo tee /etc/apt/sources.list.d/pushframe.list
 
 # 3. install

{pushframe-5.0.2 → pushframe-5.0.4}/README.md

@@ -32,6 +32,9 @@ Any advice or issues are welcome.
   environment, dependency, and interpreter management.
 - A live Aura account (email + password) for any command that actually hits the API.
 
+Release history lives in [CHANGELOG.md](CHANGELOG.md) (Added / Changed /
+Deprecated / Fixed / Security per release, Keep a Changelog format).
+
 ## Install (Ubuntu/Debian)
 
 Pre-built `.deb` packages embed their own Python 3.14 runtime under
@@ -76,8 +79,9 @@ sudo install -d -m 0755 /etc/apt/keyrings
 curl -fsSL https://coredmp95.github.io/pushframe/dists/pushframe.asc \
   | sudo gpg --dearmor -o /etc/apt/keyrings/pushframe.gpg
 
-# 2. add the sources entry
-echo "deb [signed-by=/etc/apt/keyrings/pushframe.gpg] https://coredmp95.github.io/pushframe stable main" \
+# 2. add the sources entry (arch=amd64: the repo is amd64-only — on
+#    multi-arch machines this silences apt's i386 notice)
+echo "deb [arch=amd64 signed-by=/etc/apt/keyrings/pushframe.gpg] https://coredmp95.github.io/pushframe stable main" \
   | sudo tee /etc/apt/sources.list.d/pushframe.list
 
 # 3. install

{pushframe-5.0.2 → pushframe-5.0.4}/pushframe/__init__.py

@@ -1,4 +1,4 @@
 # pushframe — unofficial community CLI for Aura Frames (not affiliated).
 # Version single source for the CLI surface (REL-02); pyproject keeps the
 # packaging metadata version and tests/test_version.py enforces lockstep.
-__version__ = "5.0.2"
+__version__ = "5.0.4"

{pushframe-5.0.2 → pushframe-5.0.4}/pushframe/cli.py

@@ -324,12 +324,10 @@ def run_google_link(*, debug: bool = False, bootstrap_fn=None) -> int:
     """
     _configure_cli_logging(debug)
 
-    if not os.environ.get(PROFILE_ENV_VAR, '').strip():
-        print(f'google-link failed: {PROFILE_ENV_VAR} is unset — the daily-driver '
-              f'profile is structurally unreachable; point the env var at a '
-              f'dedicated Chrome profile directory (e.g. ~/.config/pushframe/'
-              f'chrome-profile) and re-run (T-16-06)')
-        return 1
+    # v5.1: no env prerequisite here — bootstrap._require_profile() owns the
+    # precedence (override > legacy > built-in default, created on demand)
+    # and raises a helpful BootstrapError (near-miss names included) that the
+    # handler below prints verbatim.
 
     # Re-link notice (LGS-02): same command refreshes an existing session.
     # Vault read routes through from_vault (denylist-sanctioned); a dead or