Repository navigation
docs(agents): an authored events bag is refused by objectui validate once PR objectui#11069 lands (objectui#5250) - #12050
Conversation
…te` and named by `objectui check` (objectui#5250) AGENTS.md section 5 #4 and skills/objectui/rules/protocol.md said an `events` bag that arrives as data is "kept, judged by nothing and run by nothing". Once PR objectui#11069 (objectui#5250 slice A) lands, `objectui validate` and `objectui check` judge a document through the strict authoring face, which refuses `events` as an undeclared key. The two sentences now say that; the tolerant face still keeps the bag, and nothing runs it. Must merge together with or after PR objectui#11069, never before. Claude-Session: https://claude.ai/code/session_01MgfduSkFrfM3eorB3UGfAU Co-authored-by: Claude <noreply@anthropic.com>
…ssion (objectui#5250)
skills/objectui/guides/project-setup.md said `objectui check` exits
non-zero on unreadable JSON only. Since objectui#4795 a `${…}` refused on
a text key its node never evaluates fails the run too. One sentence in the
CLI table.
Claude-Session: https://claude.ai/code/session_01MgfduSkFrfM3eorB3UGfAU
Co-authored-by: Claude <noreply@anthropic.com>
This PR now also corrects
|
维护者速读(终稿)PR objectui#12050 · objectui#5250 的受管面配套 · **改了什么:**两份写给 AI 的规程里,改正三句话:
**为什么改:**PR objectui#11069 让命令行校验改用严格模式,没有渲染器读取的键会被直接拒绝。规程如果还写着「没人检查」,AI 会以为写了也无害,或者不把校验报错当回事。 **风险与代价(含回滚):**只改三句文字,不动代码,也不发版。
**席位意见:**同意合并。措辞已对照 PR objectui#11069 的实际行为核对: **你要做的:**PR objectui#11069 合并后(或同时),以授权账户批准本 PR。批准后由席位放行进合并队列。 Generated by Claude Code |
Part of #5250
Merge order: this PR merges together with or after PR objectui#11069 (slice A of objectui#5250), never before it. Until slice A lands, the sentence it replaces is still true.
Clause-②: no
What changed
One sentence in each of two governed files, both about an authored
eventsbag:AGENTS.md, section 5, commandment Add default props to all components to prevent collapse in designer #4 (the action system): 「…so one that arrives as data is kept, judged by nothing and run by nothing.」skills/objectui/rules/protocol.md, the paragraph that begins 「DO NOT author aneventsbag」: the same sentence.Both now say what is true once PR objectui#11069 lands. A typed literal refuses the bag. One that arrives as data is refused by name as an undeclared key by
objectui validate, and named the same way byobjectui check; both judge through the strict authoring face (objectui#5250). The tolerant zod face is.passthrough(): it still keeps the bag, and nothing runs it.Nothing else changes.
skills/objectui/SKILL.mdsays only 「kept and run by nothing」 about the tolerant face. That stays true, so it is not touched.Why
PR objectui#11069 moves
objectui validateandobjectui checkontoStrictAnyComponentSchema. Probed on that PR's merged head: atextnode and abuttonnode, each carrying aneventsbag, are refused by the strict face with oneunrecognized_keysnamingevents, and accepted by the tolerantsafeValidateSchema. After that PR lands, 「judged by nothing」 would be false in the instruction file every agent reads first, and in the published skill.Gates
Head
91845ce7c, basemain3c3115e38. Each exit code was captured before any pipe.node scripts/check-governed-queue-guard.mjs --test AGENTS.md skills/objectui/rules/protocol.md: exit 3,GOVERNED — 2 of 2 path(s) are on a governed surface(AGENTS.md,skills/**). This PR stays draft and lands only after an APPROVED review by an authorized approver.check:skills-pathsexit 0 (skills/ — 29/29 resolve);check:skill-eval-tokensexit 0;check:control-bytesexit 0;check:new-line-citationsexit 0 (0 new citation(s));docs:check-linksexit 0;check-changeset-presenceexit 0 (no released source changed, so no changeset is owed).check:skill-examplesexited 2,PRECONDITION NOT MET(it needs 12 packages built). The edited paragraph carries no code example. Declared to CI.维护者速读(草稿)
改了什么:两份写给 AI 的规程里各改一句话:仓库根的
AGENTS.md,和对外发布的技能包skills/objectui。原句说作者写进元数据的events事件包「没有任何东西检查」。现在改成 PR objectui#11069 合并之后的事实:objectui validate会按名字拒绝它,objectui check也会点名它。为什么改:PR objectui#11069 让命令行校验改用严格模式,
events这种没有渲染器读取的键会被直接拒绝。规程里如果还留着「没人检查」,AI 会以为写了也无害,或者不把校验报错当回事。风险与代价(含回滚):只改两句文字,不动代码,也不发版。唯一的风险是合并顺序:如果先于 PR objectui#11069 合并,这两句话会提前变成假话,所以必须和它一起合并,或在它之后合并。回滚就是撤销本 PR,只涉及两处文字。
席位意见:
你要做的:在 PR objectui#11069 合并的同时或之后,审阅这两句话并批准本 PR。
Generated by Claude Code