pushary 1.9.53 → 1.9.55

package/CHANGELOG.md

@@ -1,5 +1,17 @@
 # Changelog
 
+## 1.9.55
+
+- The setup test now says how to answer it. When the Pushary phone app is connected, setup prints the step for that phone: "Press and hold the notification, then tap Approve." on iPhone, "Expand the notification, then tap Approve." on Android. It then waits with "Waiting for your answer". The buttons on the notification answer the question on every version of the app; on Android the button asks you to unlock the phone first. A plain tap opens the app, and during the app's first run that showed "Connect your computer" in place of the question, so the test went unanswered.
+- `pushary doctor --roundtrip` prints the same step, so the command setup points to no longer gives different advice.
+- When nothing comes back, setup says to send another test and then gives the step for that phone, in that order, because the first notification has been withdrawn by then. A browser connection keeps the earlier wording.
+- The test question no longer says "Tap Yes or No". The buttons are named Approve and Deny in the phone app and Yes and No elsewhere, so it now reads "Answer either way".
+- A setup test stopped with Ctrl-C while it waits for the answer is now reported. Setup records the interrupt, the step it stopped at (`answer-test`), the agents it had configured and that the notification was delivered, before it exits. `--json` prints its one result object for that exit too. Before this release that exit reported nothing, so a test somebody gave up on left no record.
+
+## 1.9.54
+
+- For a switch the Pushary Mac app turns on, the login item that keeps Codex app cards on after a restart now runs Pushary's own program and not a shell line, so macOS treats it as part of Pushary and not as a separate `sh` item. A switch turned on with `pushary codex --app-cards on` keeps the login item it has, unchanged.
+
 ## 1.9.53
 
 - `pushary codex --app-cards status --json` prints the switch's state as one line of JSON for a program to read: the state, the Codex app found on this Mac, whether the Mac app turned the switch on, and whether it was turned off on purpose. The Pushary Mac app uses it for its new Settings switch, which is on by default there.
@@ -25,7 +37,7 @@
 - New, off by default: `pushary codex --app-cards on` makes the Codex app start through the same pass-through every time you open it, including after a restart, with no terminal to keep open. `pushary codex --app-cards off` undoes it and `status` says where it stands, including when Pushary or the Codex engine is no longer where the launcher expects. It writes a launcher under `~/.pushary/codex-app`, a login item, and the `CODEX_CLI_PATH` setting for your login session, and leaves that setting alone if another program already owns it. `off` replaces the launcher with one that only runs Codex's engine and leaves that file in place, because the Codex app records its path in `~/.codex/config.toml` and an open Codex keeps using it; `pushary clean` removes it, after which Codex should be reopened.
 - The launcher steps aside by itself: it hands every engine command except the app's own protocol straight to Codex's engine, starts the engine itself when Pushary is missing, broken, never starts it, or the launcher cannot write beside itself, and turns its own setting off if a Codex update moves the engine. If the launcher is stopped, Pushary stops the engine within a few seconds.
 - The pass-through holds at most 64 KiB of the app's input and inspects at most 256 KiB of a line from the engine, loads the code that talks to Pushary only when a card appears, does nothing while idle except check every two seconds that its launcher is still running, lets the engine finish its own shutdown when Codex quits, and keeps copying if anything in it fails. The first time Computer Use asks in a way this version does not know, it says so once in Codex's own log.
-- Setup: a Mac that has the Codex app and no Codex CLI gets native hooks again. The current Codex app keeps its engine behind a small script with its version in a file beside it; setup looked for the version inside the script, found none, and treated Codex as too old for hooks. Setup now reads that file, finds the engine where the app keeps it now, and never takes Pushary's own launcher for Codex.
+- Setup on a Mac that has the Codex app and no Codex CLI: setup never takes Pushary's own launcher for Codex, and it finds the app's engine where the current Codex app keeps it when Codex's settings file does not name one. Before, the first would have skipped native hooks and the second reported Codex as not found. Correction: this entry first said such a Mac got no hooks at all since the Codex app changed its layout. That was wrong. When Codex's settings file names the app's own engine, as it does after Codex has started normally, setup already found it and installed hooks.
 - `pushary codex` is experimental and no longer appears in `pushary --help`. It still runs when typed, and `pushary codex --help` describes it.
 
 ## 1.9.50