Class BaseAdapterInstanceAbstract

The stopped → starting → running/error (and back to stopped) machine every AdapterInstance re-derives, written once: start() flips to starting, runs bringUp, and lands on running — or catches, flips to error, and rethrows so the manager's startEntry sees the failure; stop() runs tearDown and lands on stopped only once it resolves (a throwing tearDown — a real device that refuses to let go — propagates instead of a status update, exactly as before this base existed: bringUp/tearDown own their OWN internal try/catch when a caller needs stop() to never throw, same as the concrete instances always did).

Four adapters had drifted onto their own copies of this exact machine (a full X-Touch and its Mini sibling, the managed control-surface bridge, the REAC adapter) — one of them (the REAC instance) had quietly lost the error status on a failed stop(). Subclasses that need MORE than the generic status (the control-surface bridge layers a peer-socket fault and a delegated child adapter status on top) are free to override the status getter; start()/stop() still drive this class's own status field beneath it.