Door cells don't match painted doorways — labels/glow float mid-floor (crypt + tavern)

[100yenadmin]

Symptom (orchestrator eyeball, ship-morning frames — PR #1532 evidence dir)

In frame1_crypt.png, "To Campfire Clearing" and "To Firelit Tavern Hall" render over open floor/left wall, while the plate's painted archways sit top-center and top-right. In frame3_tavern.png, "To Crypt Antechamber" floats mid-room; the painted doorway (dark opening, left wall) is unlabeled. The glow+label mechanism works — it's anchored at the wrong cells.

Root cause (not a renderer bug)

The walkslice door cells were authored for PATHING convenience ("prop-free door zone" comments in qa/seed_gfx_walkslice.py: camp door (6,0) back-center, tavern door (0,5) left wall), not measured against where the plates PAINT doorways. The renderer faithfully labels the authored cell — the authored cell is just not under the painted archway. Same geometry-vs-paint coherence class as #1396/#1505, now for doors instead of props.

Fix direction (next cycle)

1. Measure the painted archway positions on each canonical plate (crypt: two arches; tavern: left-wall opening; camp: gate-post gap — the new CAMP_DOOR (5,0) from walkslice: camp return door + spawn off the extended firewood footprint #1533 was measured against the paint and should be the pattern).
2. Move each door_cells entry to the measured cell; keep the landing-ring prop-free constraint (may need a 1-cell nudge + ring re-check).
3. Add the check to tools/derive_room_manifest.py or the coherence gate: every door_cells entry should sit inside a painted-doorway region (could reuse the grid-paint coherence instrument's cell-classification).
4. Re-run the journey eval + a door-cross smoke after the move (cross_door landing cells change).

Punch-list linkage: this is the class the owner notices immediately (playtest #4 "can't find room transitions" was the same complaint from the other direction — labels exist now, but in the wrong place).

[evaos-code-review-bot]

evaOS issue enrichment

Issue: #1534 - Door cells don't match painted doorways — labels/glow float mid-floor (crypt + tavern)
State: open

Related issues/PRs: #1532, #1396, #1533, #4.
Existing labels: none.
Suggested labels: bug, security, tests.
Suggested owners: none.

Related context

• SHIP-MORNING: three-room world (crypt<->camp<->tavern) + multi-door cross_door fix #1532 - mentioned in issue metadata; inspect for dependency, duplicate, or prior-decision risk.
• content: crypt_dense_v1 engine impassable cells don't match the PAINTED plate props (sarcophagus) #1396 - mentioned in issue metadata; inspect for dependency, duplicate, or prior-decision risk.
• walkslice: camp return door + spawn off the extended firewood footprint #1533 - mentioned in issue metadata; inspect for dependency, duplicate, or prior-decision risk.
• Epic 3: Combat engine #4 - mentioned in issue metadata; inspect for dependency, duplicate, or prior-decision risk.

Agent-start packet

Problem shape: Door cells don't match painted doorways — labels/glow float mid-floor (crypt + tavern) - ## Symptom (orchestrator eyeball, ship-morning frames — PR #1532 evidence dir) In frame1_crypt.png, "To Campfire Clearing" and "To Firelit Tavern Hall" render over open floor/left wall, while the plate's painted
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.

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