add: persistent tasks source pref. and runner.toml lsp

[kjanat]

Two related changes: a persistent way to choose which source runs an ambiguous task, and an editor language server that surfaces config validation/docs.

[tasks] — persistent task-source preference

A task name can exist under more than one source (e.g. a package.json script and a turbo task). Previously the only way to pick the winner was per-invocation (package.json:build, --pm bun, --runner turbo); the only file knob, [task_runner].prefer, accepted task runners only (not package managers) and restricted candidates — so prefer = ["turbo"] hard-rejected a package.json script instead of ranking it.

New [tasks] section:

[tasks]
prefer = ["turbo", "bun"]                  # rank-only global order: turbo, then package.json (bun)

[tasks.overrides]
dev   = "bun"                              # per-task pins beat the global order
build = "turbo"

• [tasks].prefer — rank-only global order. Labels may be task runners, package managers (bun/npm/… → package.json; deno → deno.json then package.json), or source names. Never hard-rejects an unlisted source — it only reorders ties.
• [tasks.overrides] — per-task pins that beat the global order for specific names.
• Both ride the existing select_task_entry/source_priority machinery, so an explicit source:task qualifier, --runner, or --pm/RUNNER_PM still outranks the file.

Deprecates [task_runner].prefer in favour of [tasks].prefer: existing configs keep working (with their original restrictive behaviour) and now emit a migration warning; when both are set, [tasks] wins. The key is flagged "deprecated": true in the committed JSON Schema and dropped from the config init scaffold.

runner lsp — language server for runner.toml

Built with --features lsp (gated like man/schema), exposed as runner lsp over stdio. Reuses the CLI's own internals so editor feedback can't drift from runner itself:

• diagnostics — the exact runner config validate pipeline (TOML parse, unknown keys, resolver field/policy validation) plus deprecation hints, mapped to buffer ranges and tagged DEPRECATED where appropriate;
• hover — section/field docs sourced from the generated JSON Schema (the RunnerConfig doc comments — single source of truth);
• completion — section names, field names, and value sets (schema enums plus the code-driven [tasks] runner/PM/source label vocabulary and booleans).

runner lsp is intercepted before project detection / config load, so it starts even when the on-disk file is currently invalid — exactly when its diagnostics matter most. The server is small and synchronous (full-text sync, one tiny document at a time). New deps (lsp-server, lsp-types) and the lsp module are feature-gated; default builds are unchanged. To enable reuse, config::collect_unknown_keys, config::deprecation_warnings (factored out of config::load), and cmd::schema::config_schema are now pub(crate).

Testing

• New unit tests for selection ranking, per-task pins, precedence, label parsing, the deprecation warning, and every LSP feature (diagnostics severities/tags/ranges, hover, completion contexts, position mapping).
• Full suite green under --all-features; clippy clean (--all-features and default, -D warnings); cargo fmt + dprint clean; JSON Schema regenerated with no drift.
• Manual end-to-end checks: ranking flips with [tasks].prefer, pins override the order, legacy [task_runner].prefer still works with a deprecation warning; and the LSP binary driven through a real stdio session emits correctly-anchored diagnostics and hover, with a clean shutdown.

Notes

• v1 of the LSP is scoped to runner.toml. Natural follow-ups: project-aware completion of real task names for [tasks.overrides] keys, and hover/diagnostics in task files (justfile/package.json).

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Preview URL	Updated (UTC)
✅ Deployment successful! View logs	runner	4e3a4f5	Commit Preview URL Branch Preview URL	Jul 01 2026, 05:53 PM

[coderabbitai]

Important

Review skipped

Auto reviews are limited based on label configuration.

🏷️ Required labels (at least one) (1)

• cr:review

🚫 Excluded labels (none allowed) (2)

• wip
• cr:skip

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: fdc67bde-45ea-4133-aa6b-9363407410c0

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

📝 Walkthrough

Walkthrough

This PR adds a feature-gated runner lsp stdio language server for runner.toml, with hover, completion, diagnostics, and schema-backed text anchoring. It also introduces a persistent [tasks] configuration section with global prefer ordering and per-task overrides, while deprecating [task_runner].prefer and wiring the new preferences through config loading, resolver parsing, task selection, schema generation, and docs.

Estimated code review effort: 5 (Critical) | ~120 minutes

Sequence Diagram(s)

sequenceDiagram
  participant Editor
  participant runner_lsp as runner lsp
  participant Diagnostics
  participant Resolver
  participant SchemaIndex

  Editor->>runner_lsp: didOpen / didChange runner.toml
  runner_lsp->>Diagnostics: compute(text, index)
  Diagnostics->>Resolver: validate_config(config)
  Resolver-->>Diagnostics: diagnostics result
  Diagnostics-->>runner_lsp: publishDiagnostics payload
  runner_lsp-->>Editor: publishDiagnostics notification

  Editor->>runner_lsp: hover / completion request
  runner_lsp->>SchemaIndex: look up section/field docs
  SchemaIndex-->>runner_lsp: schema-backed hover/completion data
  runner_lsp-->>Editor: Hover / CompletionItem[]

Loading

Possibly related PRs

• kjanat/runner#22: Touches the same resolver and task-selection pipeline that now consumes [tasks] preferences and overrides.
• kjanat/runner#71: Also changes same-name task ranking and forced-source precedence in src/cmd/run/select.rs.

Suggested labels: enhancement, documentation, area: cli

Poem

Ahoy, the config stopped wobblin’ at last,
And the LSP now speaks fast.
Deprecated keys can sulk in the foam,
While hover and completions find home.
Cheers, the bloody thing is cleaner now.

🚥 Pre-merge checks | ✅ 7 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Semver Version Bump Validation	⚠️ Warning	Source code changed, but Cargo.toml stayed 0.15.0 on both master and HEAD; this feature batch is backward-compatible, so a MINOR bump is required.	Bump Cargo.toml to the next MINOR (e.g. 0.16.0) and keep any other version file in sync.

✅ Passed checks (7 passed)

Check name	Status	Explanation
Description check	✅ Passed	The description directly covers the new tasks preference system and runner.toml language server.
Docstring Coverage	✅ Passed	Docstring coverage is 100.00% which is sufficient. The required threshold is 30.00%.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Changelog Update	✅ Passed	PASS: source files changed and CHANGELOG.md was updated under [Unreleased] with Added/Deprecated entries; no version bump is present in Cargo.toml.
Agents.Md Documentation Updated	✅ Passed	No AGENTS.md exists anywhere in the repo, so there was naught to update despite the CLI/LSP/config changes.
Title check	✅ Passed	The title clearly matches the PR’s two main additions: persistent tasks source preferences and the runner.toml LSP.

---

_{Comment @coderabbitai help to get the list of available commands.}

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	cargo/​lsp-types@​0.97.0
	cargo/​lsp-server@​0.8.0

View full report

[kjanat]

Follow-up issue for Rust state duplication / schema drift cleanup: #77