Improve issue close/reopen/delete output to show number, title, and support --json #14

Context#

During dogfooding (issue #3), it was noted that tangled issue create shows an opaque AT Protocol TID instead of the human-readable sequential issue number in its output (tracked in issue #8). The same problem likely affects tangled issue close and tangled issue reopen, which confirm the action but may not echo back enough context to confirm which issue was affected.

For example, after running tangled issue close 4, the ideal output is:

✓ Issue #4 closed
  Title: PR Phase 1: Create, List, and View Pull Requests

This makes it unambiguous that the right issue was acted on, without requiring a follow-up issue view or issue list call.

Tasks#

• Update tangled issue close <n> output to include the sequential issue number and title in the confirmation message.
• Update tangled issue reopen <n> output to include the sequential issue number and title in the confirmation message.
• Ensure the same applies to tangled issue delete <n> for consistency.
• Add --json [fields] output to issue close, issue reopen, and issue delete, returning at minimum number, title, uri, and state — consistent with the --json pattern on other issue commands.
• Add or update tests to verify the number and title appear in the confirmation output, and that --json returns the expected fields, for each command.

Notes#

Related to issue #8 (same gap in issue create) and issue #13 (--json for issue create). Should be straightforward since issue close/reopen already accept a sequential number as input — the title and number are available at the point the record is fetched.