release: 0.1.0 — agent-taught courses, Project Radar, 0.0.3 contracts

Merges feat/0.0.3-courses-and-radar: the five-course batch (C1-C5,
EN+ZH), per-project Radar YAML with radar.json + schema, claim-code
 groundwork plan (0.0.4 docs), README referral, and the instructor
canonicalization.

Author: xxg1413

.github/ISSUE_TEMPLATE/course-feedback.yml

@@ -0,0 +1,46 @@
+name: Course feedback
+description: Report teaching drift, an unclear lesson, or a verify.py mismatch in a course folder.
+title: "[Course]: "
+labels: ["course-feedback"]
+body:
+  - type: input
+    id: course
+    attributes:
+      label: Course folder
+      description: Which courses/<slug>/ folder did you take?
+      placeholder: courses/hands-on-python-with-claude-code/
+    validations:
+      required: true
+  - type: dropdown
+    id: kind
+    attributes:
+      label: What went wrong?
+      options:
+        - The agent drifted from COURSE.md (ignored rules, scope, or lesson order)
+        - A lesson was unclear or wrong
+        - verify.py result did not match the lesson's checkpoint
+        - Starter/solution/tests problem
+        - Something else
+    validations:
+      required: true
+  - type: input
+    id: lesson
+    attributes:
+      label: Lesson
+      description: Which lesson (L01–L05), if lesson-specific?
+    validations:
+      required: false
+  - type: textarea
+    id: detail
+    attributes:
+      label: What happened?
+      description: Describe what the agent did or what confused you. Include the exact command and output when reporting a verify.py mismatch.
+    validations:
+      required: true
+  - type: input
+    id: environment
+    attributes:
+      label: Environment
+      description: Tool and version (e.g. Claude Code 2.x), Python version, operating system.
+    validations:
+      required: true

.github/workflows/validate.yml

@@ -45,8 +45,8 @@ jobs:
       - name: Validate catalog
         run: python tools/validate_catalog.py
 
-      - name: Verify public JSON export
-        run: python tools/export_catalog.py --check
+      - name: Verify public JSON exports
+        run: python tools/export_catalog.py --check --target both
 
       - name: Verify browsable README indexes
         run: python tools/render_readmes.py --check
@@ -56,3 +56,6 @@ jobs:
 
       - name: Verify runnable examples
         run: python tools/verify_examples.py
+
+      - name: Verify course folders
+        run: python tools/verify_courses.py

.gitignore

@@ -42,3 +42,7 @@ __pycache__/
 
 # Generated reports
 reports/
+
+# Course scenario output written by learners running report_tool.py
+courses/*/scenario/*/report.json
+courses/*/scenario/*/report.json.tmp

AGENTS.md

@@ -25,24 +25,40 @@ reviewed catalog data, and stable public JSON contracts.
   review date, and factual meaning. All content (guides, playbooks, examples,
   courses, radar entries) ships EN+ZH in the same change.
 - Governance documents (`AGENTS.md`, `CONTRIBUTING.md`, `docs/CONSUMING.md`,
-  `docs/CURATION_POLICY.md`, `docs/REPO_TO_WEBSITE.md`, plans) are
-  English-canonical; a `_cn` companion may exist but the English text governs.
-- Add first-party guides and playbooks to `content-manifest.json`; keep each
-  locale pair aligned and verify its source checksum.
+  `docs/CURATION_POLICY.md`, `docs/REPO_TO_WEBSITE.md`) are
+  English-canonical. Version plans (`docs/repo-plan-*.md`) are maintained
+  in Chinese by owner decision (2026-09-12); their English history stays
+  in git.
+- Add first-party guides, playbooks, and courses to `content-manifest.json`;
+  keep each locale pair aligned and verify its source checksum.
+- Courses live one folder per course under `courses/<slug>/` and are taught by
+  an AI coding agent from the files themselves: `COURSE.md` (metadata plus the
+  teaching contract: audience, prerequisites, exact tool and version,
+  lesson order, teaching-style rules, when to stop, how to use `verify.py`,
+  and what the course does not cover), `lessons/L01.md` with `L01_cn.md`
+  pairs (objective, exercise, checkpoint, expected evidence), `scenario/`
+  data files for each skin, `TASK.md`/`TASK_cn.md` (task contract),
+  `starter/` and `solution/` runnable pairs, stdlib-only `verify.py` that
+  fails on `starter` and passes on `solution`, and `REVIEW.md` recording the
+  maintainer run-through (date, tool, version, observed agent deviations).
+  A course is incomplete until every lesson ships EN+ZH in the same change;
+  `COURSE.md` must name the exact tool version it was taught with, and a tool
+  major release triggers re-review. Never claim guaranteed learning outcomes.
 - Treat HTTP 403, 429, and transient 5xx responses as review-needed states, not
   automatic proof that a resource is broken.
 
 ## Change workflow
 
 - Work on a feature branch and preserve unrelated contributor changes.
 - Run the repository validation workflow before committing.
-- Regenerate `catalog.json` after source changes and verify it with
-  `python tools/export_catalog.py --check`.
-- Regenerate both README catalog indexes and verify them with
-  `python tools/render_readmes.py --check`.
+- Regenerate `catalog.json` and `radar.json` after source changes and verify
+  them with `python tools/export_catalog.py --check --target both`.
+- Regenerate both README catalog indexes and the Project Radar table, then
+  verify them with `python tools/render_readmes.py --check`.
 - Regenerate `content-manifest.json` and verify it with
   `python tools/build_content_manifest.py --check`.
-- Verify every runnable example with `python tools/verify_examples.py`.
+- Verify every runnable example with `python tools/verify_examples.py` and
+  every course folder with `python tools/verify_courses.py`.
 - Website consumers must pin a full repository commit and verify the catalog
   checksum. Do not make production builds depend on a moving branch.
 - Keep external-link checks read-only, rate-limited, retryable, and blocked from

CHANGELOG.md

@@ -2,10 +2,50 @@
 
 This file records notable catalog-contract and maintenance changes.
 
-## [Unreleased]
+## [0.1.0] - 2026-09-12
+
+First versioned release: agent-taught courses, the Project Radar
+system, and the 0.0.3 contract updates.
+
 
 ### Added
 
+- A `courses/` content type: agent-taught folders with COURSE.md teaching
+  contracts, bilingual lesson pairs, scenario skins, task contracts, runnable
+  starter/solution pairs, and objective `verify.py` completion evidence.
+- The five-course 0.0.3 batch: "Hands-on Python with Claude Code"
+  (flagship), "Hands-on with OpenAI Codex CLI" (reuses the C1 core), "One
+  source of truth for agent rules" (rule-drift checker core), "From 'it
+  runs' to 'it ships'" (release-evidence builder core), and "Give your
+  agent tools with MCP" (reuses the reviewed mcp-server contract) — each
+  EN+ZH with scenario skins and REVIEW.md run-through records.
+- `tools/verify_courses.py` enforcing the course folder contract, wired into
+  the Makefile and the validation workflow.
+- Project Radar per-project YAML records (`catalog/projects/*.yml`) with
+  lifecycle status, maintenance evidence, and `ai_familiarity` grading.
+- Deterministic `radar.json` export with `schema/radar-v1.schema.json` and
+  `--check` support in `tools/export_catalog.py` (`--target both`).
+- Bilingual generated Radar tables in `catalog/projects/README.md` and
+  `README_cn.md`.
+- `tools/radar_scan.py`: read-only, rate-limited discovery of Radar review
+  candidates from GitHub Search, the PyPI feed, and Hacker News — candidates
+  only, never descriptions or status.
+- A `course-feedback` issue template for teaching drift and verify mismatches.
+- `content-manifest.json` and its schema now carry `course` documents.
+- Courses and Radar sections in `llms.txt`.
+
+### Changed
+
+- README/README_cn gained a course banner, a courses row, and contextual
+  flypython.com footers on every guide, playbook, and example (first-party
+  continuation links per `docs/REPO_TO_WEBSITE.md`).
+- The validation workflow now verifies the radar export and every course
+  folder in addition to the existing gates.
+- Bilingual guide-URL tests now allow first-party flypython.com footer links
+  alongside reviewed catalog URLs.
+
+### Added (0.0.2 and earlier)
+
 - A complete bilingual Python AI-coding workflow covering task contracts,
   repository inspection, reproducible environments, bounded changes, tests,
   runtime verification, side-effect review, and evidence-based delivery.
@@ -32,7 +72,7 @@ This file records notable catalog-contract and maintenance changes.
   state, and source checksums for pinned website consumers.
 - A human-review contribution queue for current Python Project Radar entries.
 
-### Changed
+### Changed (0.0.2 and earlier)
 
 - Defined this repository as the canonical Python product-engineering content,
   catalog-data, and review layer behind flypython.com, rather than a second
@@ -44,7 +84,7 @@ This file records notable catalog-contract and maintenance changes.
 - Reduced the required local toolchain to Python 3.12 and locked Python
   dependencies.
 
-### Removed
+### Removed (0.0.2 and earlier)
 
 - Removed Jekyll, Ruby, page templates, styles, scripts, social assets, CNAME,
   robots configuration, and site-rendering tests.

Makefile

@@ -1,26 +1,28 @@
-.PHONY: help check export render manifest test verify lint typecheck all
+.PHONY: help check export render manifest test verify courses lint typecheck all
 
 PYTHON ?= python3
 
 help:
 	@echo "FlyPython Development Workflow:"
-	@echo "  make check      - Run all catalog, export, readme, manifest, and example checks"
-	@echo "  make export     - Regenerate catalog.json"
-	@echo "  make render     - Regenerate README and README_cn catalog indexes"
+	@echo "  make check      - Run all catalog, radar, export, readme, manifest, example, and course checks"
+	@echo "  make export     - Regenerate catalog.json and radar.json"
+	@echo "  make render     - Regenerate README and README_cn catalog indexes plus the Radar table"
 	@echo "  make manifest   - Regenerate content-manifest.json"
 	@echo "  make test       - Run pytest test suite"
 	@echo "  make verify     - Verify all runnable examples"
+	@echo "  make courses    - Verify all course folders"
 	@echo "  make all        - Regenerate all exports and run all checks and tests"
 
 check:
 	$(PYTHON) tools/validate_catalog.py
-	$(PYTHON) tools/export_catalog.py --check
+	$(PYTHON) tools/export_catalog.py --check --target both
 	$(PYTHON) tools/render_readmes.py --check
 	$(PYTHON) tools/build_content_manifest.py --check
 	$(PYTHON) tools/verify_examples.py
+	$(PYTHON) tools/verify_courses.py
 
 export:
-	$(PYTHON) tools/export_catalog.py
+	$(PYTHON) tools/export_catalog.py --target both
 
 render:
 	$(PYTHON) tools/render_readmes.py
@@ -34,4 +36,7 @@ test:
 verify:
 	$(PYTHON) tools/verify_examples.py
 
+courses:
+	$(PYTHON) tools/verify_courses.py
+
 all: export render manifest test check

README.md

@@ -6,6 +6,12 @@
 
 [English](README.md) · [中文](README_cn.md) · [🌐 Online Portal](https://flypython.com)
 
+> **New — agent-taught courses with objective verification.** Download a
+> folder from [`courses/`](courses/), open it in your coding agent, and say
+> *"start lesson 1"*. Every course ends with a `verify.py` command that
+> proves what you built. Continue the same journey on
+> [flypython.com](https://flypython.com/).
+
 FlyPython is a practical, bilingual repository for writing good Python and
 turning it into products people can rely on. It combines AI-coding methods,
 task playbooks, runnable examples, reusable templates, and reviewed primary
@@ -35,6 +41,7 @@ to a coding agent (Cursor, Windsurf, Claude Code, Copilot) and make the starter
 
 | Goal | Start here | What you will produce |
 | --- | --- | --- |
+| Learn hands-on with your coding agent | [Agent-taught courses](courses/) | A verified project: task contract → bounded change → `verify.py` evidence |
 | Write and change Python safely | [AI Coding workflow](guides/ai-coding/workflow.md) | A bounded change with explicit context and evidence |
 | Turn Python into a reliable product | [Product quality guide](guides/python-engineering/product-quality.md) | A tested, observable, reversible product path |
 | Finish a recurring engineering task | [Playbooks](playbooks/README.md) | A bug fix, API change, integration, dependency upgrade, or release |

README_cn.md

@@ -6,6 +6,11 @@
 
 [English](README.md) · [中文](README_cn.md) · [🌐 官方在线门户](https://flypython.com)
 
+> **新——由 Agent 授课、带客观验证的实战课程。** 从 [`courses/`](courses/) 下载一个
+> 文件夹，在你的编码 Agent 中打开，说一句*“开始第 1 课”*。每门课程都以一条
+> `verify.py` 命令收尾，证明你确实做出了什么。同一旅程可继续在
+> [flypython.com](https://flypython.com/) 上进行。
+
 FlyPython 是一个面向实践的双语仓库，帮助你写好 Python，并把代码变成用户可以依赖的
 产品。这里同时提供 AI Coding 方法、任务 Playbook、可运行示例、复用模板，以及 API、
 自动化、Agent、Skill 和 MCP 的一手资料。
@@ -33,6 +38,7 @@ python examples/product-slug/verify.py solution
 
 | 目标 | 从这里开始 | 最终产出 |
 | --- | --- | --- |
+| 跟随编码 Agent 动手实战 | [Agent 授课课程](courses/) | 一个通过验证的项目：任务契约 → 边界修改 → `verify.py` 证据 |
 | 安全地编写和修改 Python | [AI Coding 工作方法](guides/ai-coding/workflow_cn.md) | 上下文明确、有证据的边界修改 |
 | 把 Python 变成可靠产品 | [产品质量指南](guides/python-engineering/product-quality_cn.md) | 可测试、可观测、可回退的产品路径 |
 | 完成反复出现的工程任务 | [Playbook](playbooks/README_cn.md) | Bug 修复、API 修改、外部集成、依赖升级或发布 |