[claude-for-timatic]

GetIssueRequest now maps its own response to a typed JiraIssueDetails DTO (issue, comments, status changes), so TicketProvider::fetchTicketDetails() no longer parses raw JSON and the request loses its response-dto architecture exemption.

Closes #38

Decisions

• Reused JiraIssue, JiraComment and JiraChangelogEntry: their fields already matched the response, so the only new class is the JiraIssueDetails wrapper.
• Test first: no test covered fetchTicketDetails, so tests/Integration/Jira/TicketProviderTest.php was committed before the refactor to pin the old output (rendered comments, blank comment dropped, only status changelog items, historyId-itemIndex ids, 404 → null).
• No change to the architecture test file: tests/Architecture/ArchitectureTest.php from the issue no longer exists. The exemption was the @arch-ignore response-dto marker on the request, which is now removed.
• Mapping is written inline in createDtoFromResponse(), the way GetIssuesRequest does it, not in private helpers.
• The 404 check stays in TicketProvider, before ->dto(), so a 404 still returns null.

Review

A code-review agent found no blockers. Two optional nits are left out on purpose:

• Building JiraIssue repeats code from GetIssuesRequest. Nothing on our DTOs shares construction like this yet.
• Existing behaviour, kept as is: a comment with no rendered body falls back to the raw ADF array, and trim() throws on it.

Docs

Nothing in the domain docs (#96) changes.

Verification

Full Pest suite green, PHPStan 0 errors, Pint clean.