GeezerVison

Summary

The 0.0.3 plan had all 13 TODO items unchecked, even though most of them shipped long ago. Both plan headers also cited stale master and website-pin SHAs. Readers, including coding agents, could take those as open work. Per owner decision, version plans are maintained in Chinese, so the edits are in Chinese.

• docs/repo-plan-0.0.3.md: each item was checked against the repository on 2026-10-11. 10 items are now ticked, each with a short note citing its evidence. Three stay open, with notes saying exactly what is missing:
  • FP-326: the agent-taught (guided-mode) run-through of the flagship course is still pending in its REVIEW.md.
  • FP-332: llms.txt lists only 8 of the 12 courses. It is missing hands-on-with-cursor, -deepseek-harness, -kimi-code, and -zcode, and the link courses/hands-on-with-openai-codex-cli/ is broken; the real folder is courses/hands-on-with-openai-codex/.
  • FP-335: contextual end-of-document links are in place, but the README banner still links the site root rather than /from-github. docs/REPO_TO_WEBSITE.md permits either, so this is left for the owner to decide.
• Both headers now point to CHANGELOG.md, docs/REPO_TO_WEBSITE.md, and the website's src/data/content-pin.json instead of hard-coded SHAs that go stale.
• docs/repo-plan-0.0.4.md status now also records that verifier v2 replaced progress --json with check --json + --attest. It names the two open items: FP-414, and guided-mode run-throughs for the 9 courses whose REVIEW.md lists them as pending.

Change type

• Catalog resource or classification
• Bilingual editorial content
• Catalog export or consumer contract
• Tests, tooling, or workflow
• Governance or documentation

Evidence and scope

• Related issue: none
• Source or maintenance evidence: repository state on 5a7cb0c, gh release list, gh repo view
• Website consumer impact: none (plan docs are not in content-manifest.json)
• Intentionally out of scope: fixing llms.txt itself, switching the README banner to /from-github, and the website-side halves of FP-327 / FP-332 / FP-344, which can't be verified from this repository

Validation

• make check passes: ruff, pytest, validate_catalog.py, export_catalog.py --check --target both, render_readmes.py --check, build_content_manifest.py --check, verify_examples.py, verify_courses.py, verify_paths.py
• English and Chinese output remain consistent (Chinese-only plan docs by owner decision)
• No secrets, generated reports, local build output, or analytics IDs were committed

Permissions and review

• I have the right to submit this contribution.
• I retained third-party notices and did not relicense third-party material.
• Human reviewers wrote or verified all resource descriptions and classifications.
• I read CONTRIBUTING.md and docs/CURATION_POLICY.md.