@pydantic/logfire-cli-linux-x64 0.1.1 → 0.1.3

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,15 +21,19 @@ 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 setup`](docs/commands/setup.md) | Hand off repository instrumentation to Codex or Claude Code |
+| [`logfire skill`](docs/commands/skill.md) | Discover and run CLI-bundled Logfire agent skills |
 | [`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 |
 | [`logfire mcp`](docs/commands/mcp.md) | Discover and call the public Logfire MCP server |
 | [`logfire doctor`](docs/commands/doctor.md) | Diagnose local prerequisites without exposing secrets |
 
-Every command and group accepts `--help`.
+Every command and group accepts concise `-h`/`--help`; use
+`logfire help <command>` for the detailed option reference.
 
 ## Documentation
 
@@ -40,7 +46,10 @@ The [**User Guide**](docs/README.md) covers everything in task-oriented pages:
 Global options apply before or after every command. `--region us|eu` (env
 `PYDANTIC_LOGFIRE_REGION`) chooses a hosted region, while `--base-url <URL>`
 (env `LOGFIRE_BASE_URL`) targets a self-hosted or staging instance and overrides
-it. `--output human|json|jsonl`, `--no-input`, and `--color auto|always|never`
+it. `--org <ORGANIZATION>` selects a saved organization-specific OAuth profile;
+`logfire auth status` lists profiles and `logfire auth switch <ORGANIZATION>`
+changes the default without opening the credential store.
+`--output human|json|jsonl`, `--no-input`, and `--color auto|always|never`
 provide the shared presentation and prompting contract.
 
 ## Architecture
@@ -52,15 +61,18 @@ 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
 

package/package.json

@@ -14,5 +14,5 @@
   ],
   "preferUnplugged": true,
   "repository": "https://github.com/pydantic/logfire-cli",
-  "version": "0.1.1"
+  "version": "0.1.3"
 }