chore: 标准化仓库治理与持续集成 - #31
Merged
Merged
Conversation
This was referenced Sep 1, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
关联:#1、#10(Relates to #1 and Relates to #10)
目标
本 PR 完成 Parent #1 的仓库标准化收口,使公开仓库在许可证、打包元数据、贡献与安全治理、Issue/PR 协作入口、依赖维护和持续集成方面具备可审计的统一基线。
主要内容
Copyright 2026 Ev3rGan;License-Expression: Apache-2.0与License-File: LICENSE,并确保 sdist/wheel 包含同一许可证;tests/test_agent_run.py修正一个既有 strict-mypy 注解,使用公开ProviderStreamEvent,运行时行为不变。首轮 CI 失败与窄修复
首轮 exact head
22f195740a315633af2534221f1c57b8aaec184e的真实 Linux Actions run33510584072在 strict mypy 失败:Linux 类型环境中subprocess.CREATE_NEW_PROCESS_GROUP不存在,同时 Windows-only ignore 被判定为 unused。没有绕过、忽略或排除该检查。第二个普通提交
fc1bd7cab141ce8ad6f8b6b126b8034669f3532e引入 typed platform seam:Windows 使用CREATE_NEW_PROCESS_GROUP,POSIX 使用killpg/SIGKILL,无法确定的平台 fail closed;SWE-bench 复用同一 seam,并增加行为回归测试。该修复不使用Any掩盖、不增加 CI exclusion,也未 amend/rebase 旧提交。精确变更身份
fbab60f9a38bc4b49f0e730495d6207ea670bdd1fc1bd7cab141ce8ad6f8b6b126b8034669f3532e50f15f632e54e7d7f7a114554346647459c50ebc5677934c4791244d1b5a87d8183a484adccfe673验证
同一最终树已通过:
python:3.11-slim,Python 3.11.16 + mypy 2.3.1:32 files,0 issues--platform linux、--platform win32:全部 PASSgit diff --check:PASS.env,未进行 Provider、Docker 或 Harness 重跑仓库标准化原始验证还包括 YAML 1.2、CI 最小权限与 action pin、PEP 639、twine check、LICENSE 打包一致性和 fresh wheel Fake demo。
已有真实验收证据
本 PR 基于 exact main
fbab60f9a38bc4b49f0e730495d6207ea670bdd1。该 main 已在官方 SWE-bench Harness 中完成 DeepSeek 授权实跑:实例django__django-11133applied/resolved=true,resolved/total=1/1,infra failures=0。成功 artifact 保留在仓库外,不进入本 PR,也不会被本操作清理。合并后 GitHub 配置计划
仅在本 PR 新 exact head 的 Actions 全部成功、PR 普通 merge、merge SHA 自身 CI 再次成功后,custodian 才会按授权配置仓库 settings、安全能力和无 bypass 的
main-ci-gate。现有 owner/review ruleset 的审批语义不会修改。本 PR 不自动关闭 #1 或 #10;两个 Issue 在独立终态核验前保持 OPEN。
English appendix
Relates to #1 and Relates to #10. This PR standardizes repository governance with Apache-2.0/PEP 639 metadata, community and security documents, templates, Dependabot, and a least-privilege pinned CI workflow.
The first exact head
22f195740a315633af2534221f1c57b8aaec184eexposed a real Linux strict-mypy failure for Windows-only process-group symbols. The second ordinary commitfc1bd7cab141ce8ad6f8b6b126b8034669f3532eadds a typed fail-closed platform seam for Windows process groups and POSIXkillpg/SIGKILL, reuses it in SWE-bench, and adds regression coverage. It does not bypass, suppress, or exclude CI checks.Final identity: base
fbab60f9a38bc4b49f0e730495d6207ea670bdd1, headfc1bd7cab141ce8ad6f8b6b126b8034669f3532e, two commits, 16 paths, 835 additions / 9 deletions, stable patch-id50f15f632e54e7d7f7a114554346647459c50ebc. The repair delta is three paths, 68 additions / 6 deletions, stable patch-id5677934c4791244d1b5a87d8183a484adccfe673.The final tree passed focused tests, Linux-container mypy, native/Linux/Win32 strict mypy, Ruff, 334 tests with one explicit network skip, packaging and fresh-install acceptance, plus fixed-point Standards/Spec reviews with zero findings. Merge remains gated on successful Actions for this exact head and again for the merge SHA. Issues #1 and #10 remain open.