Pipeline Plan 4

The --json flag for shipwright status is already fully implemented. Here's the summary:

Implementation (scripts/sw-status.sh:57-267):

• --json flag parsing with --help documentation
• Collects all 11 data sections: version, timestamp, tmux_windows, teams, task_lists, daemon, issue_tracker, heartbeats, remote_machines, connected_developers, database
• Uses jq for safe JSON construction throughout
• Human-readable output is completely bypassed when --json is set (exit 0 on line 266)

Tests (scripts/sw-status-test.sh): All 30 tests pass, covering:

• Valid JSON output
• All top-level keys present
• Fixture data correctness for every section
• No ANSI escape codes in JSON
• Empty state produces valid JSON
• Human-readable output still works without --json
• Subsection queries work (e.g., jq '.daemon.active_jobs[].issue')

All acceptance criteria from issue #4 are met. No code changes are needed — the pipeline can proceed directly to PR.