feat(preflight): extend system readiness checks for wave run wave pre-flight

[nextlevelshit]

Parent: #184

Summary

Extend the existing internal/preflight/ and internal/onboarding/ systems to serve as the system readiness gate for wave run wave. This includes verifying adapter health (binary reachability + authentication), CLI availability for all configured forge types, skill dependencies, and Wave initialization status with last-update reporting. The existing preflight checks validate per-pipeline dependencies; this issue extends them to validate the full system state required for interactive orchestration mode.

Acceptance Criteria

• wave run wave pre-flight validates adapter binary is reachable and authenticated (not just present)
• Pre-flight checks verify CLI availability for all configured forge types (gh, glab, tea, bb) based on detected forge
• Skill dependency validation reports missing skills with actionable install guidance
• Wave initialization status is checked with last-update date displayed
• Pre-flight results are emitted as a structured artifact consumable by downstream pipeline steps
• Clear pass/fail reporting — each check has a status, message, and remediation hint
• Extends existing internal/preflight/preflight.go rather than creating a parallel system
• All existing preflight tests continue to pass (go test ./internal/preflight/...)

Dependencies

None — this is foundational work that other sub-issues depend on.

Scope Notes

• In scope: Extending existing preflight and onboarding systems, adapter health validation, forge CLI checks, skill dependency validation, structured artifact output
• Out of scope: Auto-installation of missing dependencies on the fly (tracked separately in feat: support external dependency installation (slash commands, speckit) in pipeline steps #97), changes to the onboarding wizard UX flow, CI/CD pipeline preflight (feat: dependency preflight checks, onboarding guidance, and CI/CD pipeline support #173 covers that independently)
• Overlap note: feat: dependency preflight checks, onboarding guidance, and CI/CD pipeline support #173 covers CI/CD preflight and onboarding guidance broadly; this issue is specifically about the wave run wave runtime readiness gate

[nextlevelshit]

Revival Update (March 2026)

Audit Findings

The existing internal/preflight/preflight.go already handles:

• ✅ CLI tool availability via exec.LookPath
• ✅ Skill availability and auto-installation
• ✅ Structured []Result with {Name, Kind, OK, Message}

The existing internal/tui/health_provider.go already handles:

• ✅ Git repository status (branch, remote, dirty)
• ✅ Adapter binary availability
• ✅ SQLite database connectivity
• ✅ Wave configuration (persona/adapter/pipeline counts)
• ✅ Required tools and skills scanning from pipeline YAMLs

What's Actually Missing

1. Adapter authentication check — preflight checks if the binary exists, but not if it's authenticated (e.g., claude --version vs actually being able to make API calls)
2. Forge CLI validation — no check for gh, glab, tea, or Bitbucket CLI based on detected forge type (depends on feat(pipeline): auto-detect forge type and propose correct pipeline family #211 forge detection)
3. wave doctor command — no non-interactive health check command that can output JSON for CI/scripting
4. Structured artifact output — health results aren't emitted as an artifact consumable by downstream steps
5. --fix auto-remediation — existing preflight has skill auto-install, but no unified "fix everything" mode

Revised Scope: wave doctor

This should become the wave doctor subcommand (per clig.dev composability principles, see parent issue #184 revival comment):

$ wave doctor              # Human-readable health check
$ wave doctor --json       # Machine-readable for CI
$ wave doctor --fix        # Auto-install missing deps

Exit codes: 0 = healthy, 1 = issues found (non-critical), 2 = critical failures.

Revised Size: S (was M)

Most of the infrastructure exists. This is primarily:

1. Wiring existing preflight + health_provider checks into a new wave doctor command
2. Adding adapter auth validation
3. Adding --json + meaningful exit codes
4. Adding --fix mode leveraging existing skill auto-install

Previous Implementation Attempt

PR #215 was closed without merging. Start fresh.

[nextlevelshit]

Implementation Update (March 2026)

Current status: Being implemented

Active session has implemented the core wave doctor command:

• internal/doctor/doctor.go — RunChecks() with system health checks (Wave init, adapter, forge CLI, tools, skills)
• internal/doctor/codebase.go — forge-aware codebase analysis (PRs, issues, CI via gh/glab/tea)
• internal/doctor/scan.go — pipeline YAML scanning for required tools/skills
• cmd/wave/commands/doctor.go — CLI with --fix, --json, --skip-codebase, exit codes 0/1/2

Scope expansion: #296

The new #296 (AI-steered project optimization) extends wave doctor with --optimize for deep project analysis and AI-powered wave.yaml generation. This issue's original scope (system readiness checks) is being delivered; #296 adds the project customization layer on top.

Previous attempt

PR #215 was closed without merging. Fresh implementation underway — no code from that PR was reused.