[openworlds-audit] Screen: Forge — 62/100 — Polish-Pass

[100yenadmin]

Per-screen UI/UX audit epic — rolls up under #242 Phase 5.

Field	Value
Screen	Forge
Route	/openworlds/#forge
Source	viewer/openworlds/screen-forge.jsx
Audit doc	docs/ui-audit/screens/forge.md
Screenshot	docs/ui-audit/screenshots/forge-1512.png
Score	62/100 — Polish-Pass
Findings	2 Critical, 4 Major, 4 Minor + 1 Trivial

Read the full audit

The complete scored audit + finding table (severity / file:line / acceptance criteria) is in docs/ui-audit/screens/forge.md. Cross-screen patterns and reference comparisons are in docs/ui-audit/RPG_REFERENCE_PATTERNS.md; scoring criteria are in docs/ui-audit/SCORING_RUBRIC.md.

Cross-cutting epics this screen contributes to

epic:per-page-polish,epic:demo-leak,epic:portraits

Next pass (per the audit doc's "Recommended next pass")

See the Recommended next pass section at the bottom of the audit doc — usually 2–3 highest-leverage findings.

How to work this epic

1. Open docs/ui-audit/screens/forge.md.
2. Pick a finding from the table (severity: Critical → Major → Minor → Trivial).
3. File a sub-issue using the audit row's Acceptance criteria column. Link the sub-issue to this epic.
4. Implement, verify (headless via qa/owshot.sh forge <out.png> 8799 or live in the macOS app).
5. Cross off the row in the audit doc when the sub-issue lands.

Parent epic: #242

[coderabbitai]

🔗 Related PRs

100yenadmin/electric-sheep-website-dashboard#115 - chore(phase-5): scoring audit + targeted polish (10 pages, +154/-85) [merged]
#125 - feat(viewer): host exact OpenWorlds surface [merged]
#241 - openworlds: wave-2 adversarial-review nits (LOW cosmetic) [merged]
#243 - [openworlds] UI finish wave 1: Session readability + demo-leak round 2 [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

[100yenadmin]

CLOSE-STALE: screen-by-screen ui-audit grind superseded 2026-05-30 by the empirical blind-AI-playtester QA strategy (fix what playtests hit, not audit checklists). History retained. (backlog triage 2026-07-02; reopen if this misjudged it)