[Docs]: Label taxonomy cleanup, new area labels, and issue template updates (#29)

[rosspeili]

Doc location

• .github/labels.yml - .github/workflows/sync-labels.yml - .github/ISSUE_TEMPLATE/feature.yml - .github/ISSUE_TEMPLATE/voice-lip-sync.yml - docs/development/roadmap.md (label references, if any) - New or updated: docs/development/labels.md (or CONTRIBUTING section — implements [Docs]: Label usage guide for triage consistency #29)

What kind of change?

Other

What’s wrong or missing?

Temporal future:* labels (future:agent-bus, future:keyword-triggers) were useful before shipping, but they force relabeling when work starts or finishes. Labels should describe stable product areas and type, not roadmap phase. Open issues still tagged future:* need migration before those labels are removed.

#29 asked for a label usage guide for triage — this issue is the implementation ticket (guide + labels.yml + template YAML updates).

Suggested fix (optional)

Remove (after migrating open issues):

Label	Replace with
future:agent-bus	area:agent-bus
future:keyword-triggers	area:agent-bus

Run sync workflow after editing labels.yml. Relabel issues via GitHub search (label:"future:agent-bus").

Add (predicted from roadmap + recent issues):

Label	Color	Description
area:agent-bus	E0E8F5	Local agent bus, MCP, external API, keyword triggers
area:expressions	F0E8F5	VRM facial expressions beyond lip sync (#43)
area:motion-deck	F5D8E8	Animation hotkeys / Motion Deck UX (#24, #51)
area:thumbnails	E8F0E8	Avatar/env/VRM preview tiles (#21)
area:docs-site	F5F0D8	Docs layout, screenshots, visual overhaul (#33)

Do not add priority, release/version, or time-boxed labels — use GitHub Projects / milestones instead.

Update descriptions: area:lip-sync (reactive live dot #42); security-privacy (cross-link SECURITY.md / #26).

Issue template updates:

• feature.yml — rename surface “Agent / external triggers (roadmap)” → “Agent / external triggers”
• voice-lip-sync.yml — live dot dropdown: Waiting / Live / Error ([Feature]: Reactive glass-bar live dot (amplitude + capture status colors) #42)
• avatar-vrm-animation.yml — optional note for custom .vrma folder ([Feature]: Custom animations folder in Settings → Directories (.vrma) #23/feat(animations): custom .vrma folder in Settings → Directories #45) if triage shows confusion
• Defer dedicated agent-bus.yml until more bus issues accumulate

Label usage guide (docs/development/labels.md):

1. Type — one primary (bug, feature, documentation, question, regression)
2. Area — one or two max (area:*); add platform:* only when stack is the whole issue
3. Status — optional (needs design, needs info, …); remove when resolved
4. Never temporal labels

PR checklist: update labels.yml + templates; close or comment on #29 when merged; relabel pass on open issues.

Checklist

• I searched existing issues for a duplicate