graff — a fast agentic coding harness in Zig: multi-provider, MCP, workflows, DGM evolution loop, TS/Python SDKs
Python
Prepare v0.302.63 release
justrach49edc7fb8a36
diff --git a/CHANGELOG.md b/CHANGELOG.mdindex 500926a8..9b8a9d2d 100644--- a/CHANGELOG.md+++ b/CHANGELOG.md@@ -10,6 +10,12 @@ The release workflow uses a tag's section here as its release notes (ahand-written `docs/releases/<tag>.md` wins if present), so keeping this filecurrent is part of cutting a release.+## v0.302.63++- An authentication failure names the credential that was rejected. A sign-in says "<Provider> sign-in was rejected: sign in again (<login command>)"; an API key says "<Provider> API key was rejected (<source>): replace or remove the key. Your sign-in is not affected."; and a key graff fell back to after a plan ran out says "<Provider> plan is out of usage, and the fallback API key was rejected (<source>)". Before, every case read "provider authentication failed: sign in again or check the API key", so a client showed "Log in" when the key was the problem (#1779, ADR 0310).+- Over ACP a rejected key carries `{"kind":"api_key_rejected","provider":"<id>"}` (v1 error data on -32603; v2 `_meta["graff/recovery"]`), so clients can offer "Update key" instead of a sign-in. `reauth_required` is unchanged.+- Retains all changes from v0.302.62.+## v0.302.62- `rlm`'s `llm_query` works on Claude Agent. Each sub-query runs on its own short-lived, tools-off `claude` process, the way titles and recaps do, so the chat's `claude` process and its prompt cache carry on untouched. Before, it answered "llm_query is not available on Claude Agent" (#1777, ADR 0309).diff --git a/docs/releases/v0.302.63.md b/docs/releases/v0.302.63.mdnew file mode 100644index 00000000..c19547ac--- /dev/null+++ b/docs/releases/v0.302.63.md@@ -0,0 +1,9 @@+# v0.302.63++Authentication errors say which credential was rejected.++- **Sign-in or API key, named.** A provider can hold a sign-in and an API key at once. When one is rejected, the error now says which: "Anthropic sign-in was rejected: sign in again (graff login anthropic)", or "Anthropic API key was rejected (<source>): replace or remove the key. Your sign-in is not affected." Before, both read "provider authentication failed: sign in again or check the API key", so a desktop client offered "Log in" even when the sign-in was fine and the key was the problem.+- **The fallback key, too.** When a plan runs out and graff switches to the API key parked behind it, and that key is then rejected, the error says so: "Anthropic plan is out of usage, and the fallback API key was rejected (<source>): replace or remove the key, or wait for the plan to reset."+- **Typed for clients.** Over ACP a rejected key carries `{"kind":"api_key_rejected","provider":"<id>"}` (v1: error data on -32603; v2: `_meta["graff/recovery"]`), so a client can show "Update key" instead of a sign-in. A rejected sign-in still carries `reauth_required` as before (ADR 0310).++Includes all changes from v0.302.62.diff --git a/scripts/eval/tier1-manifest.json b/scripts/eval/tier1-manifest.jsonindex 1aa73bcd..c28c6dd1 100644--- a/scripts/eval/tier1-manifest.json+++ b/scripts/eval/tier1-manifest.json@@ -14,7 +14,7 @@"src/main.zig","src/repl.zig"],- "test_count_baseline": 3576,+ "test_count_baseline": 3579,"test_count_slack": 25,"required_invariants": [{diff --git a/src/cli_text_source.zig b/src/cli_text_source.zigindex 786bc7f5..3623f6db 100644--- a/src/cli_text_source.zig+++ b/src/cli_text_source.zig@@ -5,6 +5,9 @@pub const changelog_text =\\What's new\\──────────+ \\0.302.63+ \\ • auth errors say which credential was rejected: the sign-in, or the API key (and when it was the fallback)+ \\\\0.302.62\\ • rlm's llm_query works on Claude Agent, on a throwaway claude process\\