LivoxProto1: port to sscl::co framework

Code now actually looks a lot cleaner, tbh.

AGENTS.md

@@ -11,6 +11,7 @@
 - Aggressively isolate, split off, deduplicate and reuse code which can be made into common library code. Do the same with UI elements. Do this both when implementing new features and opportunistically while refactoring or changing old code/UI elements.
 - Names of files, functions, classes, abstractions, database fields, etc should be aimed at disambiguating purpose and function, rather than at brevity.
 - Any source or header file that includes a Boost header must include `<boostAsioLinkageFix.h>` first (at the top of the file, or immediately after the include guard in headers), before all other includes, so Boost.Asio is used as a non-header-only library correctly.
+- When refactoring code, moving code around or splitting code into new files, don't omit or remove source code comments. Preserve source code comments across refactors.
 
 ## Style:
 
@@ -18,7 +19,8 @@
 * UpperCamelCase for class/struct names, lowerCamelCase for var and member var
   names; underscores_between_words for namespace names. No hungarian notation.
 * Differentiate overshadowing local arg var names from class member var names
-  by prefixing local arg var names with underscore (_).
+  by prefixing local arg var names with underscore (_). Don't do things like
+  postfixing the local arg var name with "In", etc.
 * Single-line blocks after a selection/iteration statement must always be
   enclosed in braces, but you can choose whether opening brace is on same line,
   versus whether you put both braces on same line. I.e: