Actor renders as a small floating hand/glove in tavern_snug (mesh-binding family)

[100yenadmin]

Seen on walk4 (2026-07-22, user-truth app, adventure fixture): in tavern_snug one actor renders as a tiny disembodied hand/glove sprite floating over its marker ring near the barrels (left of the post), while a correctly-rendered humanoid stands by the bar. Two tokens present in the room (Aidan player + Keeper Maera npc) — one of the two is mis-bound. Same family as the #1616 T-pose/hero.fbx fallback class (name->model resolution / mesh binding), new manifestation. User-truth P2 for demo gate G4. Frame: /Volumes/LEXAR/Codex/session-notes/2026-07-22/cast-presence-1639/artifacts/walk4/shot_to_tavern.png

[evaos-code-review-bot]

evaOS issue enrichment

Issue: #1666 - Actor renders as a small floating hand/glove in tavern_snug (mesh-binding family)
State: open

Related issues/PRs: #1616.
Existing labels: none.
Suggested labels: security, tests.
Suggested owners: none.

Related context

• client: runtime-spawned actors bind the animated roster setup (T-pose fix, #1601) #1616 - mentioned in issue metadata; inspect for dependency, duplicate, or prior-decision risk.

Agent-start packet

Problem shape: Actor renders as a small floating hand/glove in tavern_snug (mesh-binding family) - Seen on walk4 (2026-07-22, user-truth app, adventure fixture): in tavern_snug one actor renders as a tiny disembodied hand/glove sprite floating over its marker ring near the barrels (left of the post), while a
Product fit: Implementation issue; keep product fit lightweight unless VISION.md/repo policy raises a constraint.
Implementation wedge: Start with a focused fixture or dry-run path that proves the issue shape before widening behavior.

Build / borrow / buy scan:

• Build: identify the smallest implementation wedge that proves the issue without broad rollout.
• Borrow: inspect same-repo prior art, repo memory, GitNexus context, and allowlisted cross-repo examples first.
• Buy/use: deferred; no product, architecture, UX, library-choice, integration, roadmap, or market-positioning trigger detected.

Candidate sources:

• VISION.md / repo policy / repo-memory.md / GitNexus packet.
• Same-repo issues and PRs referenced by issue metadata.

Acceptance criteria:

• Add explicit acceptance criteria before implementation is considered done.
• Include source citations for any external OSS/library/current-market claims.
• Keep issue-enrichment comments sticky and idempotent.
• Keep labels, owners, reviewers, and roadmap fields suggestion-only.

Proof plan:

• Focused unit/fixture test for the changed planner behavior.
• Dry-run issue-enrichment evidence packet before live comment posting.
• Redaction check for issue body, citations, and generated markdown.

Known traps:

• Do not treat related links as proof by themselves; each source needs a reason why it matters.
• Do not scan old issue backlogs or exceed repo-level enrichment throttles.

Non-goals:

• Do not auto-apply labels, owners, reviewers, roadmap fields, or milestones.
• Do not bulk-enrich old backlog issues from this planner output.
• Do not claim external market or OSS research was performed unless cited sources are present.

Context-source taxonomy:

• [enabled] vision_repo_policy_memory_gitnexus: Use repo vision, policy, memory, and GitNexus first before external research.
• [enabled] same_repo_issues_prs: Issue metadata contains same-repo references.
• [deferred] allowlisted_cross_repo_github: Deferred until product, UX, market-positioning, or library-choice signal appears.
• [deferred] external_oss_examples: Deferred for low-research-value issue class.
• [deferred] library_api_docs: Deferred unless a library/API decision is present.
• [deferred] current_market_examples: Deferred for implementation-only issues.
• [enabled] internal_mcp_docs: Use internal docs/MCP context when available; missing context is degraded, not blocking.

Validation suggestions

• Confirm owner, acceptance criteria, and validation evidence before implementation.

Triage gaps

• Acceptance criteria or validation evidence not detected in issue body.
• Owner or reviewer signal not detected in issue body.

No labels, owners, reviewers, or roadmap fields were changed by this bot.

[100yenadmin]

Escalation + second occurrence (eyeball, 2026-07-22 ~18:06): the floating hand/glove reproduces in the CRYPT on the player_cert live evidence frame (cert_green/shot_sil_behind.png in LEXAR session-notes 2026-07-22/player-cert-live/artifacts/) — a hand sprite floats over the west wall while NO full party figure renders anywhere in frame (two goblin tokens render fine). The mis-bound actor is likely the PLAYER character, not an NPC — if so this is a P1 (the party can be invisible-but-for-a-hand in any room). Also flags the in-flight player_cert silhouette assert: if it passed GREEN on this frame, the assert may be measuring pixels that belong to the broken mesh — review the assert's method before crediting.

[100yenadmin]

g4-build cert frame (eyeball, post-#1676): the defect has TWO scopes and only one is fixed-path. In the crypt fixture (party + 3 goblins): the party actor now renders correctly (visible as the teal walk-behind silhouette in the cert frame — the #1674 shader fix working), TWO goblins render full-figure and grounded, but the THIRD goblin still renders as a floating fragment (now foe-red-tinted, over the west stairs). The #1676 height guard is character-scoped by design ('monsters legitimately vary in size') — so a degenerate MONSTER bind is uncovered. Fix shape: extend the guard to monsters with a lower floor (~0.3m — even a small goblin exceeds it; the fragment is ~0.2m). Also confirms the snug case was the CHARACTER path. Frame: LEXAR session-notes 2026-07-22/g4-build/artifacts/cert_g4/shot_sil_behind.png

[100yenadmin]

g5 forensics — the residual is a PER-INSTANCE failure, not an alias/registry bug: all three crypt monsters are the SAME token name/model ('Goblin Warrior 1/2/3'); two render full-figure, one (always the instance at (1,1) — the first spawn) renders as fragments. No degenerate-bind log fired (raw bounds full-height → guard passes, the flagged render-coverage case). Hypothesis: spawn races the actor-bundle load — the first instance binds mid-load, body renderers never enable, only an accessory mesh draws. Fix shape: defer monster spawn until bundle-ready (or re-enable renderers on load-complete callback), + the render-coverage guard (count enabled body renderers vs expected). Repro: seed adventure fixture at crypt, first goblin fragment every boot (3/3 boots today). Frame: LEXAR .../g4-build/artifacts/crypt_g5.png. NOTE: absent from the owner's walkslice world (no monsters seeded) — g5 installed there with this open.