feat: build Python product engineering hub

Author: xxg1413

.github/ISSUE_TEMPLATE/project-proposal.yml

@@ -0,0 +1,46 @@
+name: Propose a Python project
+description: Suggest a maintained Python project for human review in Project Radar.
+title: "[Project]: "
+labels: ["project-proposal"]
+body:
+  - type: input
+    id: source
+    attributes:
+      label: Official project URL
+      description: Link to the source repository or official project home.
+    validations:
+      required: true
+  - type: textarea
+    id: outcome
+    attributes:
+      label: What can a Python developer accomplish with it?
+      description: Describe a concrete user outcome, not marketing copy.
+    validations:
+      required: true
+  - type: textarea
+    id: evidence
+    attributes:
+      label: Maintenance and quality evidence
+      description: Include release, documentation, tests, license, and security evidence you checked.
+    validations:
+      required: true
+  - type: dropdown
+    id: area
+    attributes:
+      label: Primary area
+      options:
+        - Python engineering
+        - Web and APIs
+        - Automation
+        - AI coding
+        - AI agents
+        - Skills and MCP
+    validations:
+      required: true
+  - type: checkboxes
+    id: declaration
+    attributes:
+      label: Declaration
+      options:
+        - label: I disclosed any affiliation and wrote this proposal from sources I checked.
+          required: true

.github/PULL_REQUEST_TEMPLATE.md

@@ -28,6 +28,9 @@ List the actual results, not only the commands you intended to run.
 - [ ] `python -m pytest`
 - [ ] `python tools/validate_catalog.py`
 - [ ] `python tools/export_catalog.py --check`
+- [ ] `python tools/render_readmes.py --check`
+- [ ] `python tools/build_content_manifest.py --check`
+- [ ] `python tools/verify_examples.py`
 - [ ] English and Chinese output remain consistent
 - [ ] No secrets, generated reports, local build output, or analytics IDs were committed
 

.github/workflows/validate.yml

@@ -38,3 +38,12 @@ jobs:
 
       - name: Verify public JSON export
         run: python tools/export_catalog.py --check
+
+      - name: Verify browsable README indexes
+        run: python tools/render_readmes.py --check
+
+      - name: Verify first-party content manifest
+        run: python tools/build_content_manifest.py --check
+
+      - name: Verify runnable examples
+        run: python tools/verify_examples.py

AGENTS.md

@@ -2,15 +2,17 @@
 
 ## Mission
 
-This repository is the broad, community-maintained data catalog behind
-FlyPython. It is not a website. Keep `flypython.com` focused on editorial
-learning paths, task playbooks, and presentation; keep this repository focused
-on reviewed catalog data, its public JSON contract, and its contribution
-workflow.
+This repository is the community-maintained source for building good Python
+products in the AI-coding era. It is not a website. Keep `flypython.com`
+focused on presentation, discovery, and conversion; keep this repository
+focused on practical guides, playbooks, runnable examples, reusable templates,
+reviewed catalog data, and stable public JSON contracts.
 
 ## Content rules
 
 - Prefer official documentation and primary sources.
+- Keep first-party Python engineering and AI-coding guidance specific, testable,
+  and honest about what automation can and cannot prove.
 - Every catalog entry must include a stable ID, path, path-local order, source
   type, level, rationale, review date, status, and any key or safety requirements.
 - Do not call a project production-ready without current maintenance, licensing,
@@ -19,6 +21,10 @@ workflow.
   Descriptions and classifications require human review.
 - Keep English and Chinese website output generated from the same canonical
   resource data. Do not hand-copy catalog content into website source files.
+- Keep paired English and Chinese first-party guides aligned in scope, version,
+  review date, and factual meaning.
+- Add first-party guides and playbooks to `content-manifest.json`; keep each
+  locale pair aligned and verify its source checksum.
 - Treat HTTP 403, 429, and transient 5xx responses as review-needed states, not
   automatic proof that a resource is broken.
 
@@ -28,6 +34,11 @@ workflow.
 - 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 `content-manifest.json` and verify it with
+  `python tools/build_content_manifest.py --check`.
+- Verify every runnable example with `python tools/verify_examples.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

@@ -6,6 +6,13 @@ This file records notable catalog-contract and maintenance changes.
 
 ### Added
 
+- 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.
+- Browsable English and Chinese README indexes containing every reviewed
+  resource, its rationale, level, access requirements, risk, and review date.
+- Deterministic README generation and drift checks backed by canonical catalog
+  data.
 - One source file per reviewed resource under `catalog/resources/`.
 - A deterministic, versioned `catalog.json` export for pinned website consumers.
 - A JSON Schema describing the public catalog v1 contract.
@@ -15,11 +22,21 @@ This file records notable catalog-contract and maintenance changes.
 - Catalog validation and a safe external-link auditor with retry, report, and
   SSRF/DNS-rebinding protection.
 - Contribution, conduct, security, issue, and resource-curation policies.
+- A product-quality guide and five bilingual task playbooks for bug fixes, API
+  work, external integrations, dependency upgrades, and releases.
+- A standard-library-only example with a deliberately failing starter, verified
+  solution, and task contract.
+- Reusable task, plan, review, verification, agent-instruction, and pyproject
+  templates.
+- A versioned `content-manifest.json` with bilingual paths, summaries, review
+  state, and source checksums for pinned website consumers.
+- A human-review contribution queue for current Python Project Radar entries.
 
 ### Changed
 
-- Defined this repository as the canonical catalog-data and review layer behind
-  flypython.com, rather than a second public website.
+- Defined this repository as the canonical Python product-engineering content,
+  catalog-data, and review layer behind flypython.com, rather than a second
+  public website.
 - Split catalog metadata, paths, and resources into independently reviewable
   files while preserving the 21 existing human-reviewed resource records.
 - Required website consumers to pin a full repository commit and verify the

CONTRIBUTING.md

@@ -1,9 +1,11 @@
-# Contributing to the FlyPython catalog
+# Contributing to FlyPython
 
-FlyPython maintains a bilingual, reviewed source catalog used by
-[flypython.com](https://flypython.com/). Contributions should improve source
-quality, factual accuracy, or the maintenance workflow. General Python questions
-belong in [GitHub Discussions](https://github.com/flypythoncom/python/discussions).
+FlyPython maintains bilingual Python engineering guides, task playbooks,
+runnable examples, templates, and a reviewed source catalog used by
+[flypython.com](https://flypython.com/). Contributions should help a visitor
+complete a real Python task or improve factual accuracy and maintainability.
+General Python questions belong in
+[GitHub Discussions](https://github.com/flypythoncom/python/discussions).
 
 Read the [curation policy](docs/CURATION_POLICY.md) before contributing.
 
@@ -19,12 +21,20 @@ to submit and retain required third-party notices.
 Use the matching issue form before a larger change:
 
 - **Resource proposal** for a new official source.
+- **Project proposal** for a current Python project that should receive human
+  review for Project Radar.
 - **Broken link** for an unreachable or replaced resource.
 - **Security report** for a vulnerability; follow [SECURITY.md](SECURITY.md)
   instead of opening a public issue.
 
 Small typo, metadata, or tooling fixes may go directly to a focused pull request.
 
+First-party guides and playbooks must remain practical, testable, and aligned
+in English and Chinese. A content change must update both language files with
+the same content version and review date, then regenerate
+`content-manifest.json`. Do not present generated code, a passing test, or a
+deployment command as proof of user value or production readiness.
+
 ## Catalog sources
 
 The canonical source is the `catalog/` directory:
@@ -67,6 +77,8 @@ After changing catalog sources, regenerate the public export:
 
 ```bash
 python tools/export_catalog.py
+python tools/render_readmes.py
+python tools/build_content_manifest.py
 ```
 
 Run the same deterministic checks as CI:
@@ -75,6 +87,9 @@ Run the same deterministic checks as CI:
 python -m pytest
 python tools/validate_catalog.py
 python tools/export_catalog.py --check
+python tools/render_readmes.py --check
+python tools/build_content_manifest.py --check
+python tools/verify_examples.py
 ```
 
 Maintainers can run the networked link audit through GitHub Actions. For a
@@ -90,7 +105,7 @@ justify removing a resource.
 
 ## Pull request checklist
 
-- Keep source data and the generated `catalog.json` consistent.
+- Keep source content and generated JSON exports consistent.
 - Preserve English and Chinese meaning.
 - Include evidence for maintenance, ownership, access, and safety claims.
 - Do not call a project production-ready without current evidence.