TDD Assessment

What's covered

The Edited struct and its wire-format deserialization are adequately tested in internal/client/client_test.go (TestClient_GetThreadReplies_WithEdited):

• edited message correctly populates Edited.User and Edited.TS
• unedited message correctly leaves Edited as nil
• the omitempty tag on Edited is exercised implicitly

Gaps

No command-level tests for the [edited] text indicator.

Both history.go and thread.go got the same [edited] rendering logic, but messages_test.go has zero coverage of it. The existing TestRunHistory_Success and TestRunThread_Success tests only assert require.NoError — they don't capture or inspect output.Printf output at all. There are no new tests that:

1. Verify [edited] appears in text output when Edited != nil (for either runHistory or runThread)
2. Verify [edited] is absent when Edited == nil
3. Verify the Edited field is present in JSON output for runHistory — the TestRunHistory_JSONIncludesReactions pattern is the right model but was not replicated for the edited case

Precedent exists for this style of test. TestRunThread_JSONIncludesReactions and TestRunThread_JSONIncludesFiles both capture JSON output and assert on field values. TestRunHistory_JSONIncludesReactions does the same. That same pattern should cover Edited in JSON output and should be mirrored by a text-output test that checks the captured buffer for the literal [edited] string.

JSON serialization

The Edited struct uses json:"user" and json:"ts" (no omitempty). This means a zero-value Edited{} would serialize as {"user":"","ts":""} rather than being omitted. However, because the field on Message is a pointer with omitempty, a nil pointer is omitted correctly. The only risk is if an upstream response sends "edited": {} — the struct would be non-nil but with empty strings. This edge case is untested and low-priority, but worth noting.

Verdict

Client-layer deserialization is well tested. The command-layer rendering of [edited] in both text and JSON output has no test coverage. Two tests should be added following the existing TestRunHistory_JSONIncludesReactions / TestRunThread_JSONIncludesReactions pattern — one for each command — covering both the presence and absence of [edited].