Build animation action registry for movement, dialogue, hit, attack, death, and weapon stance

[JOY]

Summary

Create a gameplay-facing animation action registry so code does not call raw Animator state names directly.

Scope

• Define action ids for idle, walk, run, talk, attack, hit reaction, death, interact, gather, and weapon stance.
• Map action ids to available animation controller parameters or states per weapon/body capability.
• Hide or lower weapons during talk/interact when the body supports it.
• Provide safe fallback animations when a pack lacks a clip.

Acceptance Criteria

• Gameplay code requests semantic actions, not raw animation state names.
• Dialogue mode uses talk or neutral idle instead of combat-ready stance when available.
• Movement resumes promptly after exiting dialogue.
• Missing animation capability falls back gracefully and logs a compact warning.
• Unity Play Mode smoke covers movement, talk, attack, hit reaction, and death placeholder actions.

References

• docs/setup/unity-conventions.md
• ROADMAP.md

[JOY]

Implemented a scoped #146 animation registry polish pass on dev:

• Added semantic VisualAnimationIntent ids for Idle, Walk, and Run so gameplay/debug code has first-class action ids instead of inventing raw state names later.
• CharacterAnimationRegistry resolves the new locomotion ids through the shared idle fallback path for the current weapon style.
• VisualAnimationIntentDriver now emits one compact fallback warning per missing/unsupported animation contract instead of failing silently.
• Dialogue/talk intent now counts as handled when the Animator exposes the Talking or Weapon contract even if a specific talk state is missing, so talk mode can still relax the stance and lower weapons gracefully.
• Updated CHANGELOG.md.

Local review fallback: APPROVED WITH SUGGESTIONS. No blocking architecture issue found. This keeps gameplay using semantic VisualAnimationIntent ids, with raw Animator state names isolated in CharacterAnimationRegistry. Remaining production work is to move locomotion blend parameter writing fully behind the same contract once the shared controller is finalized.

Verification run:

• npm test in backend/nakama: pass
• npm run build in backend/nakama: pass
• markdownlint for public docs: pass
• git diff --check: pass
• touched-file em-dash scan: pass
• tools/windows/check-local-health.ps1 -Strict: pass exit; Unity compile OK, Editor.log tail clean, Nakama/Postgres OK, MCP 8080/8766 listening.

[JOY]

Implemented and merged in PR #169. Evidence: lint passed, local code-review fallback passed, root Unity compile/import completed with no C# errors, and a Play Mode smoke ran with no console errors. The only remaining warning is the known Visual Studio UDP messaging warning.