Skip to content

Commit 97fd70b

Browse files
thymikeeclaude
andcommitted
docs(registry): say the client adds one rule to the dispatch verdict
The JSDoc on resolveCommandDispatchDisclosure still said the daemon and the client cannot disagree, which stopped being true once the client gained its rule for a sent delegating composite. Co-Authored-By: Claude Opus 5.5 <[email protected]>
1 parent f801082 commit 97fd70b

1 file changed

Lines changed: 2 additions & 1 deletion

File tree

‎packages/command-registry/src/registry.ts‎

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -845,7 +845,8 @@ export function resolveCommandRecordingEffect(req: DispatchedCommand): Recording
845845
* Whether a failed request for this command can have reached the device, from its declared
846846
* recording effect: a read (`observes-app`) cannot have changed the app, a mutation may have, and
847847
* any other command gets no verdict. The daemon's request seam and the client's transport failures
848-
* both read this, so they cannot disagree.
848+
* both start from this; the client, which has no request ledger, adds one rule for a sent
849+
* delegating composite ({@link isDelegatingCompositeCommand}).
849850
*/
850851
export function resolveCommandDispatchDisclosure(
851852
req: DispatchedCommand,

0 commit comments

Comments
 (0)