Skip to content

refactor: remove final direct Tokio selection and test-runtime dependency #243

Description

@zackees

Refs #229; coordinated with migration PR #242 and kernel interrupt PR zackees/kernal-api#188.

Remaining direct Tokio uses are five select loops plus async test attributes. All runtime, timer, channel, process and signal mechanisms are already kernel-owned. Remove the direct manifest edge without introducing a generic select macro or companion crate: keep typed FastLED watch/test event ordering as product policy, poll kernel-owned futures via std::future::poll_fn, and run async policy tests using kernel RuntimeBuilder.

Preserve biased timeout/readiness/interrupt/liveness/viewer/command priority in production tests and prevent command output from starving child-exit checks. Preserve watch cleanup and command-specific outcomes. Generic primitive tests stay upstream; add focused application ordering/guard policy tests here.

Acceptance: RED strict direct-Tokio manifest/source boundary then GREEN; full Rust/Python tests, strict Clippy, formatting and pre-push review; no compiler flags/backend changes; Tokio may remain a private transitive kernel/backend dependency. Exact published kernel adoption and remaining dependency inventory remain required for #229.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions