Skip to content

feat: add Exit Strong development strategy game - #70

Draft
urbanplanningpros wants to merge 3 commits into
devfrom
codex/upp-exit-strong-game
Draft

urbanplanningpros wants to merge 3 commits into
devfrom
codex/upp-exit-strong-game

Conversation

@urbanplanningpros

@urbanplanningpros urbanplanningpros commented Sep 8, 2026 •

Copy link
Copy Markdown
Owner

Issue for this PR

Owner-requested Exit Strong game adaptation of the UPP book. No separate issue is linked; this remains a draft.

Type of change

  • Bug fix
  • New feature
  • Refactor / code improvement
  • Documentation

What does this PR do?

Adds a standalone browser adventure in projects/upp-exit-strong/ that teaches Evaluate → Plan → Coordinate → Exit through a fictional property and six endings.

Scout guides players through Go → Decide → Discover. The game includes investigations, development pivots, saved progress, replay, chapter notes, and links to the book and relevant UPP services. Shared assets and bounded saves keep the module compact.

Delivery requirement: the eventual production entry is /game on the confirmed UPP domain, served without an external redirect. Hostinger routing, menu integration, and paid access are unfinished and are not implemented by this PR. The later Sites-only noindex change is not included in this branch.

Sanitized-Manifest: 41 added files: 38 text files in the game module, two original WebPs, and one scoped workflow. No full book PDF, credentials, customer data, or runtime operator state.
Allowed-Paths: projects/upp-exit-strong/**, .github/workflows/upp-exit-strong.yml.

How did you verify your code works?

Run node scripts/release-check.mjs from projects/upp-exit-strong/. All 22 gameplay/journey tests and resource checks passed locally. GitHub's Exit Strong game checks also passed for the current PR commit.

Checks cover six guided endings, prerequisites, budgets, deadlines, save restoration, replay, chapter references, and duplicate assets. Browser interaction, visual rendering, and payment integration remain unverified. Resource caps are enforced; billion-fold consumption savings are not claimed.

Screenshots / recordings

Browser screenshots or a recording are still pending before final UI review.

Checklist

  • I have tested my changes locally
  • I have not included unrelated changes in this PR

The workflow addition still requires the repository's operator-approved-critical approval before merge. This metadata correction does not grant that approval or merge the draft.

Add a book-grounded fictional campaign, six exit routes, bounded saves,
locked resource budgets, and a scoped release-check workflow.
@github-actions

github-actions Bot commented Sep 8, 2026

Copy link
Copy Markdown

Hey! Your PR title Add Exit Strong, a playable UPP development strategy game doesn't follow conventional commit format.

Please update it to start with one of:

  • feat: or feat(scope): new feature
  • fix: or fix(scope): bug fix
  • docs: or docs(scope): documentation changes
  • chore: or chore(scope): maintenance tasks
  • refactor: or refactor(scope): code refactoring
  • test: or test(scope): adding or updating tests

Where scope is the package name (e.g., app, desktop, opencode).

See CONTRIBUTING.md for details.

@urbanplanningpros urbanplanningpros changed the title Add Exit Strong, a playable UPP development strategy game Add Exit Strong: play the book stages, map exits, and connect to UPP Sep 8, 2026
@urbanplanningpros urbanplanningpros changed the title Add Exit Strong: play the book stages, map exits, and connect to UPP Add Exit Strong: a guided cartoon adventure through the UPP book Sep 8, 2026
@urbanplanningpros urbanplanningpros changed the title Add Exit Strong: a guided cartoon adventure through the UPP book feat: add Exit Strong development strategy game Sep 9, 2026
@github-actions

github-actions Bot commented Sep 9, 2026

Copy link
Copy Markdown

Thanks for updating your PR! It now meets our contributing guidelines. 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant