7-Day Store Metadata Parity Sprint Before October 2026 Next Fest - One Surface Per Day for Micro-Studios

You fixed the FAQ last month. The fest demo branch promoted yesterday. Your short description still promises co-op. Your trailer still shows chapter four. Partners do not care which surface you forgot—they screenshot the lie beside build_id and call it a store-demo mismatch.

This Challenges & Community Hooks sprint assigns one Steam store surface per weekday for seven days so micro-teams finish a metadata parity pass before October 2026 Next Fest traffic. It bundles checklists you already have into a single calendar you can paste into Notion today. Same evidence culture as wishlist truth audit week—but optimized for field-group exports and Wednesday diff habit.

Time to read: ~35 minutes. Time to run the sprint: ~7 focused weekdays (~90 minutes each) once BUILD_RECEIPT exists.

Why this matters now (May–October 2026)

1. Metadata drift is multi-surface — Fixing FAQ alone leaves tags, trailer, and About lying.
2. Fest promotion velocity — Weekly branch promotes without weekly export diffs recreate yellow recovery patterns.
3. Tooling exists — 14 free export tools remove excuse.
4. Intake compression — 72-hour partner windows need one folder, not seven scattered docs.
5. May is the cheap month — Run the sprint in May–September; October is freeze and hotfix only.

Direct answer: Block one calendar week, assign each weekday a single metadata surface, require cold install + export diff + engineer sign-off per day, and end Day 7 with validate-packet exit 0 and Wednesday ritual scheduled.

Who this is for

Prerequisites (before Day 1)

Optional: run 5-day metadata freeze the following week for reinforcement.

Sprint rules (non-negotiable)

1. No branch promotion during the seven days unless copy diff is green first—order may swap if producer agrees.
2. No paid ads until Day 7 sign-off.
3. Engineer co-sign every day—writers do not self-certify hour-one proof.
4. Export after every Steam paste — live-YYYY-MM-DD-*.txt.
5. Empty git diff required before marking day complete.

Day 1 (Monday) — Short description + depot truth

Focus: 300-character short description + confirm public branch matches BUILD_RECEIPT.

Deliverable: day1-signoff.md with engineer initials.

Day 2 (Tuesday) — About bullets + opening paragraph

Focus: About section bullet parity.

Deliverable: Top three bullets match short description verbs.

Day 3 (Wednesday) — Developer tags + community note

Focus: Tag coherence checklist.

Deliverable: Tag diff green; note in day3-signoff.md.

Meta: Schedule recurring Wednesday fifteen-minute diff starting next week.

Day 4 (Thursday) — Screenshots + capsule skim

Focus: Screenshot safe zones five gates + 32px icon gates.

Deliverable: day4-visual-signoff.md + PNG grabs in release-evidence/03-store/screenshots/.

Day 5 (Friday) — Trailer frame proof table

Focus: Trailer frame to demo scope audit.

Deliverable: trailer-frame-proof.md green.

Day 6 (Saturday or slip Monday) — Specs + event draft hygiene

Focus: System requirements honesty + event post parity.

Deliverable: Spec export diff green; event draft awaiting Day 7.

Day 7 (Sunday or slip Tuesday) — Integration + packet

Focus: Whole-page integrity + automation.

Deliverable: sprint-complete-YYYY-MM-DD.md signed by producer.

Daily time budget (realistic)

Total: ~13 hours across seven days—cheaper than one yellow weekend.

Evidence folder layout (end of week)

release-evidence/03-store/sprint-2026-MM-DD/
  day1-signoff.md
  day2-signoff.md
  ...
  live-day1-short.txt
  live-day2-about.txt
  about-bullet-proof.md
  trailer-frame-proof.md
  spec-proof.md
  sprint-complete.md

Matches release-evidence taxonomy.

How this relates to other challenges

Fest marketing and UTM discipline

Do not increase fest marketing cap spend until sprint-complete.md exists. Tag UTM rows with metadata-sprint-v1 after Day 7.

Failure modes (eight)

1. Skipping days because "FAQ is enough."
2. Promoting branch mid-sprint without re-running affected days.
3. Writer-only sign-offs without engineer.
4. No exports—diff from memory.
5. Combining days 4+5 into one visual pass without tables.
6. Publishing events on Day 6 before Day 7 integration.
7. Ignoring localized store pages.
8. Ending sprint without validate-packet.

Pro tips (nine)

1. Slack daily post: "Day N green" with link to signoff file.
2. Pair sprint with Asia–EU handoff commander rule.
3. Run AI disclosure challenge parallel if AI surfaces exist.
4. Add crash-log challenge in parallel engineering track—not substitute for metadata.
5. Re-run sprint when demo scope cuts >30%.
6. Use 14 export tools on Day 1 setup.
7. Schedule operating review Block 2 metric: days green.
8. Archive sprint folder in diligence packet.
9. Follow evidence cycles after sprint—weekly metadata batches only.

Snippet-friendly answers

Can we run days out of order?
Yes if sign-offs update when build_id changes—re-run affected days after promotions.

Is this instead of Wednesday diffs?
No—Day 3 installs Wednesday ritual; sprint is bootstrap.

Solo dev realistic?
Stretch Day 4–6 across two weeks if needed—keep order.

How does this interact with tag drift sprint?
Run tag drift recovery if tags broke mid-month.

Daily standup script (copy-paste)

Post this each morning in Slack:

Metadata sprint Day N/7 — Surface: <name>. Blocker: <none|engineer cold install|export access>. Sign-off owner: <name>. Promotion freeze until Day 7: yes.

Keeps marketing from "just fixing a typo" mid-sprint without re-running the affected day.

Triangle diff on Day 7 (full page)

After each day fixed one surface, Day 7 runs the full triangle:

Any verb appearing twice but failing hour one reopens the earliest day in the sprint calendar—do not patch only Day 7.

Localization add-on (optional Day 8)

If you ship localized store pages, add Day 8 with localization QA tools—diff non-English short description and bullets against English proof tables. English-only teams skip.

Two-storefront add-on

If you follow the two-storefront rule, duplicate Days 1–3 per surface with separate live-*.txt exports—do not assume itch HTML5 page inherits Steam honesty.

Publisher diligence handoff

Append to diligence README after Day 7:

Metadata parity sprint completed <date> — folder release-evidence/03-store/sprint-<date>/ contains seven daily sign-offs, live exports, trailer table, spec proof, validate-packet log.

Under publisher diligence packets, this folder answers "how do you govern marketing surfaces?" without a live call.

When to re-run the entire sprint

Comparison to hash and yellow recovery

Hash mismatch case study and store-demo mismatch recovery are reactive. This sprint is preventive—same receipts, opposite calendar.

Team roles RACI (lightweight)

R = responsible, A = approves, C = consulted, I = informed.

Deck and AI surfaces (if applicable)

If claiming Deck or generative features anywhere in the week:

• Day 4 includes Deck tools listicle pass.
• Day 7 includes AI disclosure challenge annex row.
• Prompt registry freeze if runtime AI changed same month.

Post-sprint maintenance

After Day 7:

1. Wednesday diffs — fifteen minutes weekly forever.
2. Friday Block 5 — metadata row each week.
3. Evidence cycles — batch non-critical copy weekly per evidence cycles opinion.
4. Pre-October mock audit — full tabletop seven dimensions two weeks before fest.

Common mistakes (ten)

1. Treating sprint as marketing creative week.
2. Skipping exports because "we remember."
3. Running sprint without locked build_id.
4. Publishing events before Day 7.
5. Ignoring trailer because "copy is done."
6. Letting agency paste on Day 4 without signoff.
7. Combining all visuals into one unstructured Figma board.
8. Forgetting specs when bullets claim performance.
9. No validate-packet on Day 7.
10. Never scheduling Wednesday ritual after Day 3.

Worked example (anonymous week)

Monday Day 1: Short description still said "online co-op" — engineer fail — fixed before export.
Tuesday Day 2: Deleted two About bullets — table green.
Wednesday Day 3: Removed Online Co-Op tag — diff green — recurring Wednesday calendar invite sent.
Thursday–Friday: Cut trailer co-op segment — screenshot order fixed.
Saturday Day 6: Lowered min GPU after floor laptop test.
Sunday Day 7: validate-packet exit 0 — ads unpaused.

Total engineer time ~6 hours; writer ~8 hours; producer ~3 hours.

Evidence folder layout (copy this tree)

Create release-evidence/03-store/sprint-YYYY-MM-DD/ on Day 1 morning:

sprint-2026-05-20/
  README.md                 # links to BUILD_RECEIPT build_id + sprint owners
  day-01-short-description/
    live-short.txt          # export after paste
    proof-table.md          # verb vs hour-one matrix
    signoff.txt             # engineer + writer initials + date
  day-02-about/
    live-about.txt
    bullet-proof-table.md
    signoff.txt
  day-03-tags/
    tags-approved.json      # or approved export name your team uses
    diff-vs-wednesday-baseline.txt
    signoff.txt
  day-04-screenshots/
    hero-order.md
    safe-zone-checklist.md  # from screenshot safe zones post
    signoff.txt
  day-05-trailer/
    frame-proof-table.md    # timestamp rows
    signoff.txt
  day-06-specs-events/
    spec-floor-laptop.log
    events-draft.md         # not published until Day 7
    signoff.txt
  day-07-integrate/
    validate-packet.log
    triangle-diff.md
    producer-signoff.txt

The release-evidence taxonomy expects 03-store to answer marketing truth questions without opening gameplay builds. Naming days explicitly prevents partners from receiving seven unrelated PDFs.

BUILD_RECEIPT coupling (non-negotiable)

Your BUILD_RECEIPT row must list:

If receipt and live Steam disagree mid-sprint, freeze promotion until the disagreeing day re-runs. Do not bump build_id without re-running Days 1–3 minimum—tags and short description are build-scoped claims.

Sprint variants by team size

Solo (evenings only): Run Mon–Sun as written; merge engineer sign-off with your own cold install; skip RACI—use checklist only.

Writer + engineer (most indies): Writer owns Days 1–2 exports; engineer owns Days 3, 5, 6 cold installs; shared Day 4 art review; producer optional on Day 7.

Producer-led (3+ people): Producer owns calendar and sign-offs; writer never pastes without engineer in room for Days 1–3; art lead joins Day 4 only.

Agency-assisted: Agency may draft copy in parallel before Day 1, but nothing publishes until daily sign-off; agency never holds Steam login without your export discipline.

Pairing with adjacent 2026 challenges

Running every challenge at once is how teams burn out—sequence truth audit → metadata sprint → cold-hash unless intake deadline forces overlap.

Ads and UTM freeze during sprint

Follow fest marketing cap: no new paid campaigns until Day 7 producer-signoff.txt. Existing UTMs should map to surfaces you are editing—if UTM experiment points at trailer landing, Day 5 trailer work blocks ad restart even if copy days finished early.

Regional pricing and DLC rows (Day 6 annex)

If you sell in multiple currencies or ship DLC anchors, add thirty minutes to Day 6:

• Confirm regional pricing rows do not imply features absent from demo.
• Confirm DLC anchor pages do not promise full-game modes the fest build lacks.

These are not separate sprint days—they are annex checks so bullets on Day 2 do not contradict price-tier psychology.

Glossary (sprint vocabulary)

Key takeaways

• Seven weekdays map to seven store surfaces—finish parity without heroics.
• Day 1 short description + build_id; Day 2 About; Day 3 tags; Day 4 visuals; Day 5 trailer; Day 6 specs/events draft; Day 7 integrate + validate-packet.
• No promotion/ads until Day 7 producer sign-off.
• Engineer co-sign every day; git diff empty after each paste.
• Bundles existing 2026 checklists into one calendar for Next Fest.
• Store proof under release-evidence/03-store/sprint-*.
• Install Wednesday diff habit on Day 3.
• Run before October freeze; pair with cold-hash week after.
• Cheaper than store-demo mismatch recovery weekends.

FAQ

What if we only have five days?
Merge Day 4+5 visual and Day 6+7 integrate—higher risk, document merges in signoff.

Does this include press kits?
Add optional Day 8 for press PDF diff— not core sprint.

Can agencies run days?
They execute tasks; your engineer signs.

What if Steam UI blocks exports?
Screenshots + manual live-*.txt still required.

How tie to demo patch notes?
Publish demo patch notes after Day 7 with build_id.

October rules?
After sprint, October is typo-only unless demo scope changes—re-run affected days only.

Conclusion

Metadata parity is not one heroic Wednesday—it is seven small days that refuse to let any single surface lie about your fest demo. Paste this sprint into your calendar the week your BUILD_RECEIPT first goes green, and treat Day 7 sign-off like a mini ship gate.

When October arrives, you will not be inventing discipline—you will be running the Wednesday diff you installed on Day 3, with a folder partners can open without a call. That is how micro-studios trade panic edits for boring, provable store pages.

Pick next Monday as Day 1. Export the short description. Everything else gets easier once the first surface tells the truth.