booking-agent-cli 0.5.0__tar.gz → 0.7.0__tar.gz

{booking_agent_cli-0.5.0 → booking_agent_cli-0.7.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: booking-agent-cli
-Version: 0.5.0
+Version: 0.7.0
 Summary: The Booking Agent CLI: a stateful USP booking flow with hard gates, plus its USP protocol library.
 Project-URL: Homepage, https://github.com/wix/booking-agent
 Project-URL: Documentation, https://github.com/wix/booking-agent/blob/master/booking-agent/README.md
@@ -78,7 +78,7 @@ Each release also publishes that skill at an immutable `skill-v<version>` tag an
 the release workflow, so a harness can pin and verify the exact text it follows:
 
 ```bash
-curl -fsSLO https://raw.githubusercontent.com/wix/booking-agent/skill-v0.53.0/booking-agent/skills/booking-agent/SKILL.md
+curl -fsSLO https://raw.githubusercontent.com/wix/booking-agent/skill-v0.55.0/booking-agent/skills/booking-agent/SKILL.md
 gh attestation verify SKILL.md --repo wix/booking-agent \
   --signer-workflow wix/booking-agent/.github/workflows/release.yml
 ```

{booking_agent_cli-0.5.0 → booking_agent_cli-0.7.0}/README.md

@@ -36,7 +36,7 @@ Each release also publishes that skill at an immutable `skill-v<version>` tag an
 the release workflow, so a harness can pin and verify the exact text it follows:
 
 ```bash
-curl -fsSLO https://raw.githubusercontent.com/wix/booking-agent/skill-v0.53.0/booking-agent/skills/booking-agent/SKILL.md
+curl -fsSLO https://raw.githubusercontent.com/wix/booking-agent/skill-v0.55.0/booking-agent/skills/booking-agent/SKILL.md
 gh attestation verify SKILL.md --repo wix/booking-agent \
   --signer-workflow wix/booking-agent/.github/workflows/release.yml
 ```

{booking_agent_cli-0.5.0 → booking_agent_cli-0.7.0}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "booking-agent-cli"
-version = "0.5.0"
+version = "0.7.0"
 description = "The Booking Agent CLI: a stateful USP booking flow with hard gates, plus its USP protocol library."
 readme = "README.md"
 license = "Apache-2.0"

{booking_agent_cli-0.5.0 → booking_agent_cli-0.7.0}/src/booking_agent/__init__.py

@@ -3,4 +3,4 @@
 Ships in the booking-agent-cli wheel and never imports ``booking_agent_cli``.
 """
 
-__version__ = "0.5.0"
+__version__ = "0.7.0"

{booking_agent_cli-0.5.0 → booking_agent_cli-0.7.0}/src/booking_agent/defaults.env

@@ -14,6 +14,12 @@ USP_PLATFORM_CONTACT=support@booking-agent.dev
 # Sessions, tokens, and traces. Holds the user .env, so override it only in the
 # process environment.
 BOOKING_AGENT_SESSION_DIR=~/.booking-agent
+# Absolute folder a host keeps between runs. When set, booking-agent links its state and the
+# Link sign-in into it by itself before every command.
+# BOOKING_AGENT_PERSISTENT_ROOT=
+# Set to `none` by a host that keeps this runtime's files between conversations itself, so
+# `flow init` does not ask the agent how state is kept.
+# BOOKING_AGENT_PERSISTENCE=
 BOOKING_AGENT_MAX_SESSIONS=30
 LINK_CLI_BIN=link-cli
 

{booking_agent_cli-0.5.0 → booking_agent_cli-0.7.0}/src/booking_agent_cli/__init__.py

@@ -1,3 +1,3 @@
 """booking_agent_cli: typer-based stateful CLI for USP booking flows."""
 
-__version__ = "0.5.0"
+__version__ = "0.7.0"

{booking_agent_cli-0.5.0 → booking_agent_cli-0.7.0}/src/booking_agent_cli/bundled_skill.md

@@ -1,5 +1,5 @@
 ---
-version: 0.53.0
+version: 0.55.0
 name: booking-agent
 description: |
   Books time-based services via USP from a Link wallet. Use when the user wants to book, schedule, reserve, or pay for a service from a business (haircut, lesson, repair, class, appointment, consult). The `booking-agent` CLI owns the booking state machine and refuses to proceed when human gates are skipped. Sign the user in to Link on your own, right after install and at the start of every booking (`booking-agent flow link-auth connect`, then start `booking-agent flow link-auth poll` in the background and post the sign-in URL in the same turn, exactly like `pay poll`); never wait for the user to ask to sign in or to say they approved. After `booking-agent flow business use`, follow `next_command` through `use-ucp-checkout-mode`; businesses without native checkout fail closed. Payment uses `booking-agent flow pay request` (default returns immediately with the approval URL), then start `booking-agent flow pay poll` in the background and post the approval URL to the user in the same turn; the poll finishes checkout once they approve. Confirm through `booking-agent flow book poll --wait`; never start an inbound webhook. Surface the approval URL exactly once. Personal identification (name, phone, email, address) must always come from the user's Link account via `link-cli`, never from chat or placeholders. Before any location-based search, the CLI proposes the Link shipping address and the user confirms it or gives another; online services skip this. Talk to the user in plain everyday language only; never expose CLI, UCP, auth, session, or other implementation details unless they explicitly ask.
@@ -19,7 +19,7 @@ metadata:
         - link-cli
     install:
       - kind: uv
-        package: "booking-agent-cli==0.5.0"
+        package: "booking-agent-cli==0.7.0"
         bins: [booking-agent]
 user-invocable: true
 ---
@@ -220,7 +220,7 @@ To take a fixed, published version instead of the latest, fetch it at the releas
 workflow signs it under, and check the signature before you follow it:
 
 ```bash
-curl -fsSLO https://raw.githubusercontent.com/wix/booking-agent/skill-v0.53.0/booking-agent/skills/booking-agent/SKILL.md
+curl -fsSLO https://raw.githubusercontent.com/wix/booking-agent/skill-v0.55.0/booking-agent/skills/booking-agent/SKILL.md
 gh attestation verify SKILL.md \
   --repo wix/booking-agent \
   --signer-workflow wix/booking-agent/.github/workflows/release.yml
@@ -245,17 +245,17 @@ before installing:
 
 ```bash
 dir="$HOME/.booking-agent/verified-wheels"
-uvx pip download "booking-agent-cli==0.5.0" --no-deps --only-binary :all: -d "$dir"
+uvx pip download "booking-agent-cli==0.7.0" --no-deps --only-binary :all: -d "$dir"
 uvx pypi-attestations==0.0.30 verify pypi --repository https://github.com/wix/booking-agent \
-  "$dir/booking_agent_cli-0.5.0-py3-none-any.whl"
-uv tool install --force "$dir/booking_agent_cli-0.5.0-py3-none-any.whl"
+  "$dir/booking_agent_cli-0.7.0-py3-none-any.whl"
+uv tool install --force "$dir/booking_agent_cli-0.7.0-py3-none-any.whl"
 
 booking-agent --help
 ```
 
 Install only the wheel whose verify step passed, never one that failed it. If `uvx` is not
-available, install the same pinned release with `uv tool install booking-agent-cli==0.5.0` or
-`pipx install booking-agent-cli==0.5.0`; the CLI checks its own files against the signed release
+available, install the same pinned release with `uv tool install booking-agent-cli==0.7.0` or
+`pipx install booking-agent-cli==0.7.0`; the CLI checks its own files against the signed release
 on the first `booking-agent flow init` and refuses to book or pay if they do not match.
 
 Harnesses that read the `install` block in this skill's metadata do this for you. Do not go on
@@ -275,22 +275,21 @@ npm install -g @stripe/link-cli
 
 ### After installing
 
-**Keep state between conversations (only when this runtime needs it).** When this runtime's
-filesystem starts fresh in each conversation and it gives you a folder that survives between
-conversations, run this once per conversation, before `booking-agent flow sessions list`:
-
-```bash
-booking-agent runtime prepare --persistent-root <absolute folder that survives>
-```
-
-It links the booking state and the Link sign-in into that folder, so saved bookings, calendar
-preferences, and the sign-in carry over. Use the same folder every time; a different one, or one
-already named `booking-agent`, moves the existing state along instead of splitting it. Add `--link
-<runtime folder>=<persistent folder>` for each extra cache folder the runtime asks you to keep (a
-relative persistent folder is placed under the root). If the user is asked to sign in or reconnect
-right after a restart, run `booking-agent runtime doctor` and follow its `next_command`. When the
-runtime keeps its files anyway, or offers no surviving folder, skip the command. Do not tell the
-user about it. If it fails, continue the booking without it.
+**Keep state between conversations.** `flow init` asks how this runtime keeps its files and refuses
+(`persistence_unresolved`) until you answer. Look at what the runtime offers. If it gives you a
+folder that survives between conversations, re-run the same init with `--persistent-root <absolute
+path of that folder>`: the CLI links saved bookings and the Link sign-in into it, merging what each
+folder holds (booking files by session, the newer copy of anything else) and deleting nothing. If
+the runtime keeps its files anyway, or gives no such folder, re-run it with `--no-persistent-root`.
+If it answers `persistence_folder_not_durable` the folder failed a basic check (a temporary or
+memory-backed place, or not writable): name the folder the runtime really keeps, or use
+`--no-persistent-root`. It sends you back at most twice and then uses the folder as given.
+`persistence_setup_failed` and `persistence_flags_conflict` say what to change. Use the same folder
+every time, never guess a path, never ask the user, and never mention it. A host
+that sets `BOOKING_AGENT_PERSISTENT_ROOT` or `BOOKING_AGENT_PERSISTENCE=none` is never asked. If the
+user is asked to sign in or reconnect right after a restart, run `booking-agent runtime doctor` and
+follow its `next_command`. For extra cache folders the runtime asks you to keep, run `booking-agent
+runtime prepare --persistent-root <folder> --link <runtime folder>=<persistent folder>`.
 
 **Sign the user in to Link**, as described in [Link sign-in](#link-sign-in-automatic). It works
 with no booking in progress. Do not wait for the user to offer to sign in.
@@ -309,7 +308,7 @@ prints each effective setting and where it came from; `booking-agent config init
 
 The CLI decides whether a newer version is worth mentioning; you never decide from version
 numbers or release pages. Pass this skill's version on every `flow init` (`--skill-version
-0.53.0`, from the frontmatter above), so the CLI can tell when these instructions and the
+0.55.0`, from the frontmatter above), so the CLI can tell when these instructions and the
 installed CLI no longer match.
 
 - When a command returns `awaiting_user: update_consent`, ask the question in `prompt` in plain
@@ -471,7 +470,7 @@ confirmation email or on the business's page (`booking_url`). Do not invent a lo
 **Step 1b — Create a new session:**
 
 ```bash
-booking-agent flow init --user-request "<user's exact request>" --skill-version 0.53.0 \
+booking-agent flow init --user-request "<user's exact request>" --skill-version 0.55.0 \
   --skill-path "<absolute path of the SKILL.md you loaded>"
 ```
 

{booking_agent_cli-0.5.0 → booking_agent_cli-0.7.0}/src/booking_agent_cli/commands/flow.py

@@ -399,8 +399,17 @@ def init(
     capability: Optional[List[str]] = typer.Option(
         None, "--capability", help="A capability the user's request needs; repeatable.",
     ),
+    persistent_root: Optional[str] = typer.Option(
+        None, "--persistent-root",
+        help="Absolute folder this runtime keeps between conversations; state is linked into it.",
+    ),
+    no_persistent_root: bool = typer.Option(
+        False, "--no-persistent-root",
+        help="This runtime keeps its files between conversations anyway, or has no such folder.",
+    ),
 ) -> None:
     """Initialize a new booking session."""
+    _resolve_persistence(persistent_root, no_persistent_root)
     store = load_store()
     # Before the session checks: a skill the agent points us at is checked whatever the
     # flow state, so a changed file is never masked by session_active.
@@ -613,6 +622,86 @@ def _upcoming_duplicate_bookings(store: Any, user_request: str) -> List[Dict[str
     return matches
 
 
+def _resolve_persistence(persistent_root: Optional[str], no_persistent_root: bool) -> None:
+    """Make the agent say how this runtime keeps saved state, before any state is written.
+
+    Skipping the setup used to be silent: nothing failed until the next restart lost the
+    booking, the calendar link, and the sign-in. The agent, not the CLI, can see what the runtime
+    offers, so it must answer with a folder or an explicit "no folder"; the CLI never guesses one.
+    """
+    from ..runtime_prepare import (
+        MAX_CORRECTIONS,
+        PrepareError,
+        acknowledge_no_persistence,
+        clear_attempts,
+        corrections_so_far,
+        durability_problem,
+        persistence_resolution,
+        prepare,
+        record_accepted_despite,
+        record_correction,
+    )
+
+    if persistent_root and no_persistent_root:
+        emit_error(
+            "INIT",
+            code="persistence_flags_conflict",
+            message="Pass either --persistent-root or --no-persistent-root, not both.",
+        )
+        raise typer.Exit(code=1)
+    if persistent_root:
+        problem = durability_problem(persistent_root)
+        if problem and corrections_so_far() < MAX_CORRECTIONS:
+            used = record_correction()
+            emit_error(
+                "INIT",
+                code="persistence_folder_not_durable",
+                message=(
+                    f"That folder cannot be relied on to survive a restart: {problem}. Nothing "
+                    "was moved. Re-run the same init command with the folder this runtime "
+                    "really keeps between conversations, or with --no-persistent-root if it keeps "
+                    f"its files anyway. (Correction {used} of {MAX_CORRECTIONS}; after that the "
+                    "folder you name is used as given so the booking is never stuck.)"
+                ),
+            )
+            raise typer.Exit(code=1)
+        if problem:
+            record_accepted_despite(problem)
+        else:
+            clear_attempts()
+        try:
+            prepare(persistent_root, [])
+        except (PrepareError, OSError) as exc:
+            emit_error(
+                "INIT",
+                code="persistence_setup_failed",
+                message=(
+                    f"Saved state could not be linked into that folder ({exc}). Re-run the same "
+                    "init command with the folder this runtime really keeps between "
+                    "conversations, or with --no-persistent-root to go on without it."
+                ),
+            )
+            raise typer.Exit(code=1)
+        return
+    if no_persistent_root:
+        acknowledge_no_persistence()
+        return
+    if persistence_resolution() is None:
+        emit_error(
+            "INIT",
+            code="persistence_unresolved",
+            message=(
+                "Saved bookings and the Link sign-in are not in a folder this runtime keeps "
+                "between conversations, so a restart would lose them. Look at what this runtime "
+                "offers. If it provides a folder that survives restarts, re-run this same init "
+                "command with --persistent-root <absolute path of that folder>. If its files are "
+                "kept anyway, or it offers no such folder, re-run it with --no-persistent-root. "
+                "Decide from the runtime, never ask the user, and never guess a path."
+            ),
+        )
+        raise typer.Exit(code=1)
+
+
 def _unfinished_similar_sessions(store: Any, user_request: str) -> List[Dict[str, Any]]:
     """Unfinished sessions whose request covers most of this one's key terms, newest first."""
     wanted = _request_terms(user_request)

{booking_agent_cli-0.5.0 → booking_agent_cli-0.7.0}/src/booking_agent_cli/main.py

@@ -29,6 +29,15 @@ app.add_typer(runtime_app, name="runtime")
 app.add_typer(skill_app, name="skill")
 app.add_typer(update_app, name="update")
 
+@app.callback()
+def _main(ctx: typer.Context) -> None:
+    """Keep state in the host's persistent folder (when it names one) before any command runs."""
+    if ctx.invoked_subcommand != "runtime":
+        from .runtime_prepare import auto_prepare
+
+        auto_prepare()
+
+
 INTERNAL_ERROR_MESSAGE = (
     "The booking assistant hit an unexpected internal error. Tell the user in plain "
     "words that something went wrong on our side, then follow next_command."