Pin proposal status and start the controlled merge queue trial #489

Merged
weichen merged 5 commits from feature/proposal-status-20261012 into main 2026-10-14 02:30:52 +00:00
5 Commits
Author SHA1 Message Date
weichen 5e6bf4aa05 Pin proposal status and start the controlled merge queue trial
ci / svc-realcombo (pull_request) Successful in 1m46s
ci / test (pull_request) Successful in 5m10s
ci / test-pg (pull_request) Successful in 7m22s
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
weichen 839b2a3af0 Synchronize proposal status delivery with the current integration baseline
Why: restore the assigned task against the current target while retaining its original baseline and all newer component capabilities.
Evidence: startup precheck and real parent/component sync receipts capture the original conflict; Documents PR89 was independently reviewed, merged by the agent, and its tree verified.
Impact: include origin/main and the delivered documentation merge 7bd4e17827d4c7c88647bf3c9199c495b60cb107 without rewriting task history or pushing waiting branches.
Refs: Dev PR #489; Documents PR #89; merge queue Issue #518; user takeover authorization on 2026-10-14
2026-10-14 01:18:47 +00:00
weichenandCursor 3e7f036008 Link the status pin card to pull request 489
ci / svc-realcombo (pull_request) Successful in 2m20s
ci / test-pg (pull_request) Successful in 2m51s
ci / test (pull_request) Successful in 4m49s
Why: the delivery record needs the Dev pull request that pins the approved proposal text.
Evidence: the API returned Dev pull request 489.
Impact: task metadata only.
Refs: .task/feature-proposal-status-20261012.md
Co-authored-by: Cursor <cursoragent@cursor.com>
2026-10-12 15:54:09 +00:00
weichenandCursor f97bcb45f7 Pin the approved U8, U7, and export status
ci / svc-realcombo (pull_request) Successful in 3m7s
ci / test-pg (pull_request) Successful in 3m39s
ci / test (pull_request) Successful in 6m23s
Why: the proposal text now records the 2026-10-12 approval and corrects the RDM export note, and Dev has to point at that documents commit.
Evidence: Documents pull request 89 is b8df6f3. This pin does not claim those implementation pull requests are merged.
Impact: modules/documents moves from cb7e254 to b8df6f3. No service or login behavior changes.
Refs: modules/documents, .task/feature-proposal-status-20261012.md
Co-authored-by: Cursor <cursoragent@cursor.com>
2026-10-12 15:53:42 +00:00
weichen 77ef1359f9 Record the task card for feature-proposal-status-20261012
Why: establish the authorized task workspace and its initial baseline.

Evidence: preserved precheck receipt in .task/feature-proposal-status-20261012.md; R0=cd61bbb112eea6a210a64e84f2cef00b0d64bfc1.

Impact: task metadata only; the feature workspace starts at cd61bbb112.

Refs: .task/feature-proposal-status-20261012.md
2026-10-12 15:53:09 +00:00