Bug: cannot read trace details by trace id

[clark-cant]

Summary

Reading detailed trace content by trace id does not work in goclaw-cli.

Problem

The CLI can list or reference traces, but attempting to fetch/read the detailed content of a specific trace by id fails or returns unusable output.

This may be a CLI-side issue, or the underlying API response from the GoClaw server may be missing/broken. If the root cause is server-side, a corresponding fix may be needed in digitopvn/goclaw.

Expected behavior

Given a valid trace id, the CLI should return the full trace details in a useful format, including relevant metadata, root/child events, messages, tool calls, status, timing, and errors where applicable.

Actual behavior

Trace detail lookup by id does not work reliably.

Things to investigate

• Which CLI command is intended for reading a trace by id.
• Whether the CLI is calling the correct API endpoint.
• Whether the API endpoint returns the expected trace payload.
• Whether trace id vs run id vs root id are being confused.
• Whether JSON/table output formatting is dropping nested trace content.
• Whether server-side auth/tenant/user filtering hides the requested trace.

Acceptance criteria

• goclaw-cli can read trace details by id.
• Output works in JSON and human-readable modes.
• Errors clearly distinguish: not found, permission denied, malformed id, and server/API failure.
• If API is the root cause, document/link the server-side issue in digitopvn/goclaw.
• Add regression test or smoke test for trace detail lookup.

[mrgoonie]

Fixed in PR #20 (targets dev). The Closes #17 reference will auto-close this issue when dev is promoted to main in a follow-up /ck:ship official run. If you need it closed sooner, close manually after PR #20 merges to dev.