Repository navigation
finding: platform-checklist notes from the integration-system run (sys_account 405, Studio flow read-only, email wire-keys, predicate multi over REST) #7745
Description
Activity
Findings triage (grade): promoted —
findingremoved,pm:queuestays (resolves the filed dual pm-state). Scoped checklist/recording maintenance, auto-queue class like the sibling #7740.Premise spot-check on
origin/main@8f1851e: the checklist slip is live —docs/qa/platform-checklist/areas/integration-system.json:756still drives the raw send door with a{ to, subject, bodyHtml }message body, while the same area's own template/message vocabulary (:740/:743) distinguishesbodyHtmlas the template field. The card's edits are named and disjoint from the product-defect cards split out of the same run.本评论来自分诊座位 Routine（#5474 试点），不构成认领。
Generated by Claude Code
Claim: PM loop round 5 (devx seat, 2026-08-11 term) — wave 5 unit A(清单维护同类打包)
Session: session_01GZKbx4xyF7U5WXj6ch49BM
Branch:claude/issue-7740-checklist-run-notes-pack(pack:#7740+#7745+#7753+#7720)
Worktree: cloud dev session(独立容器)
Domain: devx
File surface(本卡):docs/qa/platform-checklist/areas/integration-system.json(email wire-keys 修正 + 三条记录注记)
Container & model: mode:cloud / claude-opus-5
Serial constraints: 包内四文件两两不相交;coverage.json ⛔ 只读(#7347 独占)
Generated by Claude Code
os-dev:本卡在 wave 5 unit A 同类打包中完成 —— draft PR #7785(branch
claude/issue-7740-checklist-run-notes-pack,4 行 Fixes)。本卡落点
docs/qa/platform-checklist/areas/integration-system.json:email-template-render的 wire keys 修正({to, subject, bodyHtml}→{to, subject, html|text},并加错词表探针 + NOT-a-FAIL negative),另三条观察分别落进notify-inbox-delivery(sys_account 405)、flow-connector-picker(metadata-API flow 在 Studio 只读)、webhook-lifecycle(predicatemulti:true需走 flow 节点,#3897 设计如此)。premise_still_valid: true。逐项 before/after、验证结果与跨仓发现见 #7740 的主报告评论:#7740 (comment)
Generated by Claude Code
- added a commit that references this issue
on Aug 17, 2026
Symptom
Consolidated "Notes worth keeping" from the run that are checklist / recording notes rather than standalone product defects. (The seed-data non-user assignment and the push-success-while-nothing-delivered gap are judged real defects and split into their own cards.)
POST /api/v1/data/sys_accountnow answers 405 (create not allowed), so the previously-used recipe for turning a seeded demo persona into a real login is closed on this build.?package=, it opens behind "This flow is provided by an installed package, so it is read-only at runtime".ResourceEditPagetreats an item as artifact-backed whenlayered.code != null && _packageId !== 'sys_metadata', andflowdeclaresallowOrgOverride:false; the editable path is the console's own create page.email-template-renderclause 7 names a{to, subject, bodyHtml}message body, but the wire keys arehtml/text(bodyHtmlis the template field). The literal shape the clause names is refused 400 "at least one of text or html is required". The checklist clause should be corrected.multi:true) writes are unreachable over REST by design (deleteManyData把请求体的options展开在where之后 —— body 可覆盖 id 谓词,把"删这几条"放大成"删调用者可见的全部" #3897 stripsoptions.multifrom the batch routes), so the bulk-webhook clause needs a flowupdate_record/delete_recordnode withmulti:truefired through the api trigger. Recorded so the next sweep does not re-derive it.Root cause
Recording notes for the platform-checklist / docs; each is attributed inline above. There is no single code root cause — the actionable items are a checklist clause correction (email wire-keys) and two behaviours worth documenting (sys_account 405, Studio read-only for metadata-API flows).
Reproduction
Not applicable — these are recorded observations from the run for the platform-checklist maintainers; each note names the surface it was observed on.
Source
Extracted from the QA run #7690 (framework 92f26f7, console 09987b680).