v0.10.0

Added

• mise task extraction and dispatch. mise was previously
  detection-only — runner listed it under "Task Runners" but its
  tasks were invisible to runner list and runner run <task>.
  New TaskSource::MiseToml makes mise a first-class source: tasks
  declared in mise.toml / .mise.toml (and the *.local.toml,
  mise/config.toml, .config/mise.toml companions in mise's
  documented precedence) appear in listings, participate in the
  selection priority, and dispatch via mise run <task>.
• Bacon-style two-tier extraction for mise. Primary path shells
  out to mise tasks --json — authoritative across mise's config
  layering and file-based tasks (mise-tasks/*); fallback parses
  the first project-local config when mise isn't on $PATH.
  Both paths exclude hidden tasks (hide = true),
  underscore-prefixed names, and tasks whose source lives
  outside the project root (so global / ~/.config/mise/* tasks
  don't pollute the project's task list). Empty or
  whitespace-only description = "" values are treated as
  missing so the renderer falls through to the run body or
  file reference instead of showing a blank column. Aliases
  come through as separate entries pointing at their target,
  mirroring the justfile shape.

Fixed

• Resolver no longer dispatches through a Node package manager in
  projects with no Node-ecosystem evidence (#23). runner run <unknown-task> in a Go-only repo with bun installed used to
  warn "no node signals matched" and then run bun <task> anyway;
  the FallbackPolicy::Probe PATH probe now requires a
  package.json (or equivalent manifest) somewhere upward of
  ctx.root before it considers the canonical Node order.
  Without that evidence the resolver returns the existing soft
  NoSignalsFound sentinel and cmd::run::run_pm_exec_fallback
  spawns the target directly on $PATH — no more wrong-ecosystem
  dispatch.

What's Changed

• resolver: skip Node PATH probe in non-Node projects by @kjanat in #24

Full Changelog: v0.9.0...v0.10.0