Version 0.22
July 14, 2026
Safer classroom changes and readable action history
Related classroom updates now stay together more reliably, stale actions are rejected more safely, and the demo action history stays readable beside Undo controls.
Why it matters
- - Multi-step card, role, student, import, undo, transfer, safety, restore, and deletion workflows are less likely to leave half-finished classroom state.
- - Old tabs and duplicate approvals are less likely to overwrite newer classroom changes.
- - Backup restores are checked against the real data shape before writing and preserve Bank and card-note state.
- - Student access codes and sign-in abuse controls are stronger without weakening normal classroom access.
- - Demo transfer sentences remain readable on desktop and mobile, with Undo placed below the sentence instead of squeezing it.
Verification
- - Twenty-five unit tests and 100 production-server browser/accessibility cases passed across Chromium, Firefox, WebKit, and mobile WebKit.
- - Typecheck, lint, production build, screenshot checks, skeleton checks, theme contrast, backendless-demo verification, and npm audit passed.
- - Live Appwrite schema, integrity, restore-plan, health, and durable rate-limit checks passed.
- - The Linear release ledger was updated before this public page entry.
Source: Linear release ledger document, PI-213
- Made related classroom writes atomic and added stale-write protection at mutation boundaries.
- Strengthened backup planning, relationship validation, schema/index checks, production integrity signals, and health reporting.
- Added stronger access-code generation, durable sign-in rate limits, scheduled cleanup, and a strict nonce-based production content security policy.
- Reworked demo action rows into a two-column layout and added a browser regression check for usable summary width.
- Captured a real headed-browser walkthrough covering use, restore, send, undo, teacher/student switching, reset, and mobile layout.