Pin modules/documents to 2e9c3bc (Documents #119), which records the 2026-10-21 GenUI prod upgrade: prod now runs dev@5360884 (schema v25 → v51) and both prod and pg1 are managed by scripts/svc.sh in the main checkout.
The upgrade itself was an out-of-repo operation (backups, rehearsal on a DB copy, adopt → agent-system migrate → svc.sh prod deploy); its facts and verification are recorded on the task card.
Why: the closure doc and the Dev pin should reflect the upgraded prod.
Evidence: Documents #119 CI success at 518e381; agent-exec receipts on the task card.
Impact: documentation pin and task card only.
Refs: task card .task/feature-genui-prod-upgrade-docsync.md (same document as this PR description).
## Summary
Pin `modules/documents` to 2e9c3bc (Documents #119), which records the 2026-10-21 GenUI prod upgrade: prod now runs `dev@5360884` (schema v25 → v51) and both `prod` and `pg1` are managed by `scripts/svc.sh` in the main checkout.
The upgrade itself was an out-of-repo operation (backups, rehearsal on a DB copy, adopt → `agent-system migrate` → `svc.sh prod deploy`); its facts and verification are recorded on the task card.
Why: the closure doc and the Dev pin should reflect the upgraded prod.
Evidence: Documents #119 CI success at 518e381; agent-exec receipts on the task card.
Impact: documentation pin and task card only.
Refs: task card `.task/feature-genui-prod-upgrade-docsync.md` (same document as this PR description).
Why: establish the authorized task workspace and its initial baseline.
Evidence: preserved precheck receipt in .task/feature-genui-prod-upgrade-docsync.md; R0=e634608d97333354c3ead85d47c9e9e368a992a0.
Impact: task metadata only; the feature workspace starts at e634608d97.
Refs: .task/feature-genui-prod-upgrade-docsync.md
Why: The card must carry the authorization, the out-of-repo upgrade steps,
the verification results and the agent-exec receipts for both units.
Evidence: Receipts /tmp/genui-prod-upgrade-doc/{docs,dev}-run.json;
Documents #119 CI success at 518e381.
Impact: Task card only.
Refs: Documents #119
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: close the task card inside its own PR so landing it needs no post-merge backfill or separate close PR.
Evidence: .task/feature-genui-prod-upgrade-docsync.md -> .task/archive/feature-genui-prod-upgrade-docsync.md; status 已完成（合入前闭合）; PR #679https://git-home.u1680832.nyat.app:30319/weichen/Agent-System-Dev/pulls/679.
Impact: task metadata only; the card is archived within PR #679 and lands with its merge commit.
Refs: task.sh close --self
weichen
merged commit ccb6dfaa9c into main2026-10-21 13:18:37 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
Pin
modules/documentsto 2e9c3bc (Documents #119), which records the 2026-10-21 GenUI prod upgrade: prod now runsdev@5360884(schema v25 → v51) and bothprodandpg1are managed byscripts/svc.shin the main checkout.The upgrade itself was an out-of-repo operation (backups, rehearsal on a DB copy, adopt →
agent-system migrate→svc.sh prod deploy); its facts and verification are recorded on the task card.Why: the closure doc and the Dev pin should reflect the upgraded prod.
Evidence: Documents #119 CI success at 518e381; agent-exec receipts on the task card.
Impact: documentation pin and task card only.
Refs: task card
.task/feature-genui-prod-upgrade-docsync.md(same document as this PR description).Why: The card must carry the authorization, the out-of-repo upgrade steps, the verification results and the agent-exec receipts for both units. Evidence: Receipts /tmp/genui-prod-upgrade-doc/{docs,dev}-run.json; Documents #119 CI success at 518e381. Impact: Task card only. Refs: Documents #119 Co-authored-by: Cursor <cursoragent@cursor.com>