weichen/Agent-System-Documents
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
413 Commits 83 Branches 0 Tags
main
Commit Graph
8 Commits
Author SHA1 Message Date
agent-exec-transportandCursor f5417fb721 Record the 2026-10-21 GenUI prod acceptance rerun
governance / governance (pull_request) Successful in 14s
Details 
Replace the NOT_RUN note in the deployment acceptance bullet with the
rerun result on dev@5360884: the 10-12 API checklist passes (11 items,
no model calls), run through a temporary genui-accept role and account
that were disabled afterwards. Also record that project.create now comes
only from roles, so admin cannot create projects until a role is assigned.

Why: the upgrade record still listed the GenUI acceptance as NOT_RUN.
Evidence: agent-exec unit documents-genui-prod-acceptance-20261021 (cursor, attempt 1, terminal=success); prod API replay VERDICT PASS on 2026-10-21.
Impact: documentation only.
Refs: Dev task fix/genui-prod-upgrade-followups.
Co-authored-by: Cursor <cursoragent@cursor.com>
 2026-10-21 13:33:58 +00:00
agent-exec-transportandCursor 518e381e4d Record the GenUI prod upgrade to dev@5360884 under svc
governance / governance (pull_request) Successful in 15s
Details 
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
agent-exec-transportandCursor 244477e0be Sync GenUI prod deploy entry with current runtime layout
governance / governance (pull_request) Successful in 14s
Details 
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 e39d327850 Record GenUI prod-acceptance action fixes on the usage guide 
Why: Capture nil-card panic and intent data-flatten field fixes found
during local prod acceptance without revising the final closure verdict.
Evidence: Backend#173 #174; prod action checklist
Impact: Field-fix log lists the two hotfixes and their PRs.
Refs: GenUI prod deploy; fix track
 2026-10-12 04:17:07 +00:00
weichen 66ddd37870 Note Generative UI prod instance acceptance on the usage guide 
Why: Record that the known-boundary production deploy/acceptance ran
on the local prod svc instance with auth and PG.
Evidence: scripts/svc.sh prod list; acceptance API checklist
Impact: Usage guide boundary list no longer says deploy is pending.
Refs: GenUI prod deploy task
 2026-10-12 04:08:58 +00:00
weichenandCursor 16cafca00c Approve Generative UI auto-trigger opt-in design 
Why: Capture the fixed opt-in/budget/anti-self-trigger decisions and
update the usage guide boundary list.
Evidence: proposal r1 status approved
Impact: Authority for backend auto-present implementation.
Refs: plan GenUI boundaries T2/T3

Co-authored-by: Cursor <cursoragent@cursor.com>
 2026-10-12 03:46:26 +00:00
weichenandCursor 7fbfad1851 Approve B-class allowlist for help and intent actions 
Why: Record the independent U5-style review for the first two B-class
surface actions and update the usage guide allowlist note.
Evidence: proposal r1 status approved; usage doc API table updated.
Impact: Documents authority for backend whitelist implementation.
Refs: U5 action-scope r2; plan GenUI boundaries 2026-10-12

Co-authored-by: Cursor <cursoragent@cursor.com>
 2026-10-12 03:19:03 +00:00
weichen 877d0683cd Add the Generative UI usage guide and U1-U6 evaluation record (final) 
Why: The direction closes at U7 - the master record needs its
companion usage guide (enable/generate/revise/act/disable for owners)
and the combined evaluation record covering every landed increment
with its evidence chain and known boundaries.

Evidence: Live E2E on dev@b634a27 (real MiniMax-M3): progress page
presented autonomously, conversation surfaces=2, project aggregation
returns cross-conversation pages under the owner scope; receipts in
Dev task feature/generative-ui-u7-acceptance.

Impact: Documents-only (new guide + index closeout).

Refs: r2 master record; U5 scope r2; Dev task
feature/generative-ui-u7-acceptance
 2026-10-12 02:47:27 +00:00