Tapoo increases maze area as levels rise. Progress continues until the current terminal window or browser viewport can no longer fit the next maze cleanly.

• Arrow keys: move the player
• Ctrl+B: cycle maze wall weight
• Space or Esc: pause the current run
• Enter: proceed after pause, win, or failure
• Ctrl+C: quit

• Keyboard controls mirror the terminal controls
• Ctrl+Alt+R: reset browser progress
• On touch devices, on-screen controls are shown automatically

• Terminal-first maze gameplay
• Browser SPA with the same black-and-green terminal feel
• Adjustable wall weights with live cycling during play
• Per-level scoring and progression
• Pause, resume, retry, and next-level flow
• Best-effort persistence for terminal and browser sessions
• Manual GitHub Pages deployment for the web build
• Go and TypeScript test coverage in CI

The browser build outputs a bundled file at public/js/tapoo.min.js and serves the SPA from public/index.html.

This compiles frontend/tapoo.ts with esbuild into a minified browser bundle.

Available pages:

• /index.html for the game
• /agents.html for the AI Agents placeholder page

The terminal version stores best-effort runtime state in a local file:

• .tapoo.store

It keeps track of:

• current level
• selected wall weight
• last game progress state

If the persisted state cannot be read or validated, Tapoo falls back to default startup behavior.

The SPA stores gameplay state in browser storage:

• localStorage for durable preferences such as level and wall weight
• sessionStorage for the active round snapshot

Privacy note: browser storage stays on the current device unless the user clears it, resets progress, or removes configured agent data. Browser storage is lightly obfuscated to discourage casual tampering, but it should not be treated as strong encryption for personal data. When AI Agent play is configured, gameplay context such as player name, current cell, destination cell, submitted moves, score, level, and traversal history may be sent to the configured agent API endpoint.

The deployed browser pages include a short privacy notice at privacy.html.

• Go 1.25+
• pnpm 11.7.0
• Node.js 22
• golangci-lint v2.12.2

make help
make frontend-install
make frontend-quality
make frontend-build
make test
make ci

Contributions are welcome, but contributors should install the repository pre-commit hook before creating commits.

1. Install the required toolchains: Go 1.25+, Node.js 22, pnpm 11.7.0, and golangci-lint v2.12.2
2. Install frontend dependencies:

make frontend-install

3. Install the repository git hooks:

./scripts/install-hooks.sh

The hook installer copies scripts/hooks/pre-commit into .git/hooks/pre-commit.

The pre-commit hook runs:

golangci-lint run

This is required so commits are checked locally before they are pushed. If golangci-lint is not installed, the hook installation script will warn you and show installation options.

make ci

At minimum, contributors should make sure:

• Go tests pass
• frontend typecheck, lint, and tests pass
• golangci-lint run passes
• govulncheck passes

• make lint: run golangci-lint
• make govulncheck: run govulncheck
• make frontend-quality: run frontend typecheck, lint, and tests
• make frontend-build: build the minified SPA bundle
• make test: run frontend checks plus Go race tests with coverage
• make ci: run the local equivalent of the main CI pipeline

The main CI workflow lives at .github/workflows/go.yml and runs:

• Go linting
• govulncheck
• frontend typecheck, lint, tests, and build
• Go race tests with coverage
• coverage uploads for Go and frontend reports

The Pages workflow lives at .github/workflows/pages.yml.

Pages deployment is manual-only.

To deploy:

1. Open the repository on GitHub.
2. Go to Actions.
3. Choose Deploy Pages Manually.
4. Click Run workflow.
5. Select the branch you want to deploy.

Important:

• GitHub Pages should be configured to use GitHub Actions as the publishing source.
• Since the workflow is manual, it deploys the branch selected at run time.