art(hubs): produce M3 hub asset bundles

[colorpulse6]

Summary

• produce the complete Cantina, Marketplace, and Town Hall M3 hub bundles from the docs-owned manifest
• retain exact built-in image-generation sources and deterministic production derivatives
• add review evidence for texture repetition, actual-size props, NPC identity, and dark/bright readability
• add a manifest-backed validator and flat sprite contract tests
• record the runtime-integration handoff without claiming registration or gameplay integration

Every manifest entry in this PR is exactly PRODUCTION-REVIEWED — NOT REGISTERED — NOT INTEGRATED. No gameplay screenshot is included because the current runtime has no consumer for these assets; the later Cantina integration slice owns the 480×854 gameplay proof.

Independent review caught a mirrored-repetition defect in the initial Town Hall environment set. All four environment sources were regenerated with non-palindromic continuity, the evidence was rebuilt, and the follow-up review approved the replacement bundle.

Verification

• all three direct M3 hub validators: pass
• npx tsc --noEmit: pass
• yarn colony:test: 284/284 pass
• yarn engine:test: 282/282 pass
• yarn sprites:test: 7/7 pass
• yarn build: pass; 6/6 static pages generated, 3/3 routes exported
• NEXT_PUBLIC_DEVTOOLS=1 yarn build: pass; 6/6 static pages generated, 3/3 routes exported
• committed visual evidence inspected for all three hubs
• runtime search confirms no M3 hub sprite registration or consumer

Integration boundary

The next artifact is an M3 Cantina code design/plan covering interior asset fields, layout, NPC placement and schedules, interaction, DevPanel fixture, normal player access, Atlas/bulletin-board boundaries, runtime registration, and the first true gameplay screenshot.

Stack

This draft targets agent/m3-asset-production-flow because the docs/manifest foundation is still open in draft PR #17. Once #17 lands, this branch can be retargeted to main.

[qodo-code-review]

Qodo reviews are paused for this user.

Troubleshooting steps vary by plan Learn more →

On a Teams plan?
Reviews resume once this user has a paid seat and their Git account is linked in Qodo.
Link Git account →

Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center?
These require an Enterprise plan - Contact us
Contact us →

[qodo-code-review]

Qodo reviews are paused for this user.

Troubleshooting steps vary by plan Learn more →

On a Teams plan?
Reviews resume once this user has a paid seat and their Git account is linked in Qodo.
Link Git account →

Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center?
These require an Enterprise plan - Contact us
Contact us →