[alob-mtc]

RunnerQ Cloud commands for the TypeScript SDK, at parity with the Go SDK. With allowControl: true, a worker's agent advertises and serves the seven activities.* commands, so the console no longer shows it as read-only.

What's in it

• Storage contract: CommandStorage / isCommandStorage and the command types, in runnerq/storage.
• PostgresStorage.applyCommand: a port of Go's SQL covering cancel (optionally cascading to descendants), retry (optionally resetting attempts), run_now, reschedule, set_priority, delete and signal.
  • A command is idempotent by its id: the runnerq_commands ledger replays its result.
  • The same id with a different fingerprint is a conflict.
  • Problems with individual targets are reported per item and don't fail the command.
  • Dry run is supported.
  • The ledger is pruned the way Go prunes it (rows older than 7 days).
• Schema: runnerq_commands, column for column Go's, including idx_runnerq_commands_created.
  • A fresh database gets it.
  • On an existing one, initialize creates the table with IF NOT EXISTS, under the advisory lock shared with Go.
  • verifySchema accepts a database without the table. Commands with an id then fail and ask you to run initialize.
• Worker: a cancelled activity that is running stops.
  • At its next heartbeat, when it finds its claim gone. There is now a test for this.
  • At once, if the cancel came through this worker's own agent. This uses an internal method keyed by a symbol the package doesn't export.
  • Either way it counts as a lost claim, not a failure or retry.
  • No hot-path cost: running attempts are now a Map keyed by activity id instead of a Set.
• Agent:
  • A new option, allowControl, default false, matching Go's AllowControl. Metadata-only mode doesn't affect commands, as in Go.
  • Capabilities are the same as Go's: {v: 1, targets}, with idempotency_key for signal only.
  • Also as in Go: the fingerprint, the queue-mismatch field error, ids from another store reported as not_found, and the per-item error codes with a status detail.
• Retention: cancelled trees are swept under the failed-retention setting.

Differences from Go

• Ids: only standard dashed UUIDs are accepted, the same choice the existing TS query handlers make.
• Fingerprints: match Go byte for byte on test vectors, except for a number too large for a double (e.g. 1e400).
• Timestamps: result and event created_at use the database clock, as TS's existing helpers do.

Behaviour notes

• ActivityStatus gains "cancelled". It's an addition, but exhaustive switch statements in user code may need a new case.
• allowReuseOnFailure now also reuses a cancelled activity's idempotency key, as Go does.
• A stale attempt still running on the worker that reclaims the same activity is now aborted at once.

Tests

• New test/commands.test.mjs: Go's command conformance cases ported.
• New test/conductor-commands.test.mjs: capabilities, round trips and the immediate interrupt.
• Worker test for a cancel found at heartbeat.
• npm run build, typecheck and format:check pass. npm test passes against Postgres (104 tests).