manifest: retire the scheduled-task vocabulary
Closes #14. scheduled_tasks and its supporting types are gone from ModuleManifest, in Rust and TypeScript.
Both halves in one commit, per the reasoning on the issue: a manifest field required by one client and absent from the protocol is the same drift that made scheduler.* readable as a roadmap.
Removed
Rust — crates/subc-protocol/src/manifest.rs: the field, plus ScheduledTask, TaskEligibility, LeaseScope, ModelPolicy, CircuitBreaker, and the fixture that was their only constructor. Ten call sites dropped scheduled_tasks: Vec::new().
TypeScript — clients/subc-client/src/provider.ts: the required scheduled_tasks field, ScheduledTaskInput / TaskEligibilityInput / ModelPolicyInput / CircuitBreakerInput, the LeaseScope type, both construction sites, and normalizeScheduledTask. Five re-exports removed from index.ts.
Swift confirmed unaffected — zero hits under clients/subc-client-swift.
control.rs's manifest() helper is a generic fixture shared by hello-frame parsing, route-liveness, and push-op tests — none of them about scheduled tasks. Its ScheduledTask literal was incidental filler, so the field was dropped and every test kept.
The fixture, called out rather than buried
crates/subc-protocol/tests/golden/module_hello_body.json loses one line. That's the serialized HELLO body carrying the whole manifest, so the field's removal necessarily moves it — a real wire-shape change, not a test artifact.
git diff --stat origin/master -- crates/subc-control/tests/golden/
(empty)
git diff --stat origin/master -- crates/subc-protocol/tests/golden/
module_hello_body.json | 1 -
subc-control is untouched, per your review criterion.
Compatibility both directions: no deny_unknown_fields anywhere in subc-protocol, so a new daemon parses an old module's HELLO that still sends scheduled_tasks, and vice versa. Only the canonical fixture moves.
Migration cost — I under-priced this on the issue and want it stated correctly
I originally said "one line per Rust module author." That was measured on the Rust side and stated as though it covered the fleet. Corrected:
- Rust module authors: drop one line at their next build.
- TypeScript module authors: drop one line, and
@cortexkit/subc-clientneeds a release — removing a required interface field is breaking for anyone typechecking against it.
Verification
cargo test --workspace 31 test binaries, 0 failures
cargo clippy --all-targets clean
cargo fmt --check clean
bun test (subc-client) 137 tests, 0 fail, 18 skip
bunx tsc --noEmit fails, and it is pre-existing — error TS2688: Cannot find type definition file for 'node'. node_modules isn't installed in this checkout, so tsc can't resolve anything. I verified this rather than asserting it: the identical error reproduces on a clean worktree of unmodified 06a2e76. bun test resolves types through Bun's own toolchain and passes, which is why the TS suite is meaningful and the tsc run isn't.
Flagging it because a typecheck that structurally cannot run is a gate whose silence means nothing — if CI installs deps, it will typecheck properly there, and that's the run I'd trust over mine.
One process note
My subagent reported a dangling ModelPolicyInput re-export as pre-existing upstream drift. It wasn't — I checked origin/master and the type was defined at provider.ts:153, so the removal was its own, correctly done, and misattributed afterward. Had I forwarded that as filed, this PR would have opened with a phantom bug report against your tree.
I mention it because the same habit is why the fixture claim above is stated as a diff rather than a summary.
Need help on this PR? Tag @codesmith with what you need. Autofix is disabled.
Summary by cubic
Retires scheduled-task fields from the manifest across Rust and TypeScript so the daemon no longer exposes unused scheduler vocabulary. Previously, ModuleManifest required scheduled_tasks; now it omits it. The HELLO payload no longer includes scheduled_tasks. Parsing remains backward/forward compatible because the protocol does not deny_unknown_fields.
- Removes
scheduled_tasksand supporting types fromsubc-protocol; updates call sites insubc-client-rs,subc-core, andsubc-mcp. - Removes the required field and related types/normalizers from the TypeScript client
@cortexkit/subc-client; Swift client is unaffected. - Updates the golden
module_hello_body.json;subc-controlgoldens are unchanged. - Drops the incidental scheduled-task literal from
control.rs’smanifest()test helper; tests remain valid.
Migration
- Rust module authors: remove
scheduled_tasksfrom manifests. - TypeScript module authors: upgrade to the next
@cortexkit/subc-clientand removescheduled_tasksfrom manifests; this is a breaking type change. - No daemon or config changes required; old/new peers can interoperate on the wire.
Deploy ordering (release note)
The daemon must be deployed before any module rebuilt against the new manifest. The old scheduled_tasks field carries no #[serde(default)], so an old daemon refuses a new module's HELLO with missing field scheduled_tasks; a new daemon accepts old modules unchanged. Producer-narrowing, and ck daemon's build_git_sha makes the ordering checkable rather than ritual.