Explore integration between KernelCI and local developer testing workflows

Context

Feedback from kernel developers highlighted the value of having CI infrastructure and local development/testing workflows share tooling and concepts.

One example is a workflow where a developer can quickly:

1. Build the kernel from the current working tree.
2. Boot it into a test environment locally or in the cloud.
3. Run a test suite or an individual reproducer.
4. Open an interactive shell for debugging.
5. Iterate through the edit/build/test cycle.

This is different from KernelCI's primary integration-testing workflow based on git trees, but reducing the distance between CI and developer-side testing could make KernelCI infrastructure more useful during development.

Goal

Explore whether parts of KernelCI's existing infrastructure could support or integrate with local developer testing workflows without distracting from its primary CI use cases.

Points to discuss
• Which parts of the KernelCI stack could realistically be reused locally.
• Running tests against a developer's current working tree.
• Local versus remote/cloud execution.
• Interactive/debugging workflows.
• Reproducing KernelCI failures locally.
• Whether existing tools already cover parts of this workflow.
• Whether this belongs within KernelCI's scope or should primarily be addressed through integrations with external tooling.

This issue is intended for exploration and scope definition rather than committing to a particular implementation.

No files, tests, or entry points are named. Start by mapping KernelCI's existing CI infrastructure and developer-facing workflows, then compare local, cloud, current-tree, interactive, and failure-reproduction use cases. Done means producing a clear scope and integration recommendation without committing to an implementation.