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.
2026-07-27 21:05:15 +08:00
parent 2ebaa30c6d
commit 6d2e5a7cd7
21 changed files with 85 additions and 55 deletions
@@ -32,7 +32,8 @@ export const commandExecuteRequestSchema = z.object({
  line: z.string(),
 }) satisfies z.ZodType<Wire<RequestPayload<'command.execute'>>>

-/** command.execute response value: pure admission — outcomes ride the logged lifecycle events, never this response. */
+/** command.execute response value: pure admission — outcomes ride the logged lifecycle events; commandId (present exactly when matched) correlates with them. */
 export const commandExecuteValueSchema = z.object({
  matched: z.boolean(),
+  commandId: z.string().min(1).optional(),
 }) satisfies z.ZodType<Wire<ResponseValue<'command.execute'>>>