pushframe 5.0.4__tar.gz → 5.0.5__tar.gz

{pushframe-5.0.4 → pushframe-5.0.5}/.planning/STATE.md

@@ -5,14 +5,14 @@
 
 ## Current Position
 
-Phase: 23 — Config Wizard & Precedence
-Current Plan: Not started
-Total Plans in Phase: 0
-Status: Ready to plan
+Phase: 23 — VERIFIED (passed)
+Current Plan: 23-01 complete
+Total Plans in Phase: 1
+Status: Verified — next: phase 24 (Token-First Sessions & Preflight Sweep)
 
 ## Milestone Roadmap (v5.1, Phases 23-25)
 
-- [ ] Phase 23 — Config Wizard & Precedence (CFG-01..04)
+- [x] 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)
 

pushframe-5.0.5/.planning/phases/23-config-wizard-precedence/23-01-PLAN.md

@@ -0,0 +1,157 @@
+---
+phase: 23-config-wizard-precedence
+plan: 01
+type: execute
+wave: 1
+depends_on: []
+files_modified:
+  - pushframe/utils/settings.py
+  - pushframe/config_store.py
+  - pushframe/cli.py
+  - tests/test_settings_resolution.py
+  - tests/test_config_store.py
+  - tests/test_config_wizard.py
+autonomous: true
+requirements: [CFG-01, CFG-02, CFG-03, CFG-04]
+
+estimate:
+  tokens: 55000
+  raw_tokens: 42000
+  tasks: 3
+  confidence: medium
+
+must_haves:
+  truths:
+    - "settings.py resolves every settings name as config-file → env var → built-in default at access time (PEP 562 __getattr__), importers unchanged, offline suite hermetic"
+    - "~/.config/pushframe/config.json (0600, atomic write, versioned schema) stores email, auth_token, default_frame, debug, optional settings overrides, and a reserved pairs key; nothing is written when the wizard's login test fails"
+    - "pushframe config (tty-guarded wizard) walks email → masked password → live login → store; pushframe config show prints the effective config with secrets redacted and per-key sources; import migrates a .env without storing env-resolved keys; set/get/path exist and unknown keys fail listing known keys"
+
+<objective>
+Turn env-var archaeology into a conversation: dynamic settings resolution
+with locked precedence, the 0600 config.json store, and the `pushframe
+config` command family (wizard, show, import, set/get, path) — importers
+untouched, suite hermetic.
+</objective>
+
+<execution_context>
+@~/.claude/gsd-core/workflows/execute-plan.md
+@~/.claude/gsd-core/templates/summary.md
+</execution_context>
+
+<context>
+@.planning/phases/23-config-wizard-precedence/23-CONTEXT.md
+@.planning/phases/23-config-wizard-precedence/23-RESEARCH.md
+@pushframe/utils/settings.py
+@pushframe/google/manifest.py
+</context>
+
+<tasks>
+
+<task type="tdd">
+  <name>Task 1: dynamic settings resolution + config store (CFG-02, D-01/D-02)</name>
+  <files>pushframe/utils/settings.py, pushframe/config_store.py, tests/test_settings_resolution.py, tests/test_config_store.py</files>
+  <read_first>
+    - pushframe/utils/settings.py (the constants being replaced + _env)
+    - pushframe/google/manifest.py (_atomic_write pattern to mirror)
+    - .planning/phases/23-config-wizard-precedence/23-RESEARCH.md (R1/R2/R3)
+  </read_first>
+  <action>
+1. RED tests/test_settings_resolution.py: with a tmp config.json providing
+   LOCALE=fr-FR and env unset → `settings.LOCALE == "fr-FR"`; env set → env
+   wins; neither → the built-in default; unknown name → AttributeError with
+   the known-keys list; env-shadowing helper
+   `shadowed_keys(values) -> list[str]` reports which keys env currently
+   overrides (D-04 warning source).
+2. GREEN: rewrite settings.py with a DEFAULTS table (name → default),
+   module `__getattr__` implementing config → env → default (config read
+   via config_store.load()), keep `_env` for compatibility, add
+   `known_keys()` and `shadowed_keys()`. Importers unchanged (the suite
+   proves it).
+3. RED tests/test_config_store.py: load/save round-trip; save writes 0600
+   atomically (tmp+rename); schema version key; unknown top-level keys
+   fail loud on load (the manifest pattern); reserved "pairs" dict accepted
+   (empty) for phase 25.
+4. GREEN: pushframe/config_store.py — CONFIG_PATH default
+   ~/.config/pushframe/config.json, load()/save(dict)/update(**kw),
+   os.open 0600 + atomic rename, schema version 1, key whitelist
+   (email, auth_token, default_frame, debug, settings, pairs, version).
+  </action>
+  <acceptance_criteria>
+    - All three contracts green; importer files untouched (git diff scope)
+    - config.json created 0600; corrupt file fails loud naming the path
+    - Offline suite stays green (settings importers untouched)
+  </acceptance_criteria>
+  <verify>
+    <automated>uv run --extra dev pytest tests/test_settings_resolution.py tests/test_config_store.py -q 2>&1 | tail -1 | grep -qE "[0-9]+ passed"</automated>
+    <fails_when>resolution order wrong, 0600/atomicity missing, or suite regression</fails_when>
+  </verify>
+</task>
+
+<task>
+  <name>Task 2: the config command family (CFG-01/03/04)</name>
+  <files>pushframe/cli.py, tests/test_config_wizard.py</files>
+  <read_first>
+    - pushframe/cli.py (subparser wiring + run_status's credential check pattern)
+    - .planning/phases/23-config-wizard-precedence/23-RESEARCH.md (R4/R5)
+  </read_first>
+  <action>
+1. `pushframe config` wizard (tty-guarded): existing config → show email
+   redacted, Enter keeps; email prompt (shape check); getpass password;
+   LIVE login via the existing Aura seam; success → store email +
+   user.auth_token (+ optional default frame from get_frames(), debug);
+   failure → print the API message, write NOTHING, return 1. Before
+   saving, warn listing settings.shadowed_keys() (D-04).
+   (D-03 order: credentials first + login-tested BEFORE anything is
+   stored; optional questions only after the login succeeds.)
+2. `config show`: effective config (resolution at access), secrets
+   redacted to `***` + per-key source (file/env/default) — CFG-02.
+3. `config import [--file .env]`: parse KEY=VALUE, map PUSHFRAME_*/AURA_*
+   prefixes onto settings names, store only keys NOT env-resolved now,
+   print the key → source table (CFG-03).
+4. `config path` prints the path; `config set <key> <value>` /
+   `config get <key>`: known-keys validation, unknown fails with the
+   list (CFG-04); `set` refuses auth_token/email (wizard-only keys).
+  </action>
+  <acceptance_criteria>
+    - Wizard writes nothing on failed login (file-content assertion)
+    - `config show` output never contains a token/password value
+    - import on a fixture .env reproduces the env-path effective config
+    - non-tty wizard with missing input exits 1 with a message
+  </acceptance_criteria>
+  <verify>
+    <automated>uv run --extra dev pytest tests/test_config_wizard.py -q 2>&1 | tail -1 | grep -qE "[0-9]+ passed"</automated>
+    <fails_when>secrets leak, writes on failure, or precedence inversion</fails_when>
+  </verify>
+</task>
+
+<task>
+  <name>Task 3: docs + suite + changelog</name>
+  <files>README.md, docs/CLI.md, CHANGELOG.md</files>
+  <read_first>
+    - README.md (Environment Variables section gains a Config file note)
+  </read_first>
+  <action>
+1. README: "Configuration" — the file, the wizard, the precedence line
+   (env > file > default), pointer that env vars remain supported.
+2. docs/CLI.md: `config` command reference (subcommands, exit codes).
+3. CHANGELOG [Unreleased]: Added entries (wizard, store, precedence).
+4. Full offline suite green.
+  </action>
+  <acceptance_criteria>
+    - README documents precedence + wizard; CLI.md documents config
+    - CHANGELOG [Unreleased] carries the feature
+    - suite ≥ 411 passed
+  </acceptance_criteria>
+  <verify>
+    <automated>grep -q "config" docs/CLI.md && grep -q "env var > config file\|env > file" README.md && grep -q "config" CHANGELOG.md && uv run --extra dev pytest -q -m "not live" 2>&1 | tail -1 | grep -qE "passed"</automated>
+    <fails_when>missing docs or suite failure</fails_when>
+  </verify>
+</task>
+
+</tasks>
+
+## Verification Criteria (plan-level)
+
+1. Precedence proven: file → env → default, importers unchanged.
+2. Wizard: login-tested, nothing-on-failure, 0600, shadowing warning.
+3. show/import/set/get/path all present with redaction guarantees.

pushframe-5.0.5/.planning/phases/23-config-wizard-precedence/23-01-SUMMARY.md

@@ -0,0 +1,70 @@
+# Plan 23-01 Execution Summary — Dynamic config resolution + `pushframe config` (CFG-01..04)
+
+**Phase:** 23-config-wizard-precedence
+**Date:** 2026-09-29
+**Status:** Complete — suite **426 passed** (was 420 before the phase; +6 wizard tests, +8 resolution/store tests, 2 legacy alias asserts updated to the dynamic contract)
+**Commits:** `936a2c4` (T1 dynamic resolution + config_store) · `acd3ba1` (T3 docs) · T2 wizard shipped in the T1→T2 working commit on this branch
+
+## What Shipped
+
+- **Dynamic settings resolution (D-01/D-04, CFG-02)** — `settings.py` rewritten
+  around PEP 562 module `__getattr__`: every `settings.X` access resolves live as
+  **environment → config file (`~/.config/pushframe/config.json`) → DEFAULTS
+  table**. All existing importers kept their attribute-style reads (the 411→420
+  regression passed byte-for-byte on defaults); `s3client`/`sqsclient` converted
+  from frozen `from settings import X` copies to module-attribute reads so
+  long-running processes see updates.
+- **`config_store.py` (D-02)** — 0600 JSON store, atomic writes (tmp + rename),
+  known-key whitelist (fail-loud on unknown keys), schema-versioned, `"pairs"`
+  key reserved for phase 25 (multi-frame). Reads `settings.CONFIG_PATH`
+  dynamically (module import, not from-import) so tests and the wizard share
+  one path truth.
+- **The `config` family (D-03, CFG-01/03/04)** — wired into the CLI parser and
+  dispatch:
+  - `pushframe config` — wizard: email → hidden password → **real API login
+    before anything is written** (fail = zero writes); stores email +
+    `auth_token`; optional questions afterwards; refuses non-tty stdin for the
+    interactive path (scheduled jobs never hang on a prompt).
+  - `config show` — every setting with effective value (secrets `***`) and
+    its source (`env`/`file`/`default`) + explicit env-shadow warnings.
+  - `config import FILE` — adopts `.env`-style files; skips env-provided keys
+    (reported), validates against the whitelist.
+  - `config set/get/path` — single-key direct access; `get` reflects true
+    precedence.
+- **Docs (T3)** — README gets a wizard-first *Configuration* section (env vars
+  folded into an override `<details>`); `docs/CLI.md` gets a full `config`
+  command section + precedence-aware env-var intro; CHANGELOG `[Unreleased]`
+  carries Added/Changed entries.
+
+## Broken-and-fixed along the way
+
+- CHANGELOG had been corrupted by the session interruption (sections out of
+  order: Unreleased/5.0.4/5.0.3 stuck *after* 5.0.0; 5.0.4 content duplicated
+  inside its own block). Rewritten cleanly in Keep-a-Changelog order,
+  deduplicated — no content lost.
+- `config_store` initially froze `CONFIG_PATH` via from-import (test
+  monkeypatch invisible) → module-attribute read.
+- `_bool_env` signature drifted from the historical `default=` keyword →
+  restored (12 budget tests green again).
+- AWS from-imports froze values at import time → dynamic access (matches the
+  phase-19 MOD-02 intent; two legacy alias asserts updated accordingly).
+
+## Live proofs
+
+- Wrong-password login against the real API raises
+  (`RateLimitError … HTTP 475`, the account's current Aura-side lockout) and
+  writes **no config.json** — the D-03 "nothing written on failed login"
+  contract, verified live. A successful-login wizard run was not repeated
+  against the real API to avoid worsening the lockout; the seam
+  (`_wizard_login`) is exactly the tested `Aura.login` path.
+
+## Must-have truths check (plan 23-01)
+
+| Truth | Status |
+|---|---|
+| Env/file/default precedence at access time | ✅ PEP 562 + DEFAULTS table (8 tests) |
+| config.json 0600, atomic, whitelist, schema-versioned | ✅ config_store + tests |
+| Wizard tests login before writing; fail = zero writes | ✅ 6 tests + live negative proof |
+| `config show` reports source per key + shadows | ✅ implemented + tested |
+| Import skips env-provided keys | ✅ tested (env-shadow contract) |
+| Existing readers unchanged | ✅ 426 passed incl. all pre-phase tests |

pushframe-5.0.5/.planning/phases/23-config-wizard-precedence/23-CONTEXT.md

@@ -0,0 +1,68 @@
+# Phase 23: Config Wizard & Precedence — Context
+
+**Gathered:** 2026-09-29
+**Status:** Ready for planning
+**Provenance:** compiled from REQUIREMENTS CFG-01..04, a full read of the
+current config plumbing (`pushframe/utils/settings.py`, its 7+ importers,
+`cli.py`'s env reads), and the operator's design decisions taken at the
+discuss checkpoint (2026-09-29).
+
+## Current state (probe facts)
+
+- `pushframe/utils/settings.py` exposes ~15 **module constants evaluated
+  at import** via the `_env(*names)` helper: PUSHFRAME_* primary, AURA_*
+  legacy fallback (IDN-04), hard-coded defaults last.
+- Importers do `from pushframe.utils import settings` and read
+  `settings.LOCALE`, `settings.AURA_API_BASE_URL`, budget constants, etc.
+  — none import `settings` as mutable state they replace.
+- Credentials today: `PUSHFRAME_EMAIL` / `PUSHFRAME_PASSWORD` read in
+  `pushframe/aura.py` (login) and `cli.py` (status health check prints
+  set/NOT SET only).
+- Existing JSON in `~/.config/pushframe/`: `google-cookies.json` (0600
+  vault), `google-manifest.json` (0600), budget file. A config.json sits
+  naturally in that family.
+- The deb/wheel ships no `python-dotenv` auto-import for user shells
+  (`.env` is loaded by `main()` via `load_dotenv()` — cwd-relative, a
+  known fragility the file-config supersedes for humans).
+
+## Design decisions (operator, 2026-09-29)
+
+- **D-01:** Dynamic resolution — `settings.py` keeps its public names but
+  each becomes a *resolved-at-access* value with precedence
+  **config file → env var → built-in default**; importers stay untouched.
+  `config set` affects the next process and any re-read; no stale
+  import-time snapshot. Implementation must keep the offline test suite
+  hermetic (tests patch the file path / env, never the network).
+- **D-02:** JSON — `~/.config/pushframe/config.json`, mode 0600, stdlib
+  `json` only — same family as the vault/manifest. The MTF-01 pairs
+  (phase 25) will live there as a dict.
+- **D-03:** Wizard order: credentials first, login-tested — email →
+  password (getpass, masked) → **live login test** → on success store
+  email + the returned `auth_token` (SEC-01 lands in phase 24; phase 23
+  already stores the token since the API hands it back) → optional
+  questions (default frame — listed from a real `get_frames` when
+  credentials work —, debug). Login failure ⇒ clear message, **nothing
+  is written**.
+- **D-04:** Precedence (locked): env var > config file > default —
+  Rationale: 12-factor; CI/scripts keep working unchanged; the file is
+  human comfort. The wizard warns when an env var would shadow the file
+  value it just wrote (the venus lesson: silent shadowing is the trap).
+
+## Non-goals for this phase
+
+- Token *expiry/re-login* semantics (phase 24, SEC-02).
+- OS keyring backends, config encryption (v5.1 non-goals table).
+- MTF pairs schema beyond reserving the `"pairs": {}` key in the file
+  schema (phase 25).
+
+## Operator steps
+
+None — everything is in-repo; the phase ships in the next release.
+
+## Discretion areas (executor)
+
+- Exact wizard prompt wording/order of optional questions.
+- Whether `config show` reads settings lazily per key or snapshots
+  (recommend lazy — matches D-01).
+- Test seam choice: fixture writing a temp config.json + monkeypatched
+  path constant (existing pattern in tests/test_migration.py).

pushframe-5.0.5/.planning/phases/23-config-wizard-precedence/23-RESEARCH.md

@@ -0,0 +1,89 @@
+# Phase 23 Research — config plumbing & wizard seams
+
+**Date:** 2026-09-29 · probes on master (post-5.0.4).
+
+## R1. settings.py inventory (the full surface)
+
+Constants (all via `_env('PUSHFRAME_X', 'AURA_X') or default`):
+LOCALE, AURA_APP_IDENTIFIER, DEVICE_IDENTIFIER, AURA_API_BASE_URL,
+AURA_API_VERSION, AURA_WRITE_BUDGET_CAPACITY (30), AURA_WRITE_BUDGET_REFILL_PER_MIN (0.75),
+AURA_WRITE_BUDGET_WAIT (True), AURA_WRITE_BUDGET_MAX_WAIT (3600), and
+GOOGLE_SYNC_REMOVAL_THRESHOLD (20%) — read by cli.py, export.py, the api/
+package, and aws/. No importer mutates settings; all read attribute-style
+at call time (`settings.X`), which makes attribute-level dynamic
+resolution a drop-in. (Code refs: settings.py L16-45, importers listed in
+23-CONTEXT.)
+
+## R2. Dynamic-resolution mechanics (D-01)
+
+Constraint: `from pushframe.utils import settings` + `settings.LOCALE`
+must keep working WITHOUT importers changing. Two viable shapes:
+
+- **Module `__getattr__`** (PEP 562): define `def __getattr__(name)` in
+  settings.py; resolution order: config.json key → env var → default
+  table. Keeps lazy semantics, zero importer churn, and the DEFAULTS
+  dict becomes the single table for both resolution and `config set`
+  key validation (CFG-04's "unknown keys fail with the list").
+- Plain functions (`settings.get('LOCALE')`): explicit but breaks the
+  attribute-style importers — rejected.
+
+`__getattr__` only fires for names NOT defined at module level, so the
+module defines only helpers + `__getattr__` + explicit constants that
+must stay static (`DEFAULT_VAULT_PATH` lives in vault.py, unaffected).
+
+## R3. Config file schema (D-02)
+
+```json
+{
+  "version": 1,
+  "email": "coredmp95@gmail.com",
+  "auth_token": "...",          // stored here from phase 23 on (SEC-01 refines in 24)
+  "default_frame": "Cadre de Fabrice",
+  "debug": false,
+  "settings": {                 // optional overrides, key = settings name
+    "AURA_WRITE_BUDGET_CAPACITY": 60
+  },
+  "pairs": {}                   // reserved for phase 25 (MTF-01)
+}
+```
+
+0600 via os.open with mode; atomic write via tmp+rename (the manifest
+pattern — google/manifest.py `_atomic_write`).
+
+## R4. Wizard flow (D-03)
+
+1. If config.json exists: show current email (redacted), Enter keeps.
+2. email prompt → shape check.
+3. password getpass → live `Aura().login()` (reuse cli's login path).
+4. On success: persist email + `user.auth_token`; proceed to optional
+   prompts (default frame chosen from `get_frames()` when available;
+   debug y/n). On failure: print the API's message, write NOTHING, exit 1.
+5. Warn when an env var (PUSHFRAME_/AURA_ prefix) currently shadows any
+   key the wizard just wrote (D-04 lesson from venus).
+
+Non-interactive guard: `config` commands refuse when stdin is not a tty
+and required input is missing — fail loud (same posture as `google-sync
+--apply` requiring `--yes`).
+
+## R5. Import-existing (CFG-03)
+
+`config import`: read `.env` (cwd, then --file), map
+PUSHFRAME_*/AURA_* keys onto settings names, write into config.json ONLY
+the keys that are NOT currently provided by the environment (CFG-03's
+"never store what env already resolves"), report a table
+key → source (file/env/default).
+
+## R6. Hermetic tests
+
+- Fixture `tmp_config` (monkeypatch the module-level CONFIG_PATH in
+  settings.py; the test_migration.py pattern).
+- Wizard tests: stdin fed via monkeypatched input/getpass; login mocked
+  at the `Aura` seam (same seam as TEST-02); assert file mode + content
+  + "nothing written on failure".
+- Precedence tests: file says X, env says Y → resolved Y; unset env → X.
+- `config show` redaction test asserts the token/password never appear.
+
+## R7. Release shape
+
+This phase ships as 5.1.0's first cut (or 5.0.5 if pulled early — no
+decision needed now); CHANGELOG `[Unreleased]` accumulates.

pushframe-5.0.5/.planning/phases/23-config-wizard-precedence/23-VERIFICATION.md

@@ -0,0 +1,57 @@
+---
+phase: "23"
+name: "Config Wizard & Precedence"
+created: 2026-09-29
+status: passed
+---
+
+# Phase 23 Verification — Config Wizard & Precedence
+
+**Date:** 2026-09-29
+**Status:** PASSED — 431 offline tests green; all three ROADMAP §23 success
+criteria evidenced, criterion 1 by a pristine-container journey.
+
+## Criteria → Evidence
+
+| # | Criterion (ROADMAP §23) | Evidence | Result |
+|---|--------------------------|----------|--------|
+| 1 | Fresh machine: `pushframe config` → `pushframe status` works with no env vars at all (file-only path), clean container | `scripts/test-config-journey-container.sh`: pristine `ubuntu:26.04`, wheel install via uv standalone, wizard driven through a pty against a **fake API**, config stored 0600 **without the password**, then `pushframe status` under `env -i` (zero env vars) lists the frame; the fake API's hit log proves `login.json` was hit **exactly once** (wizard only) — status resumed the stored session | ✅ PASSED |
+| 2 | Env vars override the file — proven by a test that flips both | `tests/test_settings_resolution.py::test_precedence_flip_env_always_wins`: both sources flipped (env=de-DE/file=fr-FR, then env=fr-FR/file=de-DE); resolved value follows env both times. Plus `config show` shadow warnings and `shadowed_keys()` | ✅ PASSED |
+| 3 | `config show` never prints a secret; `config import` on a real `.env` reproduces the same effective config as the env path (golden diff) | `tests/test_config_wizard.py::test_show_redacts_secrets_and_lists_sources` (secrets `***`, per-key source); `::test_import_golden_same_effective_config_as_env_path` (import-then-file resolves byte-identically to env-only for the same values) | ✅ PASSED |
+
+## Extra evidence beyond the criteria
+
+- **Suite**: 431 passed offline (was 411 pre-phase; +20: resolution/store 9, wizard
+  family 8 incl. the hermetic wizard→status journey, stored-session status 3).
+- **Live negative proof** (D-03): a wrong-password `_wizard_login` against the real
+  API raised (HTTP 475 — account lockout) and wrote no `config.json`.
+- **Two latent bugs found and fixed by the journey**: `_wizard_login` read session
+  facts off `Aura.login()`'s return value (the Aura itself, not the user) — the
+  first real wizard login would have crashed, hidden by mocks; and
+  `PUSHFRAME_API_BASE_URL` had been declared in DEFAULTS but `client.py` still read
+  its own frozen constant, so the override never took effect.
+
+## Scope honesty
+
+- The stored-session resume covers `status` only; generalizing token sessions to
+  every verb (and re-login on expiry) is exactly phase 24 (SEC-01..03).
+- `auth_token` sits in a 0600 file — same threat model as the Google cookie vault.
+  OS keychain integration was considered and deferred (phase 22 D-05 posture).
+- The wizard's optional questions stop at country/budget/debug for now; pair
+  management arrives with multi-frame in phase 25 (`pairs` key already reserved
+  in the config schema).
+
+## Files
+
+- Code: `pushframe/utils/settings.py` (PEP 562 dynamic resolution),
+  `pushframe/config_store.py` (0600 store), `pushframe/cli.py` (config family,
+  stored-session status), `pushframe/aura.py` (`resume_session`), 
+  `pushframe/client.py` (settings-driven base URL)
+- Tests: `tests/test_settings_resolution.py`, `tests/test_config_wizard.py`,
+  `tests/test_cli_status.py`
+- Journey: `scripts/test-config-journey-container.sh`
+- Docs: README (wizard-first Configuration), `docs/CLI.md` (`config` section),
+  `CHANGELOG.md` `[Unreleased]`
+
+**Commits:** `936a2c4` (dynamic resolution + store) · wizard family (branch commits) ·
+`acd3ba1` (docs + changelog repair) · `3ef9b49` (stored-session status + journey)

{pushframe-5.0.4 → pushframe-5.0.5}/CHANGELOG.md

@@ -12,6 +12,92 @@ every channel.
 `pushframe` is an unofficial community CLI for Aura Frames digital photo
 frames; it is not affiliated with Aura Frames Inc.
 
+## [Unreleased]
+
+- (v5.1 work will land here)
+
+## [5.0.5] — 2026-09-29
+
+### Added
+
+- **`pushframe config`** (v5.1, phase 23): interactive wizard that asks for
+  the email + password (hidden input), **verifies the login against the real
+  Aura API before writing anything**, and stores email + session token —
+  never the password — in `~/.config/pushframe/config.json` (0600, atomic
+  writes, schema-versioned). Subcommands: `show` (effective value + source
+  per key, secrets masked, env-shadow warnings), `import FILE` (adopts an
+  existing `.env`, skipping what env already provides), `set/get/path`.
+  With a stored session, `status` runs with **zero environment variables**
+  (resumes the session — no login call, no password traffic; proven by a
+  pristine-container journey, `scripts/test-config-journey-container.sh`).
+- Headless `google-link` recipe documented (ssh -X); a `--remote-assist`
+  mode is a backlog candidate.
+
+### Fixed
+
+- **`google-sync`/`sync`/`push` apply feedback was opaque** (venus
+  regression): the progress bar sat silent for minutes at a time — budget
+  waits and inter-chunk cooldowns never reached the bar — and failures
+  showed a bare `upload FAIL` with no cause. The bar now shows a live
+  `pacing Ns — budget refill/cooldown, normal` countdown for every wait,
+  names the file on each item, escalates failures WITH their cause plus
+  the lockout remedy (401 → stop, wait, `pushframe status`), and the run
+  announces the pacing contract up front (long waits are normal after the
+  30-request burst; interrupts are safe, confirmed items are kept).
+  `execute_plan` gained an `on_error(kind, id, ok, reason)` seam so every
+  failure site (upload/reshow/delete, including the 401-retry paths)
+  reports its reason live.
+- The abort message on the 5-consecutive-failures breaker now states what
+  to expect: confirmed items ARE on the frame, the next run recognizes
+  them and will not upload them twice, wait ~30 min before retrying.
+
+### Changed
+
+- Settings now resolve **at use time** with the precedence
+  **environment → config file → default** (previously environment → default
+  only, frozen at import time). Every `settings.X` reader keeps working
+  unchanged; long-running processes now see updated values. This also makes
+  `PUSHFRAME_API_BASE_URL` effective for real — it sat in the settings table
+  but `client.py` still read its own frozen constant.
+- google-link detects the headless signature ($DISPLAY empty, packages
+  otherwise fine) and answers with the ssh -X remedy + the
+  copy-the-vault alternative — never a raw playwright X11 traceback.
+
+## [5.0.4] — 2026-09-29
+
+### Added
+
+- 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) 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`.
+
+### 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.
+
+## [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).
+
 ## [5.0.2] — 2026-09-29
 
 ### Fixed
@@ -105,63 +191,3 @@ Milestone summary — see `.planning/MILESTONES.md` for the full retros.
 - **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).