weichen 5e6bf4aa05 Pin proposal status and start the controlled merge queue trial ...

Why: retain the approved status changes and current documentation while adopting the already approved manual delivery window after real platform validation.
Evidence: original startup, conflict resolution, combination test and writer inventory receipts are preserved in the task card; independent Doc89 and platform replay reports are referenced. Final candidate CI and review remain required.
Impact: publish the delivered Documents merge, manual trial policy and truthful capability state; keep all workflow triggers/checks and original task baseline unchanged.
Refs: Dev PR #489; Documents PR #89; Issue #518; approved merge queue implementation plan r1; user continuation authorization on 2026-10-14

2026-10-14 02:10:35 +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

Pin proposal status and start the controlled merge queue trial

2026-10-14 02:10:35 +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

Pin proposal status and start the controlled merge queue trial

2026-10-14 02:10:35 +00:00

tool-adaptation-zcode.md

Make development gates preserve work and verifiable evidence

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