Runtime monster tokens render unintegrated: Goblin Boss oversized, slightly floating, no scene light tint

[100yenadmin]

Seen on the first walked-arc GREEN (walk4, 2026-07-22): the throne_hall Goblin Boss token (#1662) renders but reads unintegrated — model spans ~2x the throne height, feet hover ~half a cell above its marker ring, and it carries no warm scene tint (pale flat lighting vs the brazier-lit room; the G2 light_tint treatment exists for baked renders but not runtime tokens). User-truth polish class for demo gate G4. Frame: /Volumes/LEXAR/Codex/session-notes/2026-07-22/cast-presence-1639/artifacts/walk4/shot_to_throne.png

[evaos-code-review-bot]

evaOS issue enrichment

Issue: #1665 - Runtime monster tokens render unintegrated: Goblin Boss oversized, slightly floating, no scene light tint
State: open

Related issues/PRs: #1662.
Existing labels: none.
Suggested labels: security.
Suggested owners: none.

Related context

• engine: rest surface emits located cast (NPCs + live monsters) — closes #1639 #1662 - mentioned in issue metadata; inspect for dependency, duplicate, or prior-decision risk.

Agent-start packet

Problem shape: Runtime monster tokens render unintegrated: Goblin Boss oversized, slightly floating, no scene light tint - Seen on the first walked-arc GREEN (walk4, 2026-07-22): the throne_hall Goblin Boss token (#1662) renders but reads unintegrated — model spans ~2x the throne height, feet hover ~half a cell above its marker ring, and it
Product fit: Architecture/integration issue; check repo policy, prior decisions, and operational constraints before implementation.
Implementation wedge: Start with a bounded adapter/contract or dry-run packet before changing live runtime 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.
• Contract or degraded-mode proof before runtime promotion.

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]

g4-build eyeball (post-#1676): grounding FIXED — goblins' feet sit at their rings (the applyRootMotion root cause held). But the foe warm tint renders as strong BLOOD-RED patches on the goblin bodies rather than warm ambience — the multiply is over-strong or hitting the wrong channel weight. Boss scale/tint check pending the throne re-cert. Polish pass needed on the tint constant. Frame: LEXAR session-notes 2026-07-22/g4-build/artifacts/cert_g4/shot_sil_behind.png

[100yenadmin]

Throne evidence (g4 build): boss SCALE fixed (~≤2 cells beside the throne, was tower-height). GROUNDING improved but residual: feet still hover ~1/3 cell above the ring on the dais. TINT: same over-saturated blood-red as the goblins — the warm multiply constant needs tuning down substantially (target: subtle warmth matching party lighting, not a red overlay). Frame: LEXAR session-notes 2026-07-22/g4-build/artifacts/throne_g4.png