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
{{ message }}
Repository navigation
Commit 40be3e3
Browse filesBrowse the repository at this point in the historyBrowse files
Require the current saved-message format for Sidekick records
Every saved Sidekick message carries an opaque ID and a UI or attachment
origin. Both are required: a record missing either is unreadable rather
than read as an earlier shape, and nothing projects a substitute origin
for one. The chat item carries the ID and origin the record holds, so the
live attachment's own saved message is found by that ID alone.
There is one supported format for this data, so the stored records move to
it in place: the two pinned chat fixtures gain those fields on their
message records, and each receipt restates its own byte count and digest.
The architecture and REPL specification say the fields are required.
Formatting of the files this feature already touches is brought to oxfmt's
output, which `deno task lint` checks.
Copy file name to clipboardExpand all lines: architecture.md
+5-4Lines changed: 5 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8666,9 +8666,10 @@ it or release its reservation. Exact-handle Stop joins producer cleanup before
8666
8666
release, and an old handle cannot stop a successor. Entry work remains owned by
8667
8667
ReplSession.
8668
8668
8669
-
Message records retain an optional opaque ID and UI/attachment origin beside the
8670
-
legacy numeric `turn`. The reference is published only after the message append
8671
-
is acknowledged. Legacy records are read without rewriting or inventing IDs.
8669
+
Every message record carries an opaque ID and a UI/attachment origin beside the
8670
+
conversation-scoped numeric `turn`, and a record missing either is unreadable
8671
+
rather than assumed. The reference is published only after the message append
8672
+
is acknowledged.
8672
8673
ACP-origin acknowledgement clears neither composer nor draft takeover. The live
8673
8674
root indexes established IDs for passive observation; that index supplies no
8674
8675
restart, resend or provider-acceptance authority. An earlier answer followed by
@@ -8842,7 +8843,7 @@ and categorization rather than clarify them, so both stay exactly as written.
8842
8843
| background automation | work designed to proceed without ongoing user or agent attention, with its persistence and recovery guarantees supplied by the workflow host |
8843
8844
| REPL | the foreground interactive environment for experimenting with and testing components; replay restores recorded execution state, while the user or agent handles differences between that state and the live environment |
8844
8845
| REPL history | the immutable ordered execution records the REPL reads from the durable journal and projects into `ReplModel`; the History surface presents this read model and is not itself a journal [Reference](#the-private-repl-composition-kernel). |
8845
-
| legacy message ID | the number Sidekick retains to identify a saved person message within its conversation; fixed once saved, possibly noncontiguous, and independent of the turn numbers recorded by Core. The conversation and message ID together form its lookup key |
8846
+
| message ID | the opaque identity Sidekick retains for a saved person message, written before its turn and never rewritten. The conversation and message ID together form its lookup key, and the conversation-scoped numeric `turn` beside it identifies no turn |
8846
8847
| turn | one request to an agent, together with the response or failure from that request |
8847
8848
| middleware | applied by the lexical structure, used by runtime execution [Reference](#two-layers). |
8848
8849
| workflow run | a workflow being carried out with its progress and outcome recorded durably; document executions perform its work, while ongoing effects remain scoped to the document execution in which they run [Reference](#workflow-runs). |
0 commit comments