Assignment: assemble an evidence report
Create a local report containing source commit, your changes, JDK/SDK, emulator/device, model, commands, outcomes, and unverified paths. Never paste an API key or raw provider request into it.
Run the unit tests, lint, and release build. Run instrumented tests only on a dedicated emulator. Then execute the six live cases in the lesson if your account has access. Report baseline test failures separately from failures introduced by your extension.
For each case, write a hypothesis before running it. A useful entry is: “After Stop, partial text remains STOPPED; subsequent context excludes it. Observed: … Evidence: … Remaining uncertainty: …” A screenshot of a spinner is not enough to prove network cancellation.
Inspect the release adapter and explain why the app can show local history while cloud generation is unavailable. Sketch the missing backend responsibilities without implementing fake authentication in the Android client.
Submit test summaries, a small diff, sanitized observations, and an explicit list of limitations. A blocked live request is a valid reported result; replacing it with a fake and calling it live is not. Mark completion only after you can explain what each evidence source does and does not establish.