feat: command.execute returns the lifecycle pairing id ({matched, commandId?})
CommandService.execute now returns a CommandExecution — the normalized result plus the commandId minted for its command/run/command/done records — and the wire admission value carries commandId exactly when matched, so the issuing client can correlate its RPC acknowledgment with the flow node the lifecycle events produce. apiproxy api/schema/handler, the connection fixture, and the TUI/plan/goal consumers follow the new shape.
This commit is contained in:
@@ -2,5 +2,5 @@
|
||||
# side as of the last confirmed-consistent state. Both languages carry equal authority;
|
||||
# after editing either side, bring the other along and re-record with:
|
||||
# pnpm run verify-translation-pairing --write packages/host/apiproxy/README.md
|
||||
README.md: 0e8699e513452030bfa4ffc62737df928c161603
|
||||
README.zh.md: 8b19d0357389f616ec8a4120beb2cf8d8d7686d8
|
||||
README.md: e450f7081998ce0810fc06ac688fd7214c362363
|
||||
README.zh.md: 6658f88ee3b37d1c487abb38456579ddaaba4b61
|
||||
|
||||
Reference in New Issue
Block a user