[codex] Add market benchmark evidence - #14
Open
RollNuts wants to merge 1 commit into
Open
Conversation
Owner
Author
|
Veripsa triage request: include this market benchmark PR in the merge-order set with #13, #8, #9, #10, #11, #12, #15, and #16. Expected ordering note: #13 should likely merge first because current |
This was referenced Jun 29, 2026
RollNuts
marked this pull request as ready for review
June 29, 2026 15:16
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.
What changed
Adds
docs/MARKET_BENCHMARK_2026-06-29.md, a Steam-facing market benchmark for Cinder Ward.The document covers:
appdetails.Why
The project needs a stronger direction grounded in actual Steam visuals, trailers, and replay hooks, not just text descriptions. This PR gives the art/gameplay work a benchmark-backed target before more assets are produced.
Validation
rg.Merge notes
This PR is documentation-only. It can merge after the repo policy self-match fix because current
mainpolicy still flags scanner configuration text on unrelated PRs.