Release ledger

What's new in SimDeck

A version-by-version record of approved SimDeck improvements.

Version 0.77

September 23, 2026

Remove card options without losing issued cards

Teachers can remove a card from future deals and role packages without removing cards students already hold or the Activity history.

Why it matters

- Simplifies the card library when two options are basically the same.
- Keeps student inventory and classroom history unchanged.
- Lets teachers restore a removed card later; role-package links must be added back intentionally.

Verification

- Unit regressions cover retirement, stale writes, protected templates, role/deal filtering, and preservation of issued cards and Activity references.
- Authenticated teacher smoke removes a card, reloads, restores it, reloads again, and cleans up its exact disposable Codex QA PROD class.

Source: Linear PI-252

Remove a card from its detail view, then find it in the removed-cards list and restore it when needed.
Clears the card's role-package mappings when removed, so future role deals cannot use it by mistake.
Leaves existing student cards and Activity references readable.

Version 0.70

September 2, 2026

Teacher-created usernames replace student email setup

David can add every student before class with a username and starting code 0000, prepare their roles and cards before first sign-in, and reset a forgotten code without changing classwork.

Why it matters

- Removes student email, password creation, class codes, join requests, and approval walkthroughs from new classroom setup.
- Makes each provisioned roster row an approved class member immediately, so David can preload roles, starter cards, seats, and notes.
- Lets students keep 0000 or optionally choose a different four-number code from their Account page.
- Lets David reset a code to 0000 while preserving every membership, role, card, and classroom event.

Verification

- Unit coverage proves new, replayed, cross-teacher, partial-failure, legacy-activation, code-change, reset, and last-membership reuse behavior.
- Responsive browser coverage checks the student sign-in surface at 320 and 390 CSS pixels with exact four-number input semantics.
- Exact PR-head CI, production schema creation, deployment binding, and isolated teacher/student production rehearsal remain delivery gates until release completion.

Source: Linear PI-240

Stores only a salted scrypt hash in a server-only credential collection; readable codes never enter backups, CSV, print, URLs, or Activity metadata.
Keeps usernames globally unique and reserved to the teacher who created them, including after the last class membership is removed.
Creates a student session only after the submitted code is verified and at least one approved membership exists.
Preserves existing roster IDs, private inventory routes, roles, cards, seats, and notes when a legacy student is assigned a username.

Version 0.69

September 2, 2026

Class backups omit credential-shaped metadata

Downloaded classroom backups now remove password, session, secret, sign-in ID, and private access-code fields from nested card and Activity metadata.

Why it matters

- Keeps password-reset bookkeeping out of files that teachers download or later restore.
- Preserves ordinary card provenance and classroom Activity details while removing credential-shaped fields recursively.
- Applies to existing classroom history at download time without rewriting live classroom data.

Verification

- Regression coverage includes nested password, secret, session, Auth user ID, and private access-code fields alongside preserved safe metadata.
- Full unit, typecheck, lint, build, exact PR-head CI, production deployment, and byte-level China/Egypt export audits remain required before acceptance.

Source: Linear PI-239

Normalizes underscore, hyphen, and camel-case key variants before applying the export allowlist boundary.
Sanitizes both card-template metadata and Activity metadata in the canonical backup builder.
Leaves classroom CSV exports unchanged and free of password fields.

Version 0.68

September 2, 2026

Teacher Account stays global

Teacher Account now opens in a neutral account context instead of inheriting whichever class or protected template happened to be selected.

Why it matters

- Keeps account identity and password controls separate from classroom work.
- Prevents a protected China or Egypt template from appearing to be the current context on a global page.
- Returns teachers to the neutral Classes page after account recovery or sign-out.

Verification

- Unit coverage requires neutral account shell props and rejects classroom-data selection on the account route.
- Navigation coverage requires both Account entry points to use the clean global URL.
- Full unit, typecheck, lint, build, exact PR-head CI, production deployment, and isolated teacher retest remain required before acceptance.

Source: Linear PI-239

Removes the selected-class query from both global Account links.
Avoids loading classroom data merely to render the global account page.
Uses the neutral classroom visual theme and global navigation only.

Remove card options without losing issued cards

Teachers can remove a card from future deals and role packages without removing cards students already hold or the Activity history.

Why it matters

- Simplifies the card library when two options are basically the same.
- Keeps student inventory and classroom history unchanged.
- Lets teachers restore a removed card later; role-package links must be added back intentionally.

Verification

- Unit regressions cover retirement, stale writes, protected templates, role/deal filtering, and preservation of issued cards and Activity references.
- Authenticated teacher smoke removes a card, reloads, restores it, reloads again, and cleans up its exact disposable Codex QA PROD class.

Source: Linear PI-252

Remove a card from its detail view, then find it in the removed-cards list and restore it when needed.

Clears the card's role-package mappings when removed, so future role deals cannot use it by mistake.

Leaves existing student cards and Activity references readable.

Teacher-created usernames replace student email setup

David can add every student before class with a username and starting code 0000, prepare their roles and cards before first sign-in, and reset a forgotten code without changing classwork.

Why it matters

- Removes student email, password creation, class codes, join requests, and approval walkthroughs from new classroom setup.
- Makes each provisioned roster row an approved class member immediately, so David can preload roles, starter cards, seats, and notes.
- Lets students keep 0000 or optionally choose a different four-number code from their Account page.
- Lets David reset a code to 0000 while preserving every membership, role, card, and classroom event.

Verification

- Unit coverage proves new, replayed, cross-teacher, partial-failure, legacy-activation, code-change, reset, and last-membership reuse behavior.
- Responsive browser coverage checks the student sign-in surface at 320 and 390 CSS pixels with exact four-number input semantics.
- Exact PR-head CI, production schema creation, deployment binding, and isolated teacher/student production rehearsal remain delivery gates until release completion.

Source: Linear PI-240

Stores only a salted scrypt hash in a server-only credential collection; readable codes never enter backups, CSV, print, URLs, or Activity metadata.

Keeps usernames globally unique and reserved to the teacher who created them, including after the last class membership is removed.

Creates a student session only after the submitted code is verified and at least one approved membership exists.

Preserves existing roster IDs, private inventory routes, roles, cards, seats, and notes when a legacy student is assigned a username.

Class backups omit credential-shaped metadata

Downloaded classroom backups now remove password, session, secret, sign-in ID, and private access-code fields from nested card and Activity metadata.

Why it matters

- Keeps password-reset bookkeeping out of files that teachers download or later restore.
- Preserves ordinary card provenance and classroom Activity details while removing credential-shaped fields recursively.
- Applies to existing classroom history at download time without rewriting live classroom data.

Verification

- Regression coverage includes nested password, secret, session, Auth user ID, and private access-code fields alongside preserved safe metadata.
- Full unit, typecheck, lint, build, exact PR-head CI, production deployment, and byte-level China/Egypt export audits remain required before acceptance.

Source: Linear PI-239

Normalizes underscore, hyphen, and camel-case key variants before applying the export allowlist boundary.

Sanitizes both card-template metadata and Activity metadata in the canonical backup builder.

Leaves classroom CSV exports unchanged and free of password fields.

Teacher Account stays global

Teacher Account now opens in a neutral account context instead of inheriting whichever class or protected template happened to be selected.

Why it matters

- Keeps account identity and password controls separate from classroom work.
- Prevents a protected China or Egypt template from appearing to be the current context on a global page.
- Returns teachers to the neutral Classes page after account recovery or sign-out.

Verification

- Unit coverage requires neutral account shell props and rejects classroom-data selection on the account route.
- Navigation coverage requires both Account entry points to use the clean global URL.
- Full unit, typecheck, lint, build, exact PR-head CI, production deployment, and isolated teacher retest remain required before acceptance.

Source: Linear PI-239

Removes the selected-class query from both global Account links.

Avoids loading classroom data merely to render the global account page.

Uses the neutral classroom visual theme and global navigation only.