quality-loop 0.3.0

quality-loop 0.3.0

Screens can go up where the product runs. An adapter whose product runs somewhere other than this machine (in a VM, for example) can now answer Adapter.screen_backend() with a module that opens and closes the operator's pages and terminals there, so the room's app sees them on its own desktop. The runner records the backend in the screens manifest, and screen_open / screen_close and the end-of-run cleanup all go through it. The default (None) keeps this machine's backend. docs/adapters.md describes the module's three functions.

The scenario's platform comes from the adapter. Adapter.platform() names the OS the product runs on (default sys.platform). Phase-one operator instructions use it, so a Mac host driving a Windows guest gets Windows instructions.

No adapter has to change: both methods are new, and their defaults keep 0.2.2's behaviour.