feat: publish PatchProof v0.1.0

[eatdrop]

内容 / What Changed

• 发布零运行时依赖的 PatchProof Python 库与 CLI，提供快照绑定、精确哈希审批、一次性补丁应用、四阶段验证与内容寻址回执。
• Publish the zero-runtime-dependency PatchProof Python library and CLI with snapshot binding, exact-hash approval, disposable patch application, four-phase validation, and content-addressed receipts.
• 加入 Docker 加固 Runner、可信本地 Runner、70 项自动化测试和独立 Shadow Validation CI。
• Add a hardened Docker runner, explicit trusted-local runner, 70 automated tests, and an independent shadow-validation CI job.
• 发布 verifiable-agent-audit 与 agent-eval-builder 两个经过官方结构校验的双语 Codex Skills。
• Publish two officially structure-validated bilingual Codex Skills: verifiable-agent-audit and agent-eval-builder.
• 加入双语 README、安全模型、架构、工程文章与 IssueLens 真实复用案例。
• Add bilingual README, security model, architecture, engineering article, and a real IssueLens reuse case study.

原因 / Why

把 IssueLens 中有复用价值的 Agent 工程边界抽取为独立、可运行、可审计、可展示的公开成果，同时避免携带原实习公司的内部代码或数据。

Extract the reusable Agent-engineering boundaries from IssueLens into an independent, runnable, auditable, portfolio-ready public artifact without carrying internal internship code or data.

验证 / Validation

• PYTHONPATH=src python3 -m unittest discover -s tests -v — 70 passed
• 两个 Skill 均通过官方 quick_validate.py / Both Skills pass the official quick_validate.py
• git diff --check 与 git diff --cached --check / Both whitespace checks pass
• Wheel 构建、隔离安装并导入 0.1.0 / Wheel builds, installs into an isolated target, and imports as 0.1.0
• 真实 CLI 四阶段可信本地闭环通过，目标仓库快照不变 / Real four-phase trusted-local CLI loop passes with the target repository unchanged
• IssueLens 前向审计：63 个文件，只读快照稳定 / Forward audit against IssueLens: 63 files with a stable read-only snapshot

风险边界 / Risk Boundary

v0.1 仅支持有界 UTF-8 文本、Unified Diff 和 Python unittest。Docker 加固不是生产级恶意多租户沙箱；审批身份为声明式元数据，回执哈希提供完整性但不提供签名者真实性。

v0.1 supports bounded UTF-8 text, unified diffs, and Python unittest only. Docker hardening is not a production hostile multi-tenant sandbox; approver identity is declared metadata, and receipt hashes provide integrity rather than signer authenticity.