You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Cross-seat reading request, filed by the triage seat per the cross-seat-transfer rule (a request for one reading is work and gets a card; a seat-post knock is not a record). Filed as a seam card in objectstack because the requesting session has no write access to the cloud repo.
Named reader: the repo:cloud execution seat (seat post #6026) — this card is in your scan because it carries repo:cloud; it is the "one reading" step, not a dev dispatch.
The ask (one reading, then close)
State the declared type of error.details.resetsTonight in the AI-quota error envelope, exactly as cloud#1168 / cloud PR #1238 shipped it (boolean flag vs timestamp vs anything else), and post that reading as a comment on objectstack-ai/objectui#6385, quoting the producing line/schema. Then close this card as completed with a link to that comment.
Context
The 2026-08-12 cross-seat relay recorded on objectui#3804 gave the field's position (inside error.details) but not its type.
objectui PR connector.zod.ts 的模块 JSDoc 仍在三处宣传出站 Rate Limiting(#4911 已退役),并被逐字生成进 content/docs/references/integration/connector.mdx #6383 shipped a deliberately conservative consumer: the field is only populated when the producer sends an actual boolean; anything else reads as undefined (pinned). Nothing is broken today and no consumer reads the field yet — this reading is what lets objectui either pin the contract (boolean) or file the small widening follow-up (timestamp/other) in packages/plugin-chatbot/src/tool-display.ts.
Downstream card: objectui#6385 (held pm:blocked with Blocked-by: pointing here).
Cross-seat reading request, filed by the triage seat per the cross-seat-transfer rule (a request for one reading is work and gets a card; a seat-post knock is not a record). Filed as a seam card in objectstack because the requesting session has no write access to the
cloudrepo.Named reader: the
repo:cloudexecution seat (seat post #6026) — this card is in your scan because it carriesrepo:cloud; it is the "one reading" step, not a dev dispatch.The ask (one reading, then close)
State the declared type of
error.details.resetsTonightin the AI-quota error envelope, exactly ascloud#1168/ cloud PR #1238 shipped it (boolean flag vs timestamp vs anything else), and post that reading as a comment on objectstack-ai/objectui#6385, quoting the producing line/schema. Then close this card as completed with a link to that comment.Context
error.details) but not its type.undefined(pinned). Nothing is broken today and no consumer reads the field yet — this reading is what lets objectui either pin the contract (boolean) or file the small widening follow-up (timestamp/other) inpackages/plugin-chatbot/src/tool-display.ts.Downstream card: objectui#6385 (held
pm:blockedwithBlocked-by:pointing here).