v2.69.0 — VS Code configPath setting

VS Code: explicit config path

A new fallow.configPath setting points the VS Code extension at an explicit Fallow config file, mirroring the CLI's --config flag. Useful when your config lives outside the workspace root, when you want different VS Code workspaces sharing one config file, or when you want auto-discovery off entirely.

// .vscode/settings.json
{
  "fallow.configPath": "configs/fallow.jsonc"
}

Behavior:

• Empty (default) keeps the existing auto-discovery (.fallowrc.json > .fallowrc.jsonc > fallow.toml > .fallow.toml).
• Absolute paths pass through unchanged.
• Relative paths resolve against the workspace root (the first folder in multi-root workspaces) before being forwarded to the LSP via initializationOptions.configPath and to the CLI via --config <path> for analyze and fix commands.
• Changing the setting restarts the LSP and re-runs the sidebar analysis, no reload window required.
• A broken configPath (typo, missing file, parse error) now surfaces as a WARNING-level notification including the path, instead of silently producing zero diagnostics.

Two new public fallow_core entry points (config_for_project and analyze_project_with_config) let other programmatic embedders request an explicit config the same way.

Thanks @FunctionDJ for asking in #314.

Full Changelog: v2.68.0...v2.69.0