docs(assets): integrate M3 hub production flow#17
Merged
Conversation
colorpulse6
marked this pull request as ready for review
July 19, 2026 08:43
Qodo reviews are paused for this user.Troubleshooting steps vary by plan Learn more → On a Teams plan? Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center? |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
PRODUCTION-REVIEWEDstatic art from later runtime registration andINTEGRATEDgameplay proofWhy
M3 needs buildings, props, and NPC identities as part of the development flow—not a late polish pass. This contract lets an asset worker make substantial parallel progress without inventing hub gameplay, stretching non-square props through the current renderer, or claiming unused files are integrated.
Verification
git diff --check origin/main...HEADcantina: 14,marketplace: 15,town-hall: 13)game/files are present in the diffGame tests/build were not rerun because this PR changes documentation and a JSON planning manifest only; it adds no production assets or runtime code.
Handoff boundary
This PR does not generate art or modify runtime consumers. The asset plan ends at static
PRODUCTION-REVIEWED; a later approved Cantina code slice ownssprites.tsregistration, hub data/consumer wiring, and the 480×854 production-export playtest.