fix(output): unwrap nested error objects; fix --result-type docs; agent-help name-vs-UUID examples

[ernestoongaro]

Three small things from a full sweep of the CLI against a playground instance.

1. Nested error bodies.{"error":{"code":403,"message":"Invalid bearer token"}} (what a bad token returns) was surfaced as the whole object re-serialised into "error". extractErrorDetail now descends one level into an object-valued detail/message/error key. Before/after:

   "error": "{\"error\":{\"code\":403,\"message\":\"Invalid bearer token\"}}"
   "error": "Invalid bearer token"
   

   Test added; fallback to the raw body is unchanged when no message is found.

2. Docs.CLAUDE.md and an output.go comment referred to a --result-type flag that doesn't exist — CSV/XLSX come from query run's resultType body field.

3. agent-help. The existing "some positionals take a NAME, not a UUID" note gains the other cases that tripped a scripted sweep (delete-branch, labels get, documents add-label, users get-model-roles <membership-id>). The spec and --help already describe each correctly; this is reinforcement only, easy to drop if unwanted.

🤖 Generated with Claude Code

https://claude.ai/code/session_01Ei8UYaG1bW5PJhk93EaqzA

[dspangen]

Codex says:

One minor documentation issue; no functional defects found.

[P3] Remove the remaining obsolete flag reference

cmd/omni/output_test.go:188 still says XLSX is selected with --result-type, although this PR establishes that the flag does not exist. Please update it to reference the query run body’s resultType field so the cleanup is complete.

The nested error extraction itself looks correct and preserves existing fallback behavior. GitHub CI reports both lint and test passing.

[ernestoongaro]

Fixed in f926995 — output_test.go:188 was the last --result-type reference in the repo (grep is now clean); it now reads as the resultType body field like the others.

[ernestoongaro]

Three small things from a full sweep of the CLI against a playground instance.

1. Nested error bodies.{"error":{"code":403,"message":"Invalid bearer token"}} (what a bad token returns) was surfaced as the whole object re-serialised into "error". extractErrorDetail now descends one level into an object-valued detail/message/error key. Before/after:

   "error": "{\"error\":{\"code\":403,\"message\":\"Invalid bearer token\"}}"
   "error": "Invalid bearer token"
   

   Test added; fallback to the raw body is unchanged when no message is found.

2. Docs.CLAUDE.md and an output.go comment referred to a --result-type flag that doesn't exist — CSV/XLSX come from query run's resultType body field.

3. agent-help. The existing "some positionals take a NAME, not a UUID" note gains the other cases that tripped a scripted sweep (delete-branch, labels get, documents add-label, users get-model-roles <membership-id>). The spec and --help already describe each correctly; this is reinforcement only, easy to drop if unwanted.

🤖 Generated with Claude Code

https://claude.ai/code/session_01Ei8UYaG1bW5PJhk93EaqzA

[dspangen]

Codex says:

One minor documentation issue; no functional defects found.

[P3] Remove the remaining obsolete flag reference

cmd/omni/output_test.go:188 still says XLSX is selected with --result-type, although this PR establishes that the flag does not exist. Please update it to reference the query run body’s resultType field so the cleanup is complete.

The nested error extraction itself looks correct and preserves existing fallback behavior. GitHub CI reports both lint and test passing.

[ernestoongaro]

Fixed in f926995 — output_test.go:188 was the last --result-type reference in the repo (grep is now clean); it now reads as the resultType body field like the others.

[ernestoongaro]

Three small things from a full sweep of the CLI against a playground instance.

1. Nested error bodies.{"error":{"code":403,"message":"Invalid bearer token"}} (what a bad token returns) was surfaced as the whole object re-serialised into "error". extractErrorDetail now descends one level into an object-valued detail/message/error key. Before/after:

   "error": "{\"error\":{\"code\":403,\"message\":\"Invalid bearer token\"}}"
   "error": "Invalid bearer token"
   

   Test added; fallback to the raw body is unchanged when no message is found.

2. Docs.CLAUDE.md and an output.go comment referred to a --result-type flag that doesn't exist — CSV/XLSX come from query run's resultType body field.

3. agent-help. The existing "some positionals take a NAME, not a UUID" note gains the other cases that tripped a scripted sweep (delete-branch, labels get, documents add-label, users get-model-roles <membership-id>). The spec and --help already describe each correctly; this is reinforcement only, easy to drop if unwanted.

🤖 Generated with Claude Code

https://claude.ai/code/session_01Ei8UYaG1bW5PJhk93EaqzA

[dspangen]

Codex says:

One minor documentation issue; no functional defects found.

[P3] Remove the remaining obsolete flag reference

cmd/omni/output_test.go:188 still says XLSX is selected with --result-type, although this PR establishes that the flag does not exist. Please update it to reference the query run body’s resultType field so the cleanup is complete.

The nested error extraction itself looks correct and preserves existing fallback behavior. GitHub CI reports both lint and test passing.

[ernestoongaro]

Fixed in f926995 — output_test.go:188 was the last --result-type reference in the repo (grep is now clean); it now reads as the resultType body field like the others.

[ernestoongaro]

Three small things from a full sweep of the CLI against a playground instance.

1. Nested error bodies.{"error":{"code":403,"message":"Invalid bearer token"}} (what a bad token returns) was surfaced as the whole object re-serialised into "error". extractErrorDetail now descends one level into an object-valued detail/message/error key. Before/after:

   "error": "{\"error\":{\"code\":403,\"message\":\"Invalid bearer token\"}}"
   "error": "Invalid bearer token"
   

   Test added; fallback to the raw body is unchanged when no message is found.

2. Docs.CLAUDE.md and an output.go comment referred to a --result-type flag that doesn't exist — CSV/XLSX come from query run's resultType body field.

3. agent-help. The existing "some positionals take a NAME, not a UUID" note gains the other cases that tripped a scripted sweep (delete-branch, labels get, documents add-label, users get-model-roles <membership-id>). The spec and --help already describe each correctly; this is reinforcement only, easy to drop if unwanted.

🤖 Generated with Claude Code

https://claude.ai/code/session_01Ei8UYaG1bW5PJhk93EaqzA

[dspangen]

Codex says:

One minor documentation issue; no functional defects found.

[P3] Remove the remaining obsolete flag reference

cmd/omni/output_test.go:188 still says XLSX is selected with --result-type, although this PR establishes that the flag does not exist. Please update it to reference the query run body’s resultType field so the cleanup is complete.

The nested error extraction itself looks correct and preserves existing fallback behavior. GitHub CI reports both lint and test passing.

[ernestoongaro]

Fixed in f926995 — output_test.go:188 was the last --result-type reference in the repo (grep is now clean); it now reads as the resultType body field like the others.

[ernestoongaro]

Three small things from a full sweep of the CLI against a playground instance.

1. Nested error bodies.{"error":{"code":403,"message":"Invalid bearer token"}} (what a bad token returns) was surfaced as the whole object re-serialised into "error". extractErrorDetail now descends one level into an object-valued detail/message/error key. Before/after:

   "error": "{\"error\":{\"code\":403,\"message\":\"Invalid bearer token\"}}"
   "error": "Invalid bearer token"
   

   Test added; fallback to the raw body is unchanged when no message is found.

2. Docs.CLAUDE.md and an output.go comment referred to a --result-type flag that doesn't exist — CSV/XLSX come from query run's resultType body field.

3. agent-help. The existing "some positionals take a NAME, not a UUID" note gains the other cases that tripped a scripted sweep (delete-branch, labels get, documents add-label, users get-model-roles <membership-id>). The spec and --help already describe each correctly; this is reinforcement only, easy to drop if unwanted.

🤖 Generated with Claude Code

https://claude.ai/code/session_01Ei8UYaG1bW5PJhk93EaqzA

[dspangen]

Codex says:

One minor documentation issue; no functional defects found.

[P3] Remove the remaining obsolete flag reference

cmd/omni/output_test.go:188 still says XLSX is selected with --result-type, although this PR establishes that the flag does not exist. Please update it to reference the query run body’s resultType field so the cleanup is complete.

The nested error extraction itself looks correct and preserves existing fallback behavior. GitHub CI reports both lint and test passing.

[ernestoongaro]

Fixed in f926995 — output_test.go:188 was the last --result-type reference in the repo (grep is now clean); it now reads as the resultType body field like the others.

[ernestoongaro]

Three small things from a full sweep of the CLI against a playground instance.

1. Nested error bodies.{"error":{"code":403,"message":"Invalid bearer token"}} (what a bad token returns) was surfaced as the whole object re-serialised into "error". extractErrorDetail now descends one level into an object-valued detail/message/error key. Before/after:

   "error": "{\"error\":{\"code\":403,\"message\":\"Invalid bearer token\"}}"
   "error": "Invalid bearer token"
   

   Test added; fallback to the raw body is unchanged when no message is found.

2. Docs.CLAUDE.md and an output.go comment referred to a --result-type flag that doesn't exist — CSV/XLSX come from query run's resultType body field.

3. agent-help. The existing "some positionals take a NAME, not a UUID" note gains the other cases that tripped a scripted sweep (delete-branch, labels get, documents add-label, users get-model-roles <membership-id>). The spec and --help already describe each correctly; this is reinforcement only, easy to drop if unwanted.

🤖 Generated with Claude Code

https://claude.ai/code/session_01Ei8UYaG1bW5PJhk93EaqzA

[dspangen]

Codex says:

One minor documentation issue; no functional defects found.

[P3] Remove the remaining obsolete flag reference

cmd/omni/output_test.go:188 still says XLSX is selected with --result-type, although this PR establishes that the flag does not exist. Please update it to reference the query run body’s resultType field so the cleanup is complete.

The nested error extraction itself looks correct and preserves existing fallback behavior. GitHub CI reports both lint and test passing.

[ernestoongaro]

Fixed in f926995 — output_test.go:188 was the last --result-type reference in the repo (grep is now clean); it now reads as the resultType body field like the others.

[ernestoongaro]

Three small things from a full sweep of the CLI against a playground instance.

1. Nested error bodies.{"error":{"code":403,"message":"Invalid bearer token"}} (what a bad token returns) was surfaced as the whole object re-serialised into "error". extractErrorDetail now descends one level into an object-valued detail/message/error key. Before/after:

   "error": "{\"error\":{\"code\":403,\"message\":\"Invalid bearer token\"}}"
   "error": "Invalid bearer token"
   

   Test added; fallback to the raw body is unchanged when no message is found.

2. Docs.CLAUDE.md and an output.go comment referred to a --result-type flag that doesn't exist — CSV/XLSX come from query run's resultType body field.

3. agent-help. The existing "some positionals take a NAME, not a UUID" note gains the other cases that tripped a scripted sweep (delete-branch, labels get, documents add-label, users get-model-roles <membership-id>). The spec and --help already describe each correctly; this is reinforcement only, easy to drop if unwanted.

🤖 Generated with Claude Code

https://claude.ai/code/session_01Ei8UYaG1bW5PJhk93EaqzA

[dspangen]

Codex says:

One minor documentation issue; no functional defects found.

[P3] Remove the remaining obsolete flag reference

cmd/omni/output_test.go:188 still says XLSX is selected with --result-type, although this PR establishes that the flag does not exist. Please update it to reference the query run body’s resultType field so the cleanup is complete.

The nested error extraction itself looks correct and preserves existing fallback behavior. GitHub CI reports both lint and test passing.

[ernestoongaro]

Fixed in f926995 — output_test.go:188 was the last --result-type reference in the repo (grep is now clean); it now reads as the resultType body field like the others.