@pydantic/logfire-cli-darwin-x64 0.1.2 → 0.1.4

package/README.md

@@ -3,13 +3,15 @@
 Rust command-line tools for [Pydantic Logfire](https://pydantic.dev/logfire).
 
 `logfire` authenticates against the hosted (or self-hosted) Logfire API, drives
-the public Logfire MCP server, points a project at Logfire, and exposes the typed
-Platform API — with first-class machine output for scripts and coding agents.
+the public Logfire MCP server, runs bundled agent skills, points a project
+at Logfire, and exposes the typed Platform API — with first-class machine output
+for scripts and coding agents.
 
 ## Quickstart
 
 ```bash
 cargo install --path crates/logfire-cli   # see docs/installation.md for details
+logfire --region us signup --org acme --project my-project
 logfire auth                              # browser OAuth into the OS keychain
 logfire mcp tools list                    # use that session against public MCP
 ```
@@ -19,9 +21,13 @@ logfire mcp tools list                    # use that session against public MCP
 | Command | What it does |
 | --- | --- |
 | [`logfire auth`](docs/authentication.md) | Browser OAuth shared by CLI and MCP |
+| [`logfire signup`](docs/commands/signup.md) | Create an account, first project, and local SDK credentials |
 | [`logfire init`](docs/commands/init.md) | Point a directory at a Logfire project |
-| [`logfire project`](docs/commands/project.md) | Validate and show the configured SDK project |
+| [`logfire project`](docs/commands/project.md) | Inspect or clean this directory's SDK project configuration |
 | [`logfire setup`](docs/commands/setup.md) | Hand off repository instrumentation to Codex or Claude Code |
+| [`logfire run`](docs/commands/run.md) | Run Python scripts, modules, and console commands with automatic instrumentation |
+| [`logfire skill`](docs/commands/skill.md) | Discover and run CLI-bundled Logfire agent skills |
+| [`logfire codex`](docs/commands/codex.md) | Send Codex's own completed turns to Logfire |
 | [`logfire token`](docs/commands/token.md) | Mint a project read/write token and print it |
 | [`logfire api-key`](docs/commands/api-key.md) | Mint a project-scoped API key and print it |
 | [`logfire api`](docs/commands/api.md) | Typed Platform API endpoints |
@@ -36,7 +42,7 @@ Every command and group accepts concise `-h`/`--help`; use
 The [**User Guide**](docs/README.md) covers everything in task-oriented pages:
 
 - [Installation](docs/installation.md) — the binary and shell completions
-- [Authentication](docs/authentication.md) — logins, regions, `LOGFIRE_TOKEN`, and OS-keychain storage
+- [Authentication](docs/authentication.md) — logins, regions, `LOGFIRE_API_KEY`, and OS-keychain storage
 - [Output contracts](docs/output-contracts.md) — human vs. `--output json`/`jsonl`, the envelope, exit codes, and flag precedence
 
 Global options apply before or after every command. `--region us|eu` (env
@@ -57,26 +63,29 @@ The CLI is a Cargo workspace of small, single-purpose crates:
 | `logfire-cli` | The `logfire` binary: argument parsing (clap) and command dispatch. |
 | `logfire-api` | The typed `logfire api` command surface over the generated client. |
 | `logfire-api-client` | Generated from the OpenAPI schemas (see below); never hand-edited. |
-| `logfire-auth` | Standards-based browser OAuth orchestration. |
+| `logfire-auth` | Terminal UX, organization verification, and profile persistence around browser OAuth. |
 | `logfire-config` | Credential resolution, regions / base-URL, and the request context. |
 | `logfire-init` | `logfire init` project setup and the `.logfire/` credentials file. |
 | `logfire-mcp-core` | Pure, I/O-free decision core for global input/output, envelope, limit, and error-category contracts. |
-| `logfire-mcp-client` | Official `rmcp` transport, standards OAuth, bounded protocol I/O, and protocol-faithful fakes. |
+| `logfire-mcp-client` | Official `rmcp` transport, MCP challenge and token-exchange policy, bounded protocol I/O, and protocol-faithful fakes. |
+| `logfire-oauth` | Platform OAuth, strict SDK/HTTP policy, loopback callback, and confidential session lifecycle. |
 
 See [`dev-docs/ARCHITECTURE.md`](dev-docs/ARCHITECTURE.md) for the product
 boundaries and trust model, and [`dev-docs/CRATE_RULES.md`](dev-docs/CRATE_RULES.md)
-for each crate's dependency and I/O contract.
+for each crate's dependency and I/O contract. The
+[`assurance model`](dev-docs/ASSURANCE_MODEL.md) maps critical invariants to unit,
+property, state-machine, mutation, boundary, smoke, and end-to-end evidence.
 
 ### Design notes
 
 - **No `unsafe`.** The workspace sets `unsafe_code = "forbid"`; safe `std`/`nix`
   APIs have covered every need, and `forbid` (unlike `deny`) can't be overridden
   locally.
-- **Small release binary.** The release profile trades a little compile time for
-  size (`opt-level = "z"`, fat LTO, one codegen unit, `strip`, `panic = "abort"`),
-  taking the macOS arm64 binary from ~15 MB to ~3.6 MB. Because `panic = "abort"`
-  skips unwinding, a panic ends the process without running destructors — fine for
-  a CLI, but note a task panic aborts the whole process rather than just that task.
+- **Small release binary.** The release profile trades compile time for size
+  (`opt-level = "z"`, fat LTO, one codegen unit, `strip`, `panic = "abort"`).
+  Because `panic = "abort"` skips unwinding, the accepted trade-off is that a
+  task panic aborts the whole process without running destructors instead of
+  ending only that task.
 - **TLS via `ring`, not `aws-lc`.** `reqwest`/`rustls` use the `ring` crypto
   provider — much smaller, and no `cmake` at build time. Trade-off: `ring` cannot
   verify P-521-signed certificates, so TLS can fail behind a corporate

package/package.json

@@ -11,5 +11,5 @@
   ],
   "preferUnplugged": true,
   "repository": "https://github.com/pydantic/logfire-cli",
-  "version": "0.1.2"
+  "version": "0.1.4"
 }