dailybot-cli 2.0.1__tar.gz → 3.0.1__tar.gz

{dailybot_cli-2.0.1 → dailybot_cli-3.0.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: dailybot-cli
-Version: 2.0.1
+Version: 3.0.1
 Summary: Dailybot CLI - The command-line bridge between humans and agents. Progress reports, observability, and workflow automation for modern teams across Slack, Google Chat, Discord, MS Teams, and more.
 Author-email: Dailybot <support@dailybot.com>
 License: MIT
@@ -43,25 +43,6 @@ The command-line bridge between **humans** and **agents**. [Dailybot](https://ww
 
 > 🤖 **Using an AI coding agent?** The CLI is even better paired with the **[Dailybot agent skill](https://github.com/DailybotHQ/agent-skill)** — a playbook that teaches Claude Code, Cursor, Codex, Gemini, and Copilot *when* and *how* to use these commands (report progress, complete check-ins, run and **author** forms & check-ins, give kudos, send chat messages). Install it with `npx skills add DailybotHQ/agent-skill`. See [For agents → pair with the agent skill](#pair-with-the-dailybot-agent-skill).
 
-## Upgrading to 2.0 (breaking changes)
-
-**2.0** completes the CLI's parity with the public Dailybot API. It is a **major**
-release because two consumer-visible contracts changed:
-
-- **List output is now a paginated envelope.** Every list command paginates
-  (`--all`, `--page`, `--page-size`, `--limit`), searches (`--search`/`--grep`), and
-  filters by date (`--since`/`--until`/`--date`/`--today`/`--last-week`), and prints a
-  `Showing X of N` footer. `--json` still emits the list of items, so most scripts are
-  unaffected; anything that parsed a *bare array* from an internal endpoint should read
-  the `results` field of the envelope instead.
-- **Errors are machine-readable.** Failures now carry a stable `code` and render
-  friendly, actionable messages (plan/permission/validation), instead of raw JSON.
-
-New in 2.0: `dailybot me` / `org` / `user get`, `kudos list` / `org` / `wall-of-fame`,
-the read-only `workflow list` / `get`, `chat send --send-as-user` / `--send-as-me`, and
-uniform API-key ↔ Bearer auth on every endpoint (except `logout`, which stays
-Bearer-only). See the [API reference](docs/API_REFERENCE.md) for the full surface.
-
 ## Installation
 
 ```bash
@@ -75,8 +56,8 @@ exact release, or `>=` to set a **minimum floor** (installs the newest release a
 or above it):
 
 ```bash
-pip install dailybot-cli==1.19.1     # exactly 1.19.1
-pip install "dailybot-cli>=1.19.1"   # 1.19.1 or newer — picks the latest available
+pip install dailybot-cli==3.0.0     # exactly 3.0.0
+pip install "dailybot-cli>=3.0.0"   # 3.0.0 or newer — picks the latest available
 ```
 
 ### Alternative installation methods
@@ -85,8 +66,8 @@ Every method installs the **latest** release by default. Where a version can be
 pinned, the pinned form is shown right below the default one. Two pinning styles
 are supported everywhere `DAILYBOT_VERSION` / `--version` is accepted:
 
-- **Exact** — `1.19.1` (or `==1.19.1`) installs precisely that release.
-- **Minimum floor** — `>=1.19.1` installs the newest release at or above `1.19.1`,
+- **Exact** — `3.0.0` (or `==3.0.0`) installs precisely that release.
+- **Minimum floor** — `>=3.0.0` installs the newest release at or above `3.0.0`,
   so you get any later version automatically while guaranteeing a lower bound.
 
 **macOS (Homebrew)**
@@ -99,13 +80,13 @@ Homebrew always installs the latest published formula. To pin a specific
 version, install with pip instead:
 
 ```bash
-pip install dailybot-cli==1.19.1
+pip install dailybot-cli==3.0.0
 ```
 
 **Linux, WSL2, or Git Bash on Windows (binary or pip fallback)**
 
 ```bash
-curl -sSL https://cli.dailybot.com/install.sh | bash
+curl -fsSL https://cli.dailybot.com/install.sh | bash
 ```
 
 Pin a version with the `DAILYBOT_VERSION` environment variable **or** the
@@ -114,13 +95,13 @@ accepts an exact version or a `>=` minimum floor:
 
 ```bash
 # exact version, environment variable
-curl -sSL https://cli.dailybot.com/install.sh | DAILYBOT_VERSION=1.19.1 bash
+curl -fsSL https://cli.dailybot.com/install.sh | DAILYBOT_VERSION=3.0.0 bash
 
 # exact version, equivalent flag (note the `-s --` that forwards args through bash)
-curl -sSL https://cli.dailybot.com/install.sh | bash -s -- --version 1.19.1
+curl -fsSL https://cli.dailybot.com/install.sh | bash -s -- --version 3.0.0
 
-# minimum floor — installs 1.19.1 or the newest release above it
-curl -sSL https://cli.dailybot.com/install.sh | DAILYBOT_VERSION='>=1.19.1' bash
+# minimum floor — installs 3.0.0 or the newest release above it
+curl -fsSL https://cli.dailybot.com/install.sh | DAILYBOT_VERSION='>=3.0.0' bash
 ```
 
 An exact pin installs the matching Linux binary when one exists, otherwise falls
@@ -128,6 +109,12 @@ back to `pip install dailybot-cli==<version>`. A `>=` floor installs the latest
 binary when it satisfies the floor, otherwise falls back to
 `pip install "dailybot-cli>=<version>"`.
 
+> **Why `curl -f`?** Without `-f`, an HTTP error (404/500) makes curl print the error
+> page **with exit status 0**, and `bash` would happily execute it. `-f` turns that into
+> a non-zero exit instead. Running this in a script, CI job, or Dockerfile? Add
+> `set -o pipefail` too — otherwise a failing `curl` still leaves the pipeline's exit
+> status at `bash`'s `0` and the install silently does nothing.
+
 **Native Windows PowerShell** (only if you don't have WSL2 or Git Bash)
 
 ```powershell
@@ -140,10 +127,10 @@ An exact version or a `>=` minimum floor both work:
 
 ```powershell
 # exact version
-$env:DAILYBOT_VERSION = '1.19.1'; irm https://cli.dailybot.com/install.ps1 | iex
+$env:DAILYBOT_VERSION = '3.0.0'; irm https://cli.dailybot.com/install.ps1 | iex
 
-# minimum floor — installs 1.19.1 or the newest release above it
-$env:DAILYBOT_VERSION = '>=1.19.1'; irm https://cli.dailybot.com/install.ps1 | iex
+# minimum floor — installs 3.0.0 or the newest release above it
+$env:DAILYBOT_VERSION = '>=3.0.0'; irm https://cli.dailybot.com/install.ps1 | iex
 ```
 
 Requires Python 3.10+ on PATH. Wraps `pipx` / `uv tool` / `pip --user`.
@@ -158,7 +145,7 @@ The CLI exposes two ways to inspect what's installed — a quick one-liner for s
 ```bash
 # Single-line, scriptable
 dailybot --version
-# → dailybot 1.0.0 (Python 3.12.4)
+# → dailybot 3.0.0 (Python 3.12.4)
 
 # Multi-line panel: version, Python runtime, install path, release notes link
 dailybot version

{dailybot_cli-2.0.1 → dailybot_cli-3.0.1}/README.md

@@ -4,25 +4,6 @@ The command-line bridge between **humans** and **agents**. [Dailybot](https://ww
 
 > 🤖 **Using an AI coding agent?** The CLI is even better paired with the **[Dailybot agent skill](https://github.com/DailybotHQ/agent-skill)** — a playbook that teaches Claude Code, Cursor, Codex, Gemini, and Copilot *when* and *how* to use these commands (report progress, complete check-ins, run and **author** forms & check-ins, give kudos, send chat messages). Install it with `npx skills add DailybotHQ/agent-skill`. See [For agents → pair with the agent skill](#pair-with-the-dailybot-agent-skill).
 
-## Upgrading to 2.0 (breaking changes)
-
-**2.0** completes the CLI's parity with the public Dailybot API. It is a **major**
-release because two consumer-visible contracts changed:
-
-- **List output is now a paginated envelope.** Every list command paginates
-  (`--all`, `--page`, `--page-size`, `--limit`), searches (`--search`/`--grep`), and
-  filters by date (`--since`/`--until`/`--date`/`--today`/`--last-week`), and prints a
-  `Showing X of N` footer. `--json` still emits the list of items, so most scripts are
-  unaffected; anything that parsed a *bare array* from an internal endpoint should read
-  the `results` field of the envelope instead.
-- **Errors are machine-readable.** Failures now carry a stable `code` and render
-  friendly, actionable messages (plan/permission/validation), instead of raw JSON.
-
-New in 2.0: `dailybot me` / `org` / `user get`, `kudos list` / `org` / `wall-of-fame`,
-the read-only `workflow list` / `get`, `chat send --send-as-user` / `--send-as-me`, and
-uniform API-key ↔ Bearer auth on every endpoint (except `logout`, which stays
-Bearer-only). See the [API reference](docs/API_REFERENCE.md) for the full surface.
-
 ## Installation
 
 ```bash
@@ -36,8 +17,8 @@ exact release, or `>=` to set a **minimum floor** (installs the newest release a
 or above it):
 
 ```bash
-pip install dailybot-cli==1.19.1     # exactly 1.19.1
-pip install "dailybot-cli>=1.19.1"   # 1.19.1 or newer — picks the latest available
+pip install dailybot-cli==3.0.0     # exactly 3.0.0
+pip install "dailybot-cli>=3.0.0"   # 3.0.0 or newer — picks the latest available
 ```
 
 ### Alternative installation methods
@@ -46,8 +27,8 @@ Every method installs the **latest** release by default. Where a version can be
 pinned, the pinned form is shown right below the default one. Two pinning styles
 are supported everywhere `DAILYBOT_VERSION` / `--version` is accepted:
 
-- **Exact** — `1.19.1` (or `==1.19.1`) installs precisely that release.
-- **Minimum floor** — `>=1.19.1` installs the newest release at or above `1.19.1`,
+- **Exact** — `3.0.0` (or `==3.0.0`) installs precisely that release.
+- **Minimum floor** — `>=3.0.0` installs the newest release at or above `3.0.0`,
   so you get any later version automatically while guaranteeing a lower bound.
 
 **macOS (Homebrew)**
@@ -60,13 +41,13 @@ Homebrew always installs the latest published formula. To pin a specific
 version, install with pip instead:
 
 ```bash
-pip install dailybot-cli==1.19.1
+pip install dailybot-cli==3.0.0
 ```
 
 **Linux, WSL2, or Git Bash on Windows (binary or pip fallback)**
 
 ```bash
-curl -sSL https://cli.dailybot.com/install.sh | bash
+curl -fsSL https://cli.dailybot.com/install.sh | bash
 ```
 
 Pin a version with the `DAILYBOT_VERSION` environment variable **or** the
@@ -75,13 +56,13 @@ accepts an exact version or a `>=` minimum floor:
 
 ```bash
 # exact version, environment variable
-curl -sSL https://cli.dailybot.com/install.sh | DAILYBOT_VERSION=1.19.1 bash
+curl -fsSL https://cli.dailybot.com/install.sh | DAILYBOT_VERSION=3.0.0 bash
 
 # exact version, equivalent flag (note the `-s --` that forwards args through bash)
-curl -sSL https://cli.dailybot.com/install.sh | bash -s -- --version 1.19.1
+curl -fsSL https://cli.dailybot.com/install.sh | bash -s -- --version 3.0.0
 
-# minimum floor — installs 1.19.1 or the newest release above it
-curl -sSL https://cli.dailybot.com/install.sh | DAILYBOT_VERSION='>=1.19.1' bash
+# minimum floor — installs 3.0.0 or the newest release above it
+curl -fsSL https://cli.dailybot.com/install.sh | DAILYBOT_VERSION='>=3.0.0' bash
 ```
 
 An exact pin installs the matching Linux binary when one exists, otherwise falls
@@ -89,6 +70,12 @@ back to `pip install dailybot-cli==<version>`. A `>=` floor installs the latest
 binary when it satisfies the floor, otherwise falls back to
 `pip install "dailybot-cli>=<version>"`.
 
+> **Why `curl -f`?** Without `-f`, an HTTP error (404/500) makes curl print the error
+> page **with exit status 0**, and `bash` would happily execute it. `-f` turns that into
+> a non-zero exit instead. Running this in a script, CI job, or Dockerfile? Add
+> `set -o pipefail` too — otherwise a failing `curl` still leaves the pipeline's exit
+> status at `bash`'s `0` and the install silently does nothing.
+
 **Native Windows PowerShell** (only if you don't have WSL2 or Git Bash)
 
 ```powershell
@@ -101,10 +88,10 @@ An exact version or a `>=` minimum floor both work:
 
 ```powershell
 # exact version
-$env:DAILYBOT_VERSION = '1.19.1'; irm https://cli.dailybot.com/install.ps1 | iex
+$env:DAILYBOT_VERSION = '3.0.0'; irm https://cli.dailybot.com/install.ps1 | iex
 
-# minimum floor — installs 1.19.1 or the newest release above it
-$env:DAILYBOT_VERSION = '>=1.19.1'; irm https://cli.dailybot.com/install.ps1 | iex
+# minimum floor — installs 3.0.0 or the newest release above it
+$env:DAILYBOT_VERSION = '>=3.0.0'; irm https://cli.dailybot.com/install.ps1 | iex
 ```
 
 Requires Python 3.10+ on PATH. Wraps `pipx` / `uv tool` / `pip --user`.
@@ -119,7 +106,7 @@ The CLI exposes two ways to inspect what's installed — a quick one-liner for s
 ```bash
 # Single-line, scriptable
 dailybot --version
-# → dailybot 1.0.0 (Python 3.12.4)
+# → dailybot 3.0.0 (Python 3.12.4)
 
 # Multi-line panel: version, Python runtime, install path, release notes link
 dailybot version

{dailybot_cli-2.0.1 → dailybot_cli-3.0.1}/dailybot_cli.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: dailybot-cli
-Version: 2.0.1
+Version: 3.0.1
 Summary: Dailybot CLI - The command-line bridge between humans and agents. Progress reports, observability, and workflow automation for modern teams across Slack, Google Chat, Discord, MS Teams, and more.
 Author-email: Dailybot <support@dailybot.com>
 License: MIT
@@ -43,25 +43,6 @@ The command-line bridge between **humans** and **agents**. [Dailybot](https://ww
 
 > 🤖 **Using an AI coding agent?** The CLI is even better paired with the **[Dailybot agent skill](https://github.com/DailybotHQ/agent-skill)** — a playbook that teaches Claude Code, Cursor, Codex, Gemini, and Copilot *when* and *how* to use these commands (report progress, complete check-ins, run and **author** forms & check-ins, give kudos, send chat messages). Install it with `npx skills add DailybotHQ/agent-skill`. See [For agents → pair with the agent skill](#pair-with-the-dailybot-agent-skill).
 
-## Upgrading to 2.0 (breaking changes)
-
-**2.0** completes the CLI's parity with the public Dailybot API. It is a **major**
-release because two consumer-visible contracts changed:
-
-- **List output is now a paginated envelope.** Every list command paginates
-  (`--all`, `--page`, `--page-size`, `--limit`), searches (`--search`/`--grep`), and
-  filters by date (`--since`/`--until`/`--date`/`--today`/`--last-week`), and prints a
-  `Showing X of N` footer. `--json` still emits the list of items, so most scripts are
-  unaffected; anything that parsed a *bare array* from an internal endpoint should read
-  the `results` field of the envelope instead.
-- **Errors are machine-readable.** Failures now carry a stable `code` and render
-  friendly, actionable messages (plan/permission/validation), instead of raw JSON.
-
-New in 2.0: `dailybot me` / `org` / `user get`, `kudos list` / `org` / `wall-of-fame`,
-the read-only `workflow list` / `get`, `chat send --send-as-user` / `--send-as-me`, and
-uniform API-key ↔ Bearer auth on every endpoint (except `logout`, which stays
-Bearer-only). See the [API reference](docs/API_REFERENCE.md) for the full surface.
-
 ## Installation
 
 ```bash
@@ -75,8 +56,8 @@ exact release, or `>=` to set a **minimum floor** (installs the newest release a
 or above it):
 
 ```bash
-pip install dailybot-cli==1.19.1     # exactly 1.19.1
-pip install "dailybot-cli>=1.19.1"   # 1.19.1 or newer — picks the latest available
+pip install dailybot-cli==3.0.0     # exactly 3.0.0
+pip install "dailybot-cli>=3.0.0"   # 3.0.0 or newer — picks the latest available
 ```
 
 ### Alternative installation methods
@@ -85,8 +66,8 @@ Every method installs the **latest** release by default. Where a version can be
 pinned, the pinned form is shown right below the default one. Two pinning styles
 are supported everywhere `DAILYBOT_VERSION` / `--version` is accepted:
 
-- **Exact** — `1.19.1` (or `==1.19.1`) installs precisely that release.
-- **Minimum floor** — `>=1.19.1` installs the newest release at or above `1.19.1`,
+- **Exact** — `3.0.0` (or `==3.0.0`) installs precisely that release.
+- **Minimum floor** — `>=3.0.0` installs the newest release at or above `3.0.0`,
   so you get any later version automatically while guaranteeing a lower bound.
 
 **macOS (Homebrew)**
@@ -99,13 +80,13 @@ Homebrew always installs the latest published formula. To pin a specific
 version, install with pip instead:
 
 ```bash
-pip install dailybot-cli==1.19.1
+pip install dailybot-cli==3.0.0
 ```
 
 **Linux, WSL2, or Git Bash on Windows (binary or pip fallback)**
 
 ```bash
-curl -sSL https://cli.dailybot.com/install.sh | bash
+curl -fsSL https://cli.dailybot.com/install.sh | bash
 ```
 
 Pin a version with the `DAILYBOT_VERSION` environment variable **or** the
@@ -114,13 +95,13 @@ accepts an exact version or a `>=` minimum floor:
 
 ```bash
 # exact version, environment variable
-curl -sSL https://cli.dailybot.com/install.sh | DAILYBOT_VERSION=1.19.1 bash
+curl -fsSL https://cli.dailybot.com/install.sh | DAILYBOT_VERSION=3.0.0 bash
 
 # exact version, equivalent flag (note the `-s --` that forwards args through bash)
-curl -sSL https://cli.dailybot.com/install.sh | bash -s -- --version 1.19.1
+curl -fsSL https://cli.dailybot.com/install.sh | bash -s -- --version 3.0.0
 
-# minimum floor — installs 1.19.1 or the newest release above it
-curl -sSL https://cli.dailybot.com/install.sh | DAILYBOT_VERSION='>=1.19.1' bash
+# minimum floor — installs 3.0.0 or the newest release above it
+curl -fsSL https://cli.dailybot.com/install.sh | DAILYBOT_VERSION='>=3.0.0' bash
 ```
 
 An exact pin installs the matching Linux binary when one exists, otherwise falls
@@ -128,6 +109,12 @@ back to `pip install dailybot-cli==<version>`. A `>=` floor installs the latest
 binary when it satisfies the floor, otherwise falls back to
 `pip install "dailybot-cli>=<version>"`.
 
+> **Why `curl -f`?** Without `-f`, an HTTP error (404/500) makes curl print the error
+> page **with exit status 0**, and `bash` would happily execute it. `-f` turns that into
+> a non-zero exit instead. Running this in a script, CI job, or Dockerfile? Add
+> `set -o pipefail` too — otherwise a failing `curl` still leaves the pipeline's exit
+> status at `bash`'s `0` and the install silently does nothing.
+
 **Native Windows PowerShell** (only if you don't have WSL2 or Git Bash)
 
 ```powershell
@@ -140,10 +127,10 @@ An exact version or a `>=` minimum floor both work:
 
 ```powershell
 # exact version
-$env:DAILYBOT_VERSION = '1.19.1'; irm https://cli.dailybot.com/install.ps1 | iex
+$env:DAILYBOT_VERSION = '3.0.0'; irm https://cli.dailybot.com/install.ps1 | iex
 
-# minimum floor — installs 1.19.1 or the newest release above it
-$env:DAILYBOT_VERSION = '>=1.19.1'; irm https://cli.dailybot.com/install.ps1 | iex
+# minimum floor — installs 3.0.0 or the newest release above it
+$env:DAILYBOT_VERSION = '>=3.0.0'; irm https://cli.dailybot.com/install.ps1 | iex
 ```
 
 Requires Python 3.10+ on PATH. Wraps `pipx` / `uv tool` / `pip --user`.
@@ -158,7 +145,7 @@ The CLI exposes two ways to inspect what's installed — a quick one-liner for s
 ```bash
 # Single-line, scriptable
 dailybot --version
-# → dailybot 1.0.0 (Python 3.12.4)
+# → dailybot 3.0.0 (Python 3.12.4)
 
 # Multi-line panel: version, Python runtime, install path, release notes link
 dailybot version

{dailybot_cli-2.0.1 → dailybot_cli-3.0.1}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "dailybot-cli"
-version = "2.0.1"
+version = "3.0.1"
 description = "Dailybot CLI - The command-line bridge between humans and agents. Progress reports, observability, and workflow automation for modern teams across Slack, Google Chat, Discord, MS Teams, and more."
 readme = "README.md"
 license = {text = "MIT"}