StackLogic v0.3.0-beta.1

StackLogic v0.3.0-beta.1

This is the final pre-multiplayer release of StackLogic's solo game core.

Highlights

• Deterministic level progression and drop-speed curve
• Standard competitive line-clear and drop scoring
• Reproducible seeded seven-bag piece sequences
• Bounded sequence replay offsets, including exact bag boundaries
• Cryptographically seeded solo games
• Explicit seed injection seam for the upcoming authoritative room service
• One piece source for active and preview pieces

Verification

• 130 automated tests across 56 suites
• Canonical development-lane browser acceptance
• Independent exact-commit review with no findings
• No multiplayer networking is included in this release

StackLogic v0.2.0-beta.1

StackLogic v0.2.0-beta.1

Release date: 2026-07-25

Public URL: https://vector-sigma-works.github.io/StackLogic/

Summary

This beta minor release adds StackLogic's theme system and the first accepted Matrix experience while preserving gameplay geometry and pacing. Players can select Default, Matrix, CandyPop, or Dark from the title screen and can change themes while paused without restarting or resuming the game.

User-visible changes

• Four persistent themes: Default, Matrix, CandyPop, and Dark.
• Matrix rain behind the game and UI, with input-safe stacking.
• Solid Matrix pieces in deterministic green shades.
• Solid Dark pieces in deterministic black-to-grey shades.
• Theme selection in a dedicated pause menu.
• Accessible Arrow-key and Home/End theme navigation with synchronized roving focus.
• Wide touch-device controls for iPad-class landscape and portrait viewports.
• Reduced-motion behavior that creates no Matrix rain animation resources and stops/restarts rain when the preference changes live.

Validated implementation chain

1. a38013d — title and theme scaffolding
2. bd9ff25 — theme-aware renderer foundation
3. 2bc4a6c — Matrix rain lifecycle controller
4. 712d2f4 — synchronous theme-change contract
5. a124129 — deterministic Matrix rain adapter
6. 156d81e — browser Matrix rain integration
7. def2ddc — solid theme palettes, tablet controls, and pause themes

The release is merged with history preserved so each independently validated phase remains auditable.

Verification

The release candidate passed:

• 80 canonical tests before release metadata coverage was added;
• focused renderer, lifecycle, adapter, and bootstrap tests;
• real-browser Matrix ownership, stacking, hit-testing, persistence, resize/DPR, reduced-motion, and cleanup gates;
• wide iPad-class landscape and portrait visibility/hit-testing gates;
• pause-time Dark and Matrix switching while the board remained frozen;
• an exact canvas-fill trace against stacklogic-dev.game.lan, proving Matrix fills belong only to the approved green palette and Dark fills only to the approved grayscale palette;
• changed-line security and scope scans;
• real-browser keyboard/focus acceptance and computed selected-label contrast above 4.5:1;
• real-browser live reduced-motion stop/restart acceptance without reload;
• npm audit --omit=dev: 0 vulnerabilities after lockfile-only transitive remediation;
• fresh independent semantic review.

Final release test counts and public GitHub Pages evidence are recorded in the pull request and GitHub Release after deployment.

Compatibility and data

• No gameplay board geometry, timing, scoring, or save-format migration is introduced.
• Existing local high scores and preferences remain in browser localStorage.
• No runtime dependency was added for the theme or rain implementation.

Known limitation

Web applications cannot directly observe whether an iPad hardware keyboard is docked. On-screen controls use the standards-based (hover: none) and (pointer: coarse) input-capability proxy. Automated iPad-class viewport emulation passes; physical Safari behavior remains a hardware/browser acceptance boundary.

Rollback

The pre-release production baseline is tag v0.1.0-beta.1 at commit 07e5f1772f1daab2764bbe5c5f3f3cb4d09fca34.

If public verification fails, revert the release merge commit through a reviewed rollback pull request and allow the gated GitHub Pages workflow to redeploy. Do not force-reset main or move release tags.