Bring One Local Result Back

This is the final assessed handoff inside Chapter 13. It adds no project behavior and does not change the capstone you just finished.

Read the privacy boundary immediately before the checker command:

pl_check.py runs on this computer. The script itself makes no network requests and never uploads anything. It runs only the listed checks; a declared package import executes that curated package’s import code. Its token contains the chapter and plan versions, exact Python version, pass/fail-style environment facts, declared relative file names, and file content digests; never absolute paths, usernames, environment variables, or file contents. When you paste and submit the token, Python Land receives and may store it as lesson work.

Chapter 13 plan 1 has exactly eight checks:

1. Python 3.10 or newer ran the checker.

2. That Python was inside a virtual environment.

3. That Python could import requests.

4. That Python could import pytest.

5. requirements.txt had the reviewed runtime pin.

6. requirements-dev.txt had the reviewed development recipe.

7. data/offline-page.json had the reviewed authored fixture bytes.

8. offline-report.txt had the exact deterministic offline report bytes.

The checker reads only those four declared relative files, each with a 64 KiB limit. It does not read shell history, tests, source modules, caches, secrets, or editor settings. The report digest proves only that those exact report bytes were present. It cannot prove which command created them. The token also does not prove test results, either --help result, a clean tree, a download click, an operating system, or a live API call.

Run the local check

Run this only after the README’s offline report command, from the extracted project root.

./.venv/bin/python ./pl_check.py chapter-13

.\.venv\Scripts\python.exe .\pl_check.py chapter-13

./.venv/bin/python ./pl_check.py chapter-13

Copy the complete final line beginning with PL_CHECK_TOKEN=. Replace only the placeholder between the triple quotes, leave USE_SITE_ONLY_PATH = False, and press Submit. A passing result means only that the selected local Python reported the eight declared facts.

If a check fails, follow its next action, rerun the checker, and paste a fresh complete token. Do not convert a failed or malformed token into fallback.

The explicit site-only path

If local Python, download, extraction, or this workflow is impractical on this computer, deliberately set USE_SITE_ONLY_PATH = True and submit. The exact recorded outcome is:

Site-only path selected: completion is recorded, but no local machine was verified.

That is a continuation path, not local verification.