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

Inizia dallo schema delle attività in crates/vite_task_graph/run-config.ts e confronta la struttura esistente basata solo sui comandi con i metadati proposti. Chiarisci il comportamento per l’elenco, l’output, la risoluzione degli alias, i conflitti e l’ordinamento dei gruppi prima di scegliere l’ambito dell’implementazione. Il lavoro è completato quando i metadati concordati sono supportati senza modificare il comportamento delle attività che li omettono, con una copertura per l’MVP selezionato.