| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
fix(review): cover list-form placeholders, de-link the security pointer - PLACEHOLDER_RE now also matches list-wrapped placeholders ("- （…）"), closing the mixed-draft bypass where every section but 证据 is filled and its placeholder line slipped through - flagged independently by three reviewers - the bug template's relative spec link resolves against the repo root in issue-form rendering contexts and would 404 (known platform pitfall); the plain repository path keeps the guidance without the broken link Refs #614 Co-Authored-By: Claude Code <noreply@anthropic.com> | 10 天前 | |
ci: run CI on main pushes and gate releases with go test PR events were the only automated evidence point: a broken test could merge with red PR CI (d1714f0 landed via !592 with run 419 FAILED) and nothing would re-examine the tip of main until the next PRs started failing (all PR CI blocked until the fix landed). - both ci.yml gain on.push.branches: [main] alongside the pull_request trigger, so every merge or direct push to main leaves its own CI record and go-test evidence no longer exists only at PR time - release.yml preflight gains a go test ./... step after the version sync checks, so a release cut while main CI is missing or red still hits a unit-test gate - sync the trigger documentation in spec/delivery/ci-workflows.md (must-list, hierarchy diagram, trigger section, release section), spec/workflows/ai-local-development-workflow.md, spec/foundations/code-quality-gates.md, spec/delivery/release-process.md, and AGENTS.md Acceptance evidence for the push trigger lands post-merge as the first main-branch CI run, per the issue's acceptance criteria. Refs #618 Co-Authored-By: Claude Code <noreply@anthropic.com> | 16 天前 |