Sync the GenUI closure doc's "部署与运行验收" bullet with the current runtime layout.
prod (127.0.0.1:8787, auth on, PG pg1/prod) runs dev@b4649d7 from the preserved runtime directory Agent-System-Dev-svc-preserve-genui-prod/runtime/prod; the binary lacks identity ensure/verify, so scripts/svc.sh cannot take it over and it is started/stopped manually via prodctl.sh with the DSN delivered only through AGENT_SYSTEM_DSN.
PG instance pg1 moved into the Dev main checkout runtime/pg1 on 2026-10-21 and is managed by scripts/svc.sh pg1.
Upgrading prod needs a PG backup and an assessment of the one-way schema migration from v25, under separate authorization.
Why: the bullet still said scripts/svc.sh prod from dev@c76f2bb, which no longer matches reality.
Evidence: agent-exec unit documents-genui-prod-ops-docsync (cursor, attempt 1, terminal=success); one bullet changed.
Impact: documentation only.
Refs: Dev task feature/genui-prod-ops-docsync.
## Summary
Sync the GenUI closure doc's "部署与运行验收" bullet with the current runtime layout.
- prod (127.0.0.1:8787, auth on, PG `pg1/prod`) runs `dev@b4649d7` from the preserved runtime directory `Agent-System-Dev-svc-preserve-genui-prod/runtime/prod`; the binary lacks identity ensure/verify, so `scripts/svc.sh` cannot take it over and it is started/stopped manually via `prodctl.sh` with the DSN delivered only through `AGENT_SYSTEM_DSN`.
- PG instance `pg1` moved into the Dev main checkout `runtime/pg1` on 2026-10-21 and is managed by `scripts/svc.sh pg1`.
- Upgrading prod needs a PG backup and an assessment of the one-way schema migration from v25, under separate authorization.
Why: the bullet still said `scripts/svc.sh prod` from `dev@c76f2bb`, which no longer matches reality.
Evidence: agent-exec unit `documents-genui-prod-ops-docsync` (cursor, attempt 1, terminal=success); one bullet changed.
Impact: documentation only.
Refs: Dev task `feature/genui-prod-ops-docsync`.
Why: The closure doc still said prod is managed by `scripts/svc.sh prod`
from dev@c76f2bb; prod actually runs dev@b4649d7 from a preserved runtime
directory with manual prodctl.sh lifecycle, and pg1 moved under svc.
Evidence: Implemented by agent-exec unit documents-genui-prod-ops-docsync
(cursor, attempt 1, terminal=success); diff touches one bullet only.
Impact: Documentation only; no code or runtime change.
Refs: Dev task feature/genui-prod-ops-docsync
Co-authored-by: Cursor <cursoragent@cursor.com>
weichen
merged commit fcea46602b into main2026-10-21 10:29:07 +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
Sync the GenUI closure doc's "部署与运行验收" bullet with the current runtime layout.
pg1/prod) runsdev@b4649d7from the preserved runtime directoryAgent-System-Dev-svc-preserve-genui-prod/runtime/prod; the binary lacks identity ensure/verify, soscripts/svc.shcannot take it over and it is started/stopped manually viaprodctl.shwith the DSN delivered only throughAGENT_SYSTEM_DSN.pg1moved into the Dev main checkoutruntime/pg1on 2026-10-21 and is managed byscripts/svc.sh pg1.Why: the bullet still said
scripts/svc.sh prodfromdev@c76f2bb, which no longer matches reality.Evidence: agent-exec unit
documents-genui-prod-ops-docsync(cursor, attempt 1, terminal=success); one bullet changed.Impact: documentation only.
Refs: Dev task
feature/genui-prod-ops-docsync.