RAGE #41: typed Auto-Dig control-plane runtime boundary #42

Closed

lost-rob0t wants to merge 4 commits from rage/41-autodig-control-boundary into main

lost-rob0t commented

2026-08-25 05:16:31 +00:00

(Migrated from github.com)

Closes part of #41; consumer is lost-rob0t/starintel-bixby#7.

TDD state

This PR starts intentionally RED with tests only. The tests specify the smallest server-side ownership boundary needed before wiring any real Auto-Dig runtime:

no Auto-Dig lifecycle commands are advertised when no owning runtime adapter is configured;
a configured runtime selectively installs typed autodig.* capabilities through the existing quasar.control.v1 command registry;
autodig.run.start delegates the caller workspace and payload to the owning runtime and returns the durable run ID allocated by that runtime;
typed lifecycle errors remain client-safe Quasar errors.

Architecture boundary

This does not add run state, a scheduler, browser automation, DB access, or a Bixby-specific protocol to Quasar. The production slice will provide an injectable server-side runtime adapter; actual durable lifecycle semantics remain owned by the real Auto-Dig runtime implementation.

Exact-head CI must go RED on this tests-only candidate before production implementation is added.

Closes part of #41; consumer is `lost-rob0t/starintel-bixby#7`. ## TDD state This PR starts intentionally RED with tests only. The tests specify the smallest server-side ownership boundary needed before wiring any real Auto-Dig runtime: - no Auto-Dig lifecycle commands are advertised when no owning runtime adapter is configured; - a configured runtime selectively installs typed `autodig.*` capabilities through the existing `quasar.control.v1` command registry; - `autodig.run.start` delegates the caller workspace and payload to the owning runtime and returns the durable run ID allocated by that runtime; - typed lifecycle errors remain client-safe Quasar errors. ## Architecture boundary This does **not** add run state, a scheduler, browser automation, DB access, or a Bixby-specific protocol to Quasar. The production slice will provide an injectable server-side runtime adapter; actual durable lifecycle semantics remain owned by the real Auto-Dig runtime implementation. Exact-head CI must go RED on this tests-only candidate before production implementation is added.

nsaspy changed title from ~~WIP: RAGE #41: typed Auto-Dig control-plane runtime boundary~~ to RAGE #41: typed Auto-Dig control-plane runtime boundary

2026-08-27 19:50:33 +00:00