2 Commits

Include renames

Author	SHA1	Message	Date
host	1ff8906aee	feat(repos): 仓库接入预检 + codexsvc deploy key 配给脚本 ... 本机 https 到 GitHub 常被出口策略挡、ssh 才通（2026-10-30 实测），而新项目填 https 私有仓会在 worker 里花几分钟超时 才失败。控制面不存仓库凭证的设计不动，缺的是建项目前的 快速预检与按仓库通用化的配 key 流程： - cloud.repos.check_repo_access：只跑 git ls-remote HEAD， 不 clone、不写盘、不改库；失败返回 (False, 原因)，https 失败时追加改走 git@ 形的提示；CLI python3 -m cloud.repos check <url>，退出码 0/1，只打印结果与原因。 - deploy/provision_codexsvc_key.sh：主机上以 root 跑，为 codexsvc 生成/复用 ed25519 key（绝不覆盖已有 key），只 打印公钥（私钥绝不打印），--check 时以 codexsvc 身份跑 ls-remote，通了才算配好。 - 内层沙箱边界诚实说明：Docker 任务内层本就是 danger-full-access（见 sandbox.py 注释），外层 Docker/gVisor 才是防线；宿主级 bwrap workspace-write 的 fresh proc 在嵌套 pidns 下是内核 EPERM、/tmp 不隔离——这些是上游 codex 二进制 与内核的边界，本批不谎称在仓库代码里修掉，只把仓库接入 这一档做成可重复流程。 单测：test_project_repo 20 项全过（新增 check 5 项）。	2026-10-30 01:39:46 +08:00
host	bed3fc0dff	Project repo_url: worker can run tasks from any git repo ... Projects gain repo_url (validated: https:// or git@ only, no userinfo/password, no file:// or local paths; old DBs get the column via idempotent ALTER in both SQLite and Postgres init). Worker resolves a project's repo_url to a local checkout under --repos-dir (default ./repos) before dispatch: clone if absent, verify remote origin matches and fetch if present, never force reset/clean, never push (push needs write credentials the control plane does not store). Resolve failure fails the task with a clear error, never completed. Docker workers need repos_dir under a same-path extra mount (e.g. /var/lib/codex-app-server/repos). Also: driver-missing test is now mocked instead of depending on the host really having no psycopg driver installed. Deploy package: Caddyfile template exposing only /webhooks/* and /oauth/* (tasks/projects/admin stay 403) plus a webhook-secret generator script that never prints the secret. Tests: host 27 pass, cloud 286 pass (8 skipped are environment-dependent real-Postgres tests).	2026-10-26 04:16:11 +08:00