weichen c02043f2c4 Require agent execution for every pull request merge ...

Why: The user requires all merges to follow agent-run synchronization, review, current-head CI and platform admission.

Evidence: Existing delivery stages and owner-only protection boundary reviewed; exact current Gitea Chinese labels verified from runtime resources.

Impact: Strengthen the merge executor rule only; retain human stage reviews, owner protection actions and actual CI requirements.

Refs: User instruction; merge-queue implementation plan U4/U5; Dev PR #519; Issue #518

2026-10-13 17:11:13 +00:00

..

adoption.md

Adopt the merged merge queue standards and implementation plan in the Dev candidate

2026-10-13 14:44:01 +00:00

architecture-baseline.json

Register the shared project scope dependency boundaries

2026-10-13 10:42:39 +00:00

architecture.yaml

Register the shared project scope dependency boundaries

2026-10-13 10:42:39 +00:00

delivery.md

Require agent execution for every pull request merge

2026-10-13 17:11:13 +00:00

facts.md

Bump frontend and backend pins; register account facts F5/F6

2026-10-13 06:41:34 +00:00

governance.md

Keep fixed-candidate evidence outside the measured checkout

2026-10-13 07:53:47 +00:00

lib-deps-allowlist.txt

Pin the D1 heads and cover the adapter modules

2026-10-03 13:47:02 +00:00

merge-queue.md

Adopt the merged merge queue standards and implementation plan in the Dev candidate

2026-10-13 14:44:01 +00:00

platform-admission.md

Prepare exact required CI settings for the platform owner

2026-10-13 08:21:58 +00:00

tool-adaptation-matrix.md

Adopt the merged merge queue standards and implementation plan in the Dev candidate

2026-10-13 14:44:01 +00:00

tool-adaptation-zcode.md

Make development gates preserve work and verifiable evidence

2026-10-05 12:36:02 +00:00