actions

4 modules

• actions/action_bridge.ts

  Bridge functions to derive RouteSpec and SseEventSpec from ActionSpec.

  Action specs define the contract (method, input/output, auth, side effects). Bridge functions produce transport-specific specs from them. HTTP-specific concerns (path, handler) come from options.

• actions/action_codegen.ts

• actions/action_registry.ts

  ActionRegistry — query and filter utility over ActionSpecUnion[].

• actions/action_spec.ts

  Action spec types — the canonical source of truth for action contracts.

  Extracted from zzz's action system. Action specs define method, kind, auth, side effects, and input/output schemas. Bridge functions in action_bridge.ts derive RouteSpec and SseEventSpec from them.

  TODO @action-system-review The action system (action_spec, action_registry, action_codegen, action_bridge) will evolve significantly with the saes-rpc quest. Current state: bridge is stable, registry and codegen are partially stub API. Search for @action-system-review across the actions/ and routes/ modules.