[design][license] Audit OpenWorlds/Owlcat reference assets before visual PRs

[100yenadmin]

Summary

Audit the OpenWorlds/Owlcat reference bundle before any visual PR copies assets, text, icons, screenshots, or source snippets into the ClawDnD repo.

Refs #82 and #61.

Risk-reduction value: 7.0/10.

Evidence

Local design bundle:

• /Users/lume/Downloads/OpenWorlds.zip
• /Volumes/LEXAR/Codex/openworlds-design-2026-05-25/openworlds/screenshots/*.png
• /Volumes/LEXAR/Codex/openworlds-design-2026-05-25/uploads/*.png
• /Volumes/LEXAR/Codex/openworlds-design-2026-05-25/openworlds/*.jsx
• /Volumes/LEXAR/Codex/openworlds-design-2026-05-25/openworlds/styles.css

Known concern:

• Several uploads/*.png files are Owlcat-style game UI references and must be treated as inspiration/reference only unless separately licensed.
• Prototype copy and data in data.js may be generated/test content and should not become canonical ClawDnD content by accident.

Architecture/Process Plan

Create a lightweight audit before the first visual PR:

1. Classify each asset/source bucket:
   • safe to port as abstract design tokens
   • safe to port as generic component structure
   • requires rewrite
   • reference-only, do not commit
   • unknown, block until clarified
2. Add a local audit artifact under /Volumes/LEXAR/Codex/openworlds-design-2026-05-25/.
3. If needed, add repo docs under docs/ that describe the visual inspiration policy without committing third-party assets.
4. Update PR templates/body language for visual PRs to state whether any assets were copied.

Code/Repo Map

Inspect first:

• scripts/license_check.py
• content/
• data/srd/
• viewer/dashboard.html
• macos/ClawDnDApp/
• .gitignore

Implementation Notes

• Do not commit OpenWorlds.zip, extracted screenshots, pasted Owlcat references, or private test content.
• It is acceptable to port abstract layout patterns and color-token ideas after rewriting names/implementation.
• Prefer generated/owned game art or open-license assets later.
• Keep audit artifacts outside the repo unless they are clean policy docs.

Red-Team Review Checklist

• No binary screenshot/reference assets are staged.
• No BG/Owlcat/proprietary names or copy are added to production files.
• No private world seeds or test transcripts are committed.
• scripts/license_check.py still passes.
• .gitignore covers new build/design/runtime output if needed.

Acceptance Criteria

• There is a clear audit note saying which parts of the OpenWorlds bundle can be ported and which are reference-only.
• First visual PR explicitly states "no third-party/reference assets copied" or lists licensed assets.
• scripts/license_check.py passes.
• Git status excludes bundle artifacts.

Focused Validation

cd /Volumes/LEXAR/repos/ClawDnD
python3 scripts/license_check.py
git status --short
git diff --check

Original-Agent Handoff

Inspect first:

• /Volumes/LEXAR/Codex/openworlds-design-2026-05-25/clawdnd-mac-app-gap-map.md
• scripts/license_check.py
• .gitignore
• viewer/dashboard.html
• macos/ClawDnDApp/

[coderabbitai]

🔗 Related PRs

100yenadmin/electric-sheep-website-dashboard#109 - Add UI/UX Pro Max design intelligence skill with 161 product types [merged]
100yenadmin/electric-sheep-website-dashboard#115 - chore(phase-5): scoring audit + targeted polish (10 pages, +154/-85) [merged]
100yenadmin/openclaw-code-index#1 - feat: add OpenClaw Code Index distribution [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]

Rollout note: PR #124 adds the asset/fidelity policy for OpenWorlds work. It classifies primary visual/reference sources, reference-only screenshots/uploads, prototype demo data requiring rewrite, and production-banned Open Design/tweak-host code. The next UI PR must list copied source files, dependency notices, removed CDNs, removed sandbox/tweak code, and prototype data handling.