Proposal: task metadata (description) + aliases/groups for discoverability at scale

Problem

As task count grows, discoverability becomes a major UX issue.
just provides aliases and groups; it also has strong listing/help UX. Vite Tasks appears command-centric and does not expose first-class description/alias/group metadata in the task schema (based on the public schema file).

Evidence (primary)

• Task schema appears centered around command without rich metadata fields.

Ref:

• https://github.com/voidzero-dev/vite-task/blob/main/crates/vite_task_graph/run-config.ts

Proposed behavior (Unspecified)

• Add optional fields:
  • description?: string
  • aliases?: string[]
  • group?: string
• Display description/group in task listing and error messages.
• Allow running a task via any alias, with clear conflict handling (unspecified).

Use cases

• Provide “human intent” descriptions for tasks (deploy, release, verify, etc.)
• Create short entry points via aliases
• Organize tasks into groups (lint/test/build/release) for large monorepos

Backward compatibility

• Purely additive; tasks without metadata behave exactly the same.

Minimal implementation suggestion (MVP)

• Implement description first and show it in listings/output.
• Add aliases resolution later, then group sorting/printing.

Prior art

• just aliases: https://just.systems/man/en/aliases.html
• just groups: https://just.systems/man/en/groups.html

Start with the task schema in crates/vite_task_graph/run-config.ts and compare the existing command-only structure with the proposed metadata. Clarify the behavior for listing, output, alias resolution, conflicts, and group ordering before choosing an implementation scope. Done means the agreed metadata is supported without changing behavior for tasks that omit it, with coverage for the selected MVP.