@anyforge/control 0.7.2 → 0.8.1

package/README.md

@@ -14,6 +14,17 @@ The second half is what makes AnyForge usable from CI. Every command speaks the
 npx @anyforge/control init
 ```
 
+Sign in to the workspace you want to connect. Issuing a Control key requires
+an **Owner**, **Operator** or **Editor** role in that workspace. If approval
+says **Editor or higher required**, ask a workspace owner to check your
+membership and role, then rerun `init` with a new browser approval code.
+Reinstalling the CLI does not change your permissions.
+
+Owners and Operators can receive `read`, `write` and `approve` scopes.
+Editors can receive `read` and `write` for planning, but cannot run crews or
+approve gates. A role change does not add scopes to an existing key; rerun
+`init` if the new role needs scopes your key lacks.
+
 The CLI:
 
 1. Issues a one-time auth code, opens your browser to authorise it.
@@ -45,9 +56,16 @@ The inference proxy is **BYOK-only**: it routes Claude Code through your own Ant
 `anyforge init` detects a subscription login and **skips patching**, steering you to the **AnyForge MCP server** instead — which keeps your subscription for inference and adds AnyForge control (HIL approvals, work items, crews) on top, with no auth conflict:
 
 ```bash
-claude mcp add anyforge --env ANYFORGE_API_KEY=<your key> -- npx -y @anyforge/mcp-server
+claude mcp add anyforge -- npx -y @anyforge/mcp-server
 ```
 
+Run this after `init`: the MCP server reads the credential and endpoint from
+`~/.anyforge/credentials`, so no secret belongs in the command. If your MCP
+client runs on another machine, configure its secret store with
+`ANYFORGE_API_TOKEN` and `ANYFORGE_API_URL`; `ANYFORGE_API_KEY` is not the
+MCP server's credential variable. Restart the client and check
+`claude mcp list`.
+
 If you really want the metered BYOK proxy, re-run `anyforge init --force` (you'll need an Anthropic API key configured on your company; this disables your subscription in Claude Code until you `anyforge logout`).
 
 ### Why `ANTHROPIC_AUTH_TOKEN`, not `ANTHROPIC_API_KEY`?
@@ -126,6 +144,35 @@ attachment when a turn exceeds the remaining conversation limit.
 `anyforge ask` keeps its existing stateless read-only API and JSON output.
 See the [CLI guide](https://anyforge.ai/docs/cli) for the full command contract.
 
+### Oracle in ACP clients
+
+`anyforge acp` exposes the hosted Oracle over Agent Client Protocol v1 stdio.
+Sign in once with `anyforge oracle login`, then add a local ACP provider in
+T3 Code with executable `anyforge` and argument `acp`. For an editor that
+accepts command configuration:
+
+```json
+{
+  "command": "anyforge",
+  "args": ["acp"]
+}
+```
+
+The adapter supports saved conversations, streaming answers, tool activity,
+questions, cancellation and recovery after a stream disconnect. Read access
+is the default. Add `--workspace <name-or-id>` to select a saved workspace,
+or `--program`, `--initiative` or `--codebase` to select Oracle context.
+Workspace changes need a suitable grant and `--write`; operator actions also
+need `--approve` and your current role. The same Oracle confirmation rules apply.
+
+This is a hosted Oracle integration: local files are never opened or changed,
+and client-supplied MCP tools are omitted with a visible notice. T3's injected
+tools are handled this way too. Your workspace's server-side tools remain
+available within your access. This deliberately limited ACP profile does not
+claim full protocol conformance. See the
+[ACP setup guide](https://anyforge.ai/docs?page=acp) for limits
+and setup details. ACP v2 is not supported.
+
 ### Setup
 
 | | |
@@ -152,6 +199,8 @@ See the [CLI guide](https://anyforge.ai/docs/cli) for the full command contract.
 | `anyforge workflows` | List operator workflows | `read` |
 | `anyforge run <id>` | Dispatch a run (`--input '{"repo":"acme/web"}'`) | `write` |
 | `anyforge ask <question>` | Ask the Oracle one question | `read` |
+| `anyforge audit` | Page through the hash-chained audit trail (`--event`, `--actor`, `--from`, `--to`, `--cursor`, `--all`); `--verify` checks every hash and link across the pages read | `audit:read` + owner |
+| `anyforge people invite <email> --role <role>` | Invite one person as operator, editor, viewer or filer on a verified company domain (`--team <ids>`, `--no-email`); `people invitations` lists the invitations the key could have written and `people withdraw <email>` withdraws a pending one | `people:invite` + owner |
 
 Every command takes `--json`, which prints the API payload verbatim:
 
@@ -171,6 +220,7 @@ CI gates on these, so they are a contract:
 | `2` | Usage error |
 | `3` | Not authenticated — run `init`, or set `ANYFORGE_API_TOKEN` |
 | `4` | The API refused; its error code, and any details the API sent with it, print to stderr |
+| `5` | `audit --verify` found a broken link or an entry that no longer matches its hash |
 | `130` | An Oracle run was interrupted: `exec` was cancelled with Ctrl+C, or you left an interactive session whose last answer you cancelled |
 
 Errors and progress go to stderr, so a `--json` pipe stays parseable under a failure.
@@ -232,6 +282,12 @@ A successful check verifies the Control API used by MCP; confirm the actual MCP
 connection in your agent client. It does not send an inference request or charge
 for a test call.
 
+If you used an older CLI, run `npx @anyforge/control@latest status` to use the
+current diagnostics. Confirm the displayed workspace and user before checking
+activity. In **Settings → API keys**, the last-used time shows credential use;
+in **Traces**, **My activity** filters attributable traces to your user.
+Older traces labelled **Unknown** cannot establish who made the request.
+
 The three connections are separate:
 
 - **MCP** provides access to AnyForge work and tools. It does not route inference