Azalee's Cat Café Vertical Slice Quality Evidence Sprint 12

Azalee's Cat Café added local vertical-slice quality evidence for the Bootstrap scene, scripted first-session path, save fixtures, and runtime smoke metrics.

Azalee's Cat Café completed a vertical-slice quality evidence sprint.

The sprint added a local Unity editor evidence runner for the Bootstrap playable scene. It inspects the scene setup, checks that the scene is included in build settings, confirms the controller and UI document are present, and writes a machine-readable report under build/evidence/sprint-12/.

The same runner executes a deterministic first-session script through the current cafe loop. The script covers tap and drag inputs, completes six correct serves with no misses, reaches Glowing Flow, introduces Mochi, places the Window Plant, claims A Warm Welcome, and records the resulting rewards and state.

Sprint 12 also added save-data fixtures for the first-session local save path. The evidence covers a completed save round-trip, corrupted save rejection, incompatible save-version rejection, contradictory monetization-gate rejection, and delete recovery back to a fresh first session.

The performance-smoke section runs the deterministic first-session loop 500 times and records coarse runtime timing. This is intentionally narrow: it is useful production evidence, not a frame-rate, memory, thermal, device-performance, or release-readiness claim.

The product contract now includes a dedicated scanner record, validation-runner record, evidence records, and a guardrail that local quality evidence cannot be treated as release, store, privacy, platform, or performance readiness.

Repository, content, VeritySpec, Unity EditMode, Unity PlayMode, Android build-smoke, iOS build-smoke, and the new vertical-slice evidence runner all passed before the product PR merged to main. The merge-triggered GitHub Actions on main passed as well.

The next Azalee production gaps are more human and platform-specific: human playtest notes, device performance captures, save migration fixtures, release-readiness gates, and platform store/privacy/signing evidence before any readiness claims.