Expressive command lifecycle: restore, curate and integrate 600+ activity pairs #362

Goal

Bring back NMSh's playful command activity vocabulary without compromising truthful execution state. This is not yet implemented: a data-only draft branch exists, but lifecycle routing, settings, persistence and physical QA remain.

Provenance and current state

• Original 261 pairs: src/status/activityVerbs.ts at commit 982f6a37; removed by PR #29 to make lifecycle observations factual.
• Draft branch: feature/expressive-activity-vocabulary, commit 504f2b3, built on #361. It currently contains 679 candidate pairs only; these have not been fully edited or connected to the app. Verify branch freshness before touching it.
• PR feat(ui): factual milestone rows replacing random verbs #29's factual failure codes, timing and interruption semantics must stay.

Behavior

• Expressive (default) and Classic setting, within existing Activity/Appearance controls. Settings normalize/migrate, persist, export and import.
• Choose an active/completed pair once per command; preserve the choice through redraws, folding, scrolling and, where relevant, session restoration/reattachment.
• Successful: Cooking… → Cooked for 18s · done 14:46. Failed, interrupted and awaiting-input states stay unmistakable with real exit codes/timing.
• Vary the vocabulary without repeated adjacent selections; avoid expensive random selection on every render. Factual machine-readable status, reports and copy data never depend on decorative phrases.
• Curate to at least 600 meaningful, distinct, grammatically correct pairs. Remove awkward invented phrases, near duplicates, misleading outcome claims (Verified, Installed without evidence), and irregular-conjugation errors. Count alone is not quality.
• Respect short layouts, reduced motion, NO_COLOR, Safe glyphs, managed sessions and input ownership.

Acceptance

• Audit historical and draft dictionaries; document selection/exclusion rules, confirm 600+ reviewed pairs.
• Add stable lifecycle selection and style setting without competing execution state.
• Preserve facts, failures, interrupts and input-wait displays; support transcript/resume behavior honestly.
• Unit/integration/real-PTY tests plus representative narrow/host captures.
• Document dependencies and reviewable PR on the current workflow stack; no merge/release before approval.

Related: #359 terminal workflow, #361 current branch base.