docs(troubleshooting): add developer error troubleshooting and diagnosis playbook (#107)

[showmemercy19-rgb]

Adds developer troubleshooting playbook.

[github-actions]

All applicable PR CI workflows passed for 1e5b958.

• ci
• security

Ready for maintainer code review.

[armstrongsam25]

Thanks for contributing. I reviewed the full diff against current main and the LETS constitution.

The complete troubleshooting playbook only names RequestConflictError and timeout cascades. It gives users no symptoms, diagnosis or safe resolution. Please document actual typed SDK/server error codes and recovery steps with source references, especially reusing the original request_id/content after a lost reply versus rejecting changed content, and expiry/cancellation behavior. Include concrete examples and avoid recommending retries that duplicate effects or widen authority.

Please expand this into complete, source-backed documentation before merge (constitution XI and XII). This head contains no measurable executable lines, so changed-line coverage is not applicable; that should be recorded explicitly in the PR. No tests or candidate code were executed during this review.

[armstrongsam25]

Closing after source-based triage of head 1e5b958. The claimed troubleshooting playbook only names request conflicts and lease timeout cascades. It provides no symptoms, diagnostic steps, error mapping or safe resolution, so it adds no actionable troubleshooting outcome.

Evidence: actual typed error mapping; existing retry identity guidance; entire submitted playbook.

Triage criterion: unsupported-completion. Closing this unmerged PR does not close an unfulfilled task, delete the contributor branch, or award bounty points. A distinct substantive revision may be reviewed after reopening.