Practice 10 · Evidence for release

A. Read and run the checks

Run typecheck, the reference test suite and build. Record commands, result counts and limitations. Choose one pure-rule test and one component test; explain the claim each supports. Run preview and inspect one checkpoint from the built output if your environment supports a real browser.

B. Repair a weak test

A test clicks Save and asserts that the component's internal state variable changed. Rewrite the proposed assertion in terms of visible or accessible behavior. Explain why a hard-coded one-second wait is weaker than waiting for a named async result. Name one behavior that a simulated DOM cannot certify.

C. Transfer

Write a release note for your copied explorer: exact setup commands, four verified behaviors, three still-unverified checks, a known limitation, and a rollback/recovery step. Add one new regression test for a bug you deliberately reproduce and then fix. Keep the failing-before and passing-after evidence. Do not publish the app.

Completion evidence: command results, behavior-focused assertion, one new regression test and honest release note. Separate solutions. Then attempt assessment 03 and the capstone.