feat!: write-through to Jira by default

[sthadka]

Summary

• jai set, jai comment: now push changes to Jira immediately instead of queuing locally. Errors surface at command time, not at jai push time.
• jai transition: calls ExecuteTransition directly instead of queuing then calling ProcessQueue (which had the surprising side effect of pushing ALL queued changes).
• TUI inline edit: writes through via background tea.Cmd; falls back to queue on API error.
• --queue / -q flag added to all three commands to preserve the old queue-first behavior.
• AddComment now returns (string, error) so write-through comments get real Jira IDs instead of synthetic local_* IDs.
• JSON output "status" field changes from "pending" to "synced" (write-through) or "queued" (with --queue).

Breaking Changes

Before	After
jai set queues locally, needs jai push	jai set pushes to Jira immediately
jai comment queues locally	jai comment pushes to Jira immediately
jai transition pushes ALL queued changes	jai transition pushes only the transition
Works offline (deferred push)	Requires network (use --queue for offline)
JSON status: "pending"	JSON status: "synced" or "queued"

Migration

Add --queue / -q to any scripts that relied on the old queue-first behavior:

# Before (implicit queue)
jai set ROX-123 priority High
jai push

# After (explicit queue)
jai set ROX-123 priority High --queue
jai push

Test plan

• go build -tags fts5 ./... — clean build
• go test -tags fts5 ./... — 258 tests pass
• Manual: jai set <key> priority Minor pushes immediately (staging, 19/19 tests pass)
• Manual: jai set <key> priority Major --queue queues for push
• Manual: jai comment <key> "test" posts immediately
• Manual: jai transition <key> "In Progress" transitions immediately
• Manual: jai set <key> labels --add/--remove array ops push immediately
• Manual: TUI field edit saves via API (not tested — requires interactive session)