Compare commits

..
Author SHA1 Message Date
weichen 2e9c3bc1d8 Merge pull request 'Record the GenUI prod upgrade to dev@5360884 under svc' (#119) from feature/genui-prod-upgrade-docsync into main
governance / governance (push) Successful in 17s
2026-10-21 12:48:22 +00:00
agent-exec-transportandCursor 518e381e4d Record the GenUI prod upgrade to dev@5360884 under svc
governance / governance (pull_request) Successful in 15s
Why: prod was upgraded on 2026-10-21 (schema v25 to v51) and both prod and
pg1 are now managed by scripts/svc.sh; the closure doc still described the
manual prodctl.sh layout.
Evidence: agent-exec unit documents-genui-prod-upgrade-docsync (cursor,
attempt 1, terminal=success); one bullet changed.
Impact: Documentation only.
Refs: Dev task feature/genui-prod-upgrade-docsync

Co-authored-by: Cursor <cursoragent@cursor.com>
2026-10-21 12:47:24 +00:00
weichen fcea46602b Merge pull request 'Sync GenUI prod deploy entry with current runtime layout' (#118) from feature/genui-prod-ops-docsync into main
governance / governance (push) Successful in 14s
2026-10-21 10:29:07 +00:00
agent-exec-transportandCursor 244477e0be Sync GenUI prod deploy entry with current runtime layout
governance / governance (pull_request) Successful in 14s
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>
2026-10-21 10:28:13 +00:00
weichen f361071034 Merge pull request 'Document IAM U1-U7 implementation completion (L1 plan revision 3 merged)' (#117) from feature/iam-u1-u7-implementation-record into main
governance / governance (push) Successful in 25s
2026-10-20 07:21:59 +00:00
@@ -93,9 +93,17 @@ Frontend #58/#59,Dev #381/#382/#387/#388):工具描述缺「何时用」
不嵌套分发;提案 `2026-10-12-generative-ui-bclass-help-intent.md`);其余仍逐条评审。
- 人类可用性对照以 owner 实际使用替代(2026-10-11 用户裁定),本轮体感「初步不错」,
小问题另行修复。
- 部署与运行验收:本机 `prod` 实例已登记(`scripts/svc.sh prod`,`--auth on`,
PG `pg1/prod`,来源 `dev@c76f2bb`+后端 nil-card 修复);验收覆盖启禁、present、
B/C 类动作、项目聚合、未登录 401。
- 部署与运行验收:2026-10-12 本机 `prod`(127.0.0.1:8787,`--auth on`,PG `pg1/prod`)
两刀部署至 `dev@b4649d7`(含 Backend#173/#174);验收覆盖启禁、present、B/C 类动作、
项目聚合、未登录 401。2026-10-21 经用户授权升级至 `dev@5360884`,库 schema v25→v51
(升级前已备份 PG 与运行目录,并在库副本上完整演练);`prod` 与 `pg1` 均由 Dev 主检出
`scripts/svc.sh` 管理(`runtime/prod`、`runtime/pg1`),DSN 只经环境变量
`AGENT_SYSTEM_DSN` 交付、不进命令行。开启认证需超级管理员:账户 `superadmin`,凭据文件
`runtime/prod/super-admin.env`(0600),`deploy/start/restart` 时以 `AGENT_SYSTEM_ENV_FILE`
指向该文件(svc 不持久化该凭据,缺失时服务拒绝启动);原 `admin` 账户保留。升级后验证
healthz/readyz/UI 200、superadmin 登录、未登录 401;GenUI 功能验收清单未重跑(NOT_RUN)。
经验:schema v27 之前的旧库经 svc 部署前,须先以候选二进制执行 `agent-system migrate`
(svc 身份门禁的 identity ensure 不做迁移)。
## 三、结论