Study Sprint Release Lab
Use one real client-side interaction to audit a static package, run smoke checks, change the release route, diagnose a controlled route-only fault, and recover. A “simulated release” below is a classroom state change, not a public deployment.
1. Run the local app
Default oracle: 2 minutes prepare, 3 minutes reflect, remaining whole minutes focus.
Visible result
2. Audit four release gates
3. Preserve + package
Course route: a single self-contained HTML file; step 4’s controlled fault imagines the folder version, with its styles in a separate styles.css. A checkpoint is a recoverable working copy; a manifest is the list of files shipped; an asset path tells the browser where a style, script, or image lives.
Local smoke evidence
4. Change route, retest, and recover
Optional Web Storage decision
This optional demo stores one fictional value for this page's current browser origin under learnai-week10-release-demo. The saved value is not a shipped file, but the storage-writing code is shipped; a public origin can create its own separate values. Browser storage is not secure and is not required for credit.
- Never store credentials, secrets, grades, health/identity data, consent/assent records, or private prompts.
- Clear the demo before leaving a shared device.
- The packet saves non-name responses locally; its clear control removes that draft.