v16.3.0

What's Changed

New Features

• New rulesync doctor command — read-only diagnostics for your configuration files (rulesync.jsonc / rulesync.local.jsonc), reported by severity (error / warning / info) by @dyoshikawa in #2491
  • Detects unknown or misspelled configuration keys with "did you mean" suggestions — previously these were silently ignored and generation quietly fell back to defaults
  • Validates tool targets and features (array and object forms) with nearest-name suggestions, and warns on the deprecated ignore feature
  • Reports JSONC parse errors with line/column, conflicting target pairs, object-form targets combined with features (including conflicts that only appear after merging rulesync.jsonc with rulesync.local.jsonc), $schema presence and currency, malformed sources entries, unset sources[].tokenEnv environment variables, and a nonexistent inputRoot
  • Exits with code 1 when errors are present; --strict makes warnings fatal for CI
  • Honors the global --json flag: diagnostics and a severity summary are emitted in data on success and in error.details (code DOCTOR_FAILED) on failure
• CLIError now carries an optional structured details payload that is propagated into the JSON error document, so --json consumers keep machine-readable context on failure

Documentation

• Added a Doctor Command reference section and a troubleshooting FAQ entry recommending rulesync doctor as the first step when generation does not behave as expected

Contributors

• @dyoshikawa

Full Changelog: v16.2.0...v16.3.0