OpenVibe Node: the repository and its build brief (plan T15/T16, ADR-043; ADR-045 to follow): Go core, Python robot plugins (Adeept ADR036, Cozmo via PyCozmo, dry run), WHIP video, safety, installer and CI.

ddiff --git a/LICENSE b/LICENSE
nnew file mode 100644
iindex 0000000..0ad25db
---- /dev/null
++++ b/LICENSE
@@@ -0,0 +1,661 @@
++                    GNU AFFERO GENERAL PUBLIC LICENSE
++                       Version 3, 19 November 2007
++
++ Copyright (C) 2007 Free Software Foundation, Inc. <https://fsf.org/>
++ Everyone is permitted to copy and distribute verbatim copies
++ of this license document, but changing it is not allowed.
++
++                            Preamble
++
++  The GNU Affero General Public License is a free, copyleft license for
++software and other kinds of works, specifically designed to ensure
++cooperation with the community in the case of network server software.
++
++  The licenses for most software and other practical works are designed
++to take away your freedom to share and change the works.  By contrast,
++our General Public Licenses are intended to guarantee your freedom to
++share and change all versions of a program--to make sure it remains free
++software for all its users.
++
++  When we speak of free software, we are referring to freedom, not
++price.  Our General Public Licenses are designed to make sure that you
++have the freedom to distribute copies of free software (and charge for
++them if you wish), that you receive source code or can get it if you
++want it, that you can change the software or use pieces of it in new
++free programs, and that you know you can do these things.
++
++  Developers that use our General Public Licenses protect your rights
++with two steps: (1) assert copyright on the software, and (2) offer
++you this License which gives you legal permission to copy, distribute
++and/or modify the software.
++
++  A secondary benefit of defending all users' freedom is that
++improvements made in alternate versions of the program, if they
++receive widespread use, become available for other developers to
++incorporate.  Many developers of free software are heartened and
++encouraged by the resulting cooperation.  However, in the case of
++software used on network servers, this result may fail to come about.
++The GNU General Public License permits making a modified version and
++letting the public access it on a server without ever releasing its
++source code to the public.
++
++  The GNU Affero General Public License is designed specifically to
++ensure that, in such cases, the modified source code becomes available
++to the community.  It requires the operator of a network server to
++provide the source code of the modified version running there to the
++users of that server.  Therefore, public use of a modified version, on
++a publicly accessible server, gives the public access to the source
++code of the modified version.
++
++  An older license, called the Affero General Public License and
++published by Affero, was designed to accomplish similar goals.  This is
++a different license, not a version of the Affero GPL, but Affero has
++released a new version of the Affero GPL which permits relicensing under
++this license.
++
++  The precise terms and conditions for copying, distribution and
++modification follow.
++
++                       TERMS AND CONDITIONS
++
++  0. Definitions.
++
++  "This License" refers to version 3 of the GNU Affero General Public License.
++
++  "Copyright" also means copyright-like laws that apply to other kinds of
++works, such as semiconductor masks.
++
++  "The Program" refers to any copyrightable work licensed under this
++License.  Each licensee is addressed as "you".  "Licensees" and
++"recipients" may be individuals or organizations.
++
++  To "modify" a work means to copy from or adapt all or part of the work
++in a fashion requiring copyright permission, other than the making of an
++exact copy.  The resulting work is called a "modified version" of the
++earlier work or a work "based on" the earlier work.
++
++  A "covered work" means either the unmodified Program or a work based
++on the Program.
++
++  To "propagate" a work means to do anything with it that, without
++permission, would make you directly or secondarily liable for
++infringement under applicable copyright law, except executing it on a
++computer or modifying a private copy.  Propagation includes copying,
++distribution (with or without modification), making available to the
++public, and in some countries other activities as well.
++
++  To "convey" a work means any kind of propagation that enables other
++parties to make or receive copies.  Mere interaction with a user through
++a computer network, with no transfer of a copy, is not conveying.
++
++  An interactive user interface displays "Appropriate Legal Notices"
++to the extent that it includes a convenient and prominently visible
++feature that (1) displays an appropriate copyright notice, and (2)
++tells the user that there is no warranty for the work (except to the
++extent that warranties are provided), that licensees may convey the
++work under this License, and how to view a copy of this License.  If
++the interface presents a list of user commands or options, such as a
++menu, a prominent item in the list meets this criterion.
++
++  1. Source Code.
++
++  The "source code" for a work means the preferred form of the work
++for making modifications to it.  "Object code" means any non-source
++form of a work.
++
++  A "Standard Interface" means an interface that either is an official
++standard defined by a recognized standards body, or, in the case of
++interfaces specified for a particular programming language, one that
++is widely used among developers working in that language.
++
++  The "System Libraries" of an executable work include anything, other
++than the work as a whole, that (a) is included in the normal form of
++packaging a Major Component, but which is not part of that Major
++Component, and (b) serves only to enable use of the work with that
++Major Component, or to implement a Standard Interface for which an
++implementation is available to the public in source code form.  A
++"Major Component", in this context, means a major essential component
++(kernel, window system, and so on) of the specific operating system
++(if any) on which the executable work runs, or a compiler used to
++produce the work, or an object code interpreter used to run it.
++
++  The "Corresponding Source" for a work in object code form means all
++the source code needed to generate, install, and (for an executable
++work) run the object code and to modify the work, including scripts to
++control those activities.  However, it does not include the work's
++System Libraries, or general-purpose tools or generally available free
++programs which are used unmodified in performing those activities but
++which are not part of the work.  For example, Corresponding Source
++includes interface definition files associated with source files for
++the work, and the source code for shared libraries and dynamically
++linked subprograms that the work is specifically designed to require,
++such as by intimate data communication or control flow between those
++subprograms and other parts of the work.
++
++  The Corresponding Source need not include anything that users
++can regenerate automatically from other parts of the Corresponding
++Source.
++
++  The Corresponding Source for a work in source code form is that
++same work.
++
++  2. Basic Permissions.
++
++  All rights granted under this License are granted for the term of
++copyright on the Program, and are irrevocable provided the stated
++conditions are met.  This License explicitly affirms your unlimited
++permission to run the unmodified Program.  The output from running a
++covered work is covered by this License only if the output, given its
++content, constitutes a covered work.  This License acknowledges your
++rights of fair use or other equivalent, as provided by copyright law.
++
++  You may make, run and propagate covered works that you do not
++convey, without conditions so long as your license otherwise remains
++in force.  You may convey covered works to others for the sole purpose
++of having them make modifications exclusively for you, or provide you
++with facilities for running those works, provided that you comply with
++the terms of this License in conveying all material for which you do
++not control copyright.  Those thus making or running the covered works
++for you must do so exclusively on your behalf, under your direction
++and control, on terms that prohibit them from making any copies of
++your copyrighted material outside their relationship with you.
++
++  Conveying under any other circumstances is permitted solely under
++the conditions stated below.  Sublicensing is not allowed; section 10
++makes it unnecessary.
++
++  3. Protecting Users' Legal Rights From Anti-Circumvention Law.
++
++  No covered work shall be deemed part of an effective technological
++measure under any applicable law fulfilling obligations under article
++11 of the WIPO copyright treaty adopted on 20 December 1996, or
++similar laws prohibiting or restricting circumvention of such
++measures.
++
++  When you convey a covered work, you waive any legal power to forbid
++circumvention of technological measures to the extent such circumvention
++is effected by exercising rights under this License with respect to
++the covered work, and you disclaim any intention to limit operation or
++modification of the work as a means of enforcing, against the work's
++users, your or third parties' legal rights to forbid circumvention of
++technological measures.
++
++  4. Conveying Verbatim Copies.
++
++  You may convey verbatim copies of the Program's source code as you
++receive it, in any medium, provided that you conspicuously and
++appropriately publish on each copy an appropriate copyright notice;
++keep intact all notices stating that this License and any
++non-permissive terms added in accord with section 7 apply to the code;
++keep intact all notices of the absence of any warranty; and give all
++recipients a copy of this License along with the Program.
++
++  You may charge any price or no price for each copy that you convey,
++and you may offer support or warranty protection for a fee.
++
++  5. Conveying Modified Source Versions.
++
++  You may convey a work based on the Program, or the modifications to
++produce it from the Program, in the form of source code under the
++terms of section 4, provided that you also meet all of these conditions:
++
++    a) The work must carry prominent notices stating that you modified
++    it, and giving a relevant date.
++
++    b) The work must carry prominent notices stating that it is
++    released under this License and any conditions added under section
++    7.  This requirement modifies the requirement in section 4 to
++    "keep intact all notices".
++
++    c) You must license the entire work, as a whole, under this
++    License to anyone who comes into possession of a copy.  This
++    License will therefore apply, along with any applicable section 7
++    additional terms, to the whole of the work, and all its parts,
++    regardless of how they are packaged.  This License gives no
++    permission to license the work in any other way, but it does not
++    invalidate such permission if you have separately received it.
++
++    d) If the work has interactive user interfaces, each must display
++    Appropriate Legal Notices; however, if the Program has interactive
++    interfaces that do not display Appropriate Legal Notices, your
++    work need not make them do so.
++
++  A compilation of a covered work with other separate and independent
++works, which are not by their nature extensions of the covered work,
++and which are not combined with it such as to form a larger program,
++in or on a volume of a storage or distribution medium, is called an
++"aggregate" if the compilation and its resulting copyright are not
++used to limit the access or legal rights of the compilation's users
++beyond what the individual works permit.  Inclusion of a covered work
++in an aggregate does not cause this License to apply to the other
++parts of the aggregate.
++
++  6. Conveying Non-Source Forms.
++
++  You may convey a covered work in object code form under the terms
++of sections 4 and 5, provided that you also convey the
++machine-readable Corresponding Source under the terms of this License,
++in one of these ways:
++
++    a) Convey the object code in, or embodied in, a physical product
++    (including a physical distribution medium), accompanied by the
++    Corresponding Source fixed on a durable physical medium
++    customarily used for software interchange.
++
++    b) Convey the object code in, or embodied in, a physical product
++    (including a physical distribution medium), accompanied by a
++    written offer, valid for at least three years and valid for as
++    long as you offer spare parts or customer support for that product
++    model, to give anyone who possesses the object code either (1) a
++    copy of the Corresponding Source for all the software in the
++    product that is covered by this License, on a durable physical
++    medium customarily used for software interchange, for a price no
++    more than your reasonable cost of physically performing this
++    conveying of source, or (2) access to copy the
++    Corresponding Source from a network server at no charge.
++
++    c) Convey individual copies of the object code with a copy of the
++    written offer to provide the Corresponding Source.  This
++    alternative is allowed only occasionally and noncommercially, and
++    only if you received the object code with such an offer, in accord
++    with subsection 6b.
++
++    d) Convey the object code by offering access from a designated
++    place (gratis or for a charge), and offer equivalent access to the
++    Corresponding Source in the same way through the same place at no
++    further charge.  You need not require recipients to copy the
++    Corresponding Source along with the object code.  If the place to
++    copy the object code is a network server, the Corresponding Source
++    may be on a different server (operated by you or a third party)
++    that supports equivalent copying facilities, provided you maintain
++    clear directions next to the object code saying where to find the
++    Corresponding Source.  Regardless of what server hosts the
++    Corresponding Source, you remain obligated to ensure that it is
++    available for as long as needed to satisfy these requirements.
++
++    e) Convey the object code using peer-to-peer transmission, provided
++    you inform other peers where the object code and Corresponding
++    Source of the work are being offered to the general public at no
++    charge under subsection 6d.
++
++  A separable portion of the object code, whose source code is excluded
++from the Corresponding Source as a System Library, need not be
++included in conveying the object code work.
++
++  A "User Product" is either (1) a "consumer product", which means any
++tangible personal property which is normally used for personal, family,
++or household purposes, or (2) anything designed or sold for incorporation
++into a dwelling.  In determining whether a product is a consumer product,
++doubtful cases shall be resolved in favor of coverage.  For a particular
++product received by a particular user, "normally used" refers to a
++typical or common use of that class of product, regardless of the status
++of the particular user or of the way in which the particular user
++actually uses, or expects or is expected to use, the product.  A product
++is a consumer product regardless of whether the product has substantial
++commercial, industrial or non-consumer uses, unless such uses represent
++the only significant mode of use of the product.
++
++  "Installation Information" for a User Product means any methods,
++procedures, authorization keys, or other information required to install
++and execute modified versions of a covered work in that User Product from
++a modified version of its Corresponding Source.  The information must
++suffice to ensure that the continued functioning of the modified object
++code is in no case prevented or interfered with solely because
++modification has been made.
++
++  If you convey an object code work under this section in, or with, or
++specifically for use in, a User Product, and the conveying occurs as
++part of a transaction in which the right of possession and use of the
++User Product is transferred to the recipient in perpetuity or for a
++fixed term (regardless of how the transaction is characterized), the
++Corresponding Source conveyed under this section must be accompanied
++by the Installation Information.  But this requirement does not apply
++if neither you nor any third party retains the ability to install
++modified object code on the User Product (for example, the work has
++been installed in ROM).
++
++  The requirement to provide Installation Information does not include a
++requirement to continue to provide support service, warranty, or updates
++for a work that has been modified or installed by the recipient, or for
++the User Product in which it has been modified or installed.  Access to a
++network may be denied when the modification itself materially and
++adversely affects the operation of the network or violates the rules and
++protocols for communication across the network.
++
++  Corresponding Source conveyed, and Installation Information provided,
++in accord with this section must be in a format that is publicly
++documented (and with an implementation available to the public in
++source code form), and must require no special password or key for
++unpacking, reading or copying.
++
++  7. Additional Terms.
++
++  "Additional permissions" are terms that supplement the terms of this
++License by making exceptions from one or more of its conditions.
++Additional permissions that are applicable to the entire Program shall
++be treated as though they were included in this License, to the extent
++that they are valid under applicable law.  If additional permissions
++apply only to part of the Program, that part may be used separately
++under those permissions, but the entire Program remains governed by
++this License without regard to the additional permissions.
++
++  When you convey a copy of a covered work, you may at your option
++remove any additional permissions from that copy, or from any part of
++it.  (Additional permissions may be written to require their own
++removal in certain cases when you modify the work.)  You may place
++additional permissions on material, added by you to a covered work,
++for which you have or can give appropriate copyright permission.
++
++  Notwithstanding any other provision of this License, for material you
++add to a covered work, you may (if authorized by the copyright holders of
++that material) supplement the terms of this License with terms:
++
++    a) Disclaiming warranty or limiting liability differently from the
++    terms of sections 15 and 16 of this License; or
++
++    b) Requiring preservation of specified reasonable legal notices or
++    author attributions in that material or in the Appropriate Legal
++    Notices displayed by works containing it; or
++
++    c) Prohibiting misrepresentation of the origin of that material, or
++    requiring that modified versions of such material be marked in
++    reasonable ways as different from the original version; or
++
++    d) Limiting the use for publicity purposes of names of licensors or
++    authors of the material; or
++
++    e) Declining to grant rights under trademark law for use of some
++    trade names, trademarks, or service marks; or
++
++    f) Requiring indemnification of licensors and authors of that
++    material by anyone who conveys the material (or modified versions of
++    it) with contractual assumptions of liability to the recipient, for
++    any liability that these contractual assumptions directly impose on
++    those licensors and authors.
++
++  All other non-permissive additional terms are considered "further
++restrictions" within the meaning of section 10.  If the Program as you
++received it, or any part of it, contains a notice stating that it is
++governed by this License along with a term that is a further
++restriction, you may remove that term.  If a license document contains
++a further restriction but permits relicensing or conveying under this
++License, you may add to a covered work material governed by the terms
++of that license document, provided that the further restriction does
++not survive such relicensing or conveying.
++
++  If you add terms to a covered work in accord with this section, you
++must place, in the relevant source files, a statement of the
++additional terms that apply to those files, or a notice indicating
++where to find the applicable terms.
++
++  Additional terms, permissive or non-permissive, may be stated in the
++form of a separately written license, or stated as exceptions;
++the above requirements apply either way.
++
++  8. Termination.
++
++  You may not propagate or modify a covered work except as expressly
++provided under this License.  Any attempt otherwise to propagate or
++modify it is void, and will automatically terminate your rights under
++this License (including any patent licenses granted under the third
++paragraph of section 11).
++
++  However, if you cease all violation of this License, then your
++license from a particular copyright holder is reinstated (a)
++provisionally, unless and until the copyright holder explicitly and
++finally terminates your license, and (b) permanently, if the copyright
++holder fails to notify you of the violation by some reasonable means
++prior to 60 days after the cessation.
++
++  Moreover, your license from a particular copyright holder is
++reinstated permanently if the copyright holder notifies you of the
++violation by some reasonable means, this is the first time you have
++received notice of violation of this License (for any work) from that
++copyright holder, and you cure the violation prior to 30 days after
++your receipt of the notice.
++
++  Termination of your rights under this section does not terminate the
++licenses of parties who have received copies or rights from you under
++this License.  If your rights have been terminated and not permanently
++reinstated, you do not qualify to receive new licenses for the same
++material under section 10.
++
++  9. Acceptance Not Required for Having Copies.
++
++  You are not required to accept this License in order to receive or
++run a copy of the Program.  Ancillary propagation of a covered work
++occurring solely as a consequence of using peer-to-peer transmission
++to receive a copy likewise does not require acceptance.  However,
++nothing other than this License grants you permission to propagate or
++modify any covered work.  These actions infringe copyright if you do
++not accept this License.  Therefore, by modifying or propagating a
++covered work, you indicate your acceptance of this License to do so.
++
++  10. Automatic Licensing of Downstream Recipients.
++
++  Each time you convey a covered work, the recipient automatically
++receives a license from the original licensors, to run, modify and
++propagate that work, subject to this License.  You are not responsible
++for enforcing compliance by third parties with this License.
++
++  An "entity transaction" is a transaction transferring control of an
++organization, or substantially all assets of one, or subdividing an
++organization, or merging organizations.  If propagation of a covered
++work results from an entity transaction, each party to that
++transaction who receives a copy of the work also receives whatever
++licenses to the work the party's predecessor in interest had or could
++give under the previous paragraph, plus a right to possession of the
++Corresponding Source of the work from the predecessor in interest, if
++the predecessor has it or can get it with reasonable efforts.
++
++  You may not impose any further restrictions on the exercise of the
++rights granted or affirmed under this License.  For example, you may
++not impose a license fee, royalty, or other charge for exercise of
++rights granted under this License, and you may not initiate litigation
++(including a cross-claim or counterclaim in a lawsuit) alleging that
++any patent claim is infringed by making, using, selling, offering for
++sale, or importing the Program or any portion of it.
++
++  11. Patents.
++
++  A "contributor" is a copyright holder who authorizes use under this
++License of the Program or a work on which the Program is based.  The
++work thus licensed is called the contributor's "contributor version".
++
++  A contributor's "essential patent claims" are all patent claims
++owned or controlled by the contributor, whether already acquired or
++hereafter acquired, that would be infringed by some manner, permitted
++by this License, of making, using, or selling its contributor version,
++but do not include claims that would be infringed only as a
++consequence of further modification of the contributor version.  For
++purposes of this definition, "control" includes the right to grant
++patent sublicenses in a manner consistent with the requirements of
++this License.
++
++  Each contributor grants you a non-exclusive, worldwide, royalty-free
++patent license under the contributor's essential patent claims, to
++make, use, sell, offer for sale, import and otherwise run, modify and
++propagate the contents of its contributor version.
++
++  In the following three paragraphs, a "patent license" is any express
++agreement or commitment, however denominated, not to enforce a patent
++(such as an express permission to practice a patent or covenant not to
++sue for patent infringement).  To "grant" such a patent license to a
++party means to make such an agreement or commitment not to enforce a
++patent against the party.
++
++  If you convey a covered work, knowingly relying on a patent license,
++and the Corresponding Source of the work is not available for anyone
++to copy, free of charge and under the terms of this License, through a
++publicly available network server or other readily accessible means,
++then you must either (1) cause the Corresponding Source to be so
++available, or (2) arrange to deprive yourself of the benefit of the
++patent license for this particular work, or (3) arrange, in a manner
++consistent with the requirements of this License, to extend the patent
++license to downstream recipients.  "Knowingly relying" means you have
++actual knowledge that, but for the patent license, your conveying the
++covered work in a country, or your recipient's use of the covered work
++in a country, would infringe one or more identifiable patents in that
++country that you have reason to believe are valid.
++
++  If, pursuant to or in connection with a single transaction or
++arrangement, you convey, or propagate by procuring conveyance of, a
++covered work, and grant a patent license to some of the parties
++receiving the covered work authorizing them to use, propagate, modify
++or convey a specific copy of the covered work, then the patent license
++you grant is automatically extended to all recipients of the covered
++work and works based on it.
++
++  A patent license is "discriminatory" if it does not include within
++the scope of its coverage, prohibits the exercise of, or is
++conditioned on the non-exercise of one or more of the rights that are
++specifically granted under this License.  You may not convey a covered
++work if you are a party to an arrangement with a third party that is
++in the business of distributing software, under which you make payment
++to the third party based on the extent of your activity of conveying
++the work, and under which the third party grants, to any of the
++parties who would receive the covered work from you, a discriminatory
++patent license (a) in connection with copies of the covered work
++conveyed by you (or copies made from those copies), or (b) primarily
++for and in connection with specific products or compilations that
++contain the covered work, unless you entered into that arrangement,
++or that patent license was granted, prior to 28 March 2007.
++
++  Nothing in this License shall be construed as excluding or limiting
++any implied license or other defenses to infringement that may
++otherwise be available to you under applicable patent law.
++
++  12. No Surrender of Others' Freedom.
++
++  If conditions are imposed on you (whether by court order, agreement or
++otherwise) that contradict the conditions of this License, they do not
++excuse you from the conditions of this License.  If you cannot convey a
++covered work so as to satisfy simultaneously your obligations under this
++License and any other pertinent obligations, then as a consequence you may
++not convey it at all.  For example, if you agree to terms that obligate you
++to collect a royalty for further conveying from those to whom you convey
++the Program, the only way you could satisfy both those terms and this
++License would be to refrain entirely from conveying the Program.
++
++  13. Remote Network Interaction; Use with the GNU General Public License.
++
++  Notwithstanding any other provision of this License, if you modify the
++Program, your modified version must prominently offer all users
++interacting with it remotely through a computer network (if your version
++supports such interaction) an opportunity to receive the Corresponding
++Source of your version by providing access to the Corresponding Source
++from a network server at no charge, through some standard or customary
++means of facilitating copying of software.  This Corresponding Source
++shall include the Corresponding Source for any work covered by version 3
++of the GNU General Public License that is incorporated pursuant to the
++following paragraph.
++
++  Notwithstanding any other provision of this License, you have
++permission to link or combine any covered work with a work licensed
++under version 3 of the GNU General Public License into a single
++combined work, and to convey the resulting work.  The terms of this
++License will continue to apply to the part which is the covered work,
++but the work with which it is combined will remain governed by version
++3 of the GNU General Public License.
++
++  14. Revised Versions of this License.
++
++  The Free Software Foundation may publish revised and/or new versions of
++the GNU Affero General Public License from time to time.  Such new versions
++will be similar in spirit to the present version, but may differ in detail to
++address new problems or concerns.
++
++  Each version is given a distinguishing version number.  If the
++Program specifies that a certain numbered version of the GNU Affero General
++Public License "or any later version" applies to it, you have the
++option of following the terms and conditions either of that numbered
++version or of any later version published by the Free Software
++Foundation.  If the Program does not specify a version number of the
++GNU Affero General Public License, you may choose any version ever published
++by the Free Software Foundation.
++
++  If the Program specifies that a proxy can decide which future
++versions of the GNU Affero General Public License can be used, that proxy's
++public statement of acceptance of a version permanently authorizes you
++to choose that version for the Program.
++
++  Later license versions may give you additional or different
++permissions.  However, no additional obligations are imposed on any
++author or copyright holder as a result of your choosing to follow a
++later version.
++
++  15. Disclaimer of Warranty.
++
++  THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
++APPLICABLE LAW.  EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
++HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY
++OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
++THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
++PURPOSE.  THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
++IS WITH YOU.  SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
++ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
++
++  16. Limitation of Liability.
++
++  IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
++WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
++THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
++GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
++USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
++DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
++PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
++EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
++SUCH DAMAGES.
++
++  17. Interpretation of Sections 15 and 16.
++
++  If the disclaimer of warranty and limitation of liability provided
++above cannot be given local legal effect according to their terms,
++reviewing courts shall apply local law that most closely approximates
++an absolute waiver of all civil liability in connection with the
++Program, unless a warranty or assumption of liability accompanies a
++copy of the Program in return for a fee.
++
++                     END OF TERMS AND CONDITIONS
++
++            How to Apply These Terms to Your New Programs
++
++  If you develop a new program, and you want it to be of the greatest
++possible use to the public, the best way to achieve this is to make it
++free software which everyone can redistribute and change under these terms.
++
++  To do so, attach the following notices to the program.  It is safest
++to attach them to the start of each source file to most effectively
++state the exclusion of warranty; and each file should have at least
++the "copyright" line and a pointer to where the full notice is found.
++
++    <one line to give the program's name and a brief idea of what it does.>
++    Copyright (C) <year>  <name of author>
++
++    This program is free software: you can redistribute it and/or modify
++    it under the terms of the GNU Affero General Public License as published
++    by the Free Software Foundation, either version 3 of the License, or
++    (at your option) any later version.
++
++    This program is distributed in the hope that it will be useful,
++    but WITHOUT ANY WARRANTY; without even the implied warranty of
++    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
++    GNU Affero General Public License for more details.
++
++    You should have received a copy of the GNU Affero General Public License
++    along with this program.  If not, see <https://www.gnu.org/licenses/>.
++
++Also add information on how to contact you by electronic and paper mail.
++
++  If your software can interact with users remotely through a computer
++network, you should also make sure that it provides a way for users to
++get its source.  For example, if your program is a web application, its
++interface could display a "Source" link that leads users to an archive
++of the code.  There are many ways you could offer source, and different
++solutions will be better for different programs; see section 13 for the
++specific requirements.
++
++  You should also get your employer (if you work as a programmer) or school,
++if any, to sign a "copyright disclaimer" for the program, if necessary.
++For more information on this, and how to apply and follow the GNU AGPL, see
++<https://www.gnu.org/licenses/>.
ddiff --git a/README.md b/README.md
nnew file mode 100644
iindex 0000000..6679752
---- /dev/null
++++ b/README.md
@@@ -0,0 +1,5 @@
++# OpenVibe Node
++
++One service for your computers, servers, Raspberry Pis, phones and robots: pair it once with OpenVibe and products like OpenVibe.Bot (robots) and OpenVibe.Actor (AI agents) can use the device safely. It connects out, needs no open ports, and keeps a local kill switch.
++
++Status: being built. Start here: [docs/HANDOFF.md](docs/HANDOFF.md) and [docs/ADR-043-bot-devices-and-control.md](docs/ADR-043-bot-devices-and-control.md).
ddiff --git a/SECURITY.md b/SECURITY.md
nnew file mode 100644
iindex 0000000..49b94e7
---- /dev/null
++++ b/SECURITY.md
@@@ -0,0 +1,21 @@
++# Security policy
++
++OpenVibe is run in the open, and we want to hear about security problems before anyone else does.
++
++## Reporting a vulnerability
++
++Email **[email protected]** with "security" in the subject. Please include what you found, where (URL,
++repository, file), how to reproduce it, and what an attacker could do with it. Do not open a public GitHub issue for
++a vulnerability, and do not test against other people's accounts, data or streams.
++
++We reply within 7 days, keep you updated while we fix it, and credit you when the fix ships if you would like.
++
++## Scope
++
++Every OpenVibe service and site (openvibe.live, openvibe.network, openvibe.tools, openvibe.media, openvibe.community,
++openvibe.games and the other openvibe.* domains) and every repository under github.com/OpenVibers. Machine-readable
++contact details are at `/.well-known/security.txt` on each site.
++
++## Supported versions
++
++Only the current `main` branch, which is what runs in production, receives fixes.
ddiff --git a/docs/ADR-043-bot-devices-and-control.md b/docs/ADR-043-bot-devices-and-control.md
nnew file mode 100644
iindex 0000000..2bea063
---- /dev/null
++++ b/docs/ADR-043-bot-devices-and-control.md
@@@ -0,0 +1,115 @@
++# ADR-043: Bot — devices, pairing, control and safety
++
++**Status:** Accepted 2026-09-29 (plan track T15, "Bot complete"; owner direction the same evening: openvibe.bot is an open
++control panel for robots, streaming optional; the first robots are the owner's Adeept 4WD Smart Car for Raspberry Pi and
++a Cozmo-based robot).
++
++## Context and current evidence
++
++- Robot control lives in OpenVibe.Live today (`server/controls/`: control-server 572 lines, routes 1522, ONVIF 444). A
++  robot authenticates with its owner's **stream key**, the same string that appears in RTMP/WHIP publish URLs. One device
++  per streamer (the socket map is keyed by stream key). No heartbeat, no deadman, no acknowledgement, no audit.
++- Chat commands (`!forward`, `!headup`, `!say`…) reached the robot with no permission check; Live fb3957f put them behind
++  the panel's rules as a stop-gap. Live also generates ~900 lines of Python per Cozmo owner (`routes.js`), because
++  buttons are table rows rather than a profile.
++- OpenRe's webrtc worker (75a5dd7) takes WHIP ingest and serves viewers; Media records; Events carries events; Network
++  issues service tokens and delegated grants.
++- The owner's first robot, the Adeept ADR036, is a Raspberry Pi with Adeept's Robot HAT: a PCA9685 at I²C 0x5f drives the
++  four DC motors (channels 8–15) and the pan/tilt servos (0, 1); an ADS7830 at 0x48 reads battery voltage; ultrasonic,
++  line and light sensors, WS2812 LEDs, a buzzer, a Pi camera through Picamera2. Its stock software listens on
++  0.0.0.0:8888 with a hard-coded `admin:123456` login and serves MJPEG on :5000.
++- The second, a Cozmo, runs closed firmware, makes its own Wi-Fi access point with no internet and speaks its own UDP
++  protocol; PyCozmo (MIT) drives it directly: wheels, head, lift, camera (320×240), speaker, face display, lights, cubes,
++  cliff/pick-up sensors, battery.
++
++## Decision
++
++1. **Robots, devices and credentials are separate things.** A **robot** (`rob_…`) is what the owner sees and shares; a
++   **device** (`dev_…`) is a running agent attached to one or more robots (a Pi on a rover; a bridge computer driving a
++   Cozmo; later a phone brain). A device holds one **device credential**: 32 random bytes, stored hashed, shown once, never
++   in a URL, a log line or a browser, rotatable (the old one keeps working 60 s) and revocable (instant; the device must
++   pair again). A device's camera publishes with its own **publish key** (per device, rotatable), never the owner's
++   stream key. Stream keys stop being robot credentials.
++2. **Pairing is a one-time code.** The owner adds a robot; Bot shows an 8-character code (Crockford base32, `XXXX-XXXX`,
++   10-minute lifetime, single use, 5 wrong tries end it) as text, as a QR code and inside the one-line installer command.
++   The agent sends `{pair: code, agent_version, device_kind, drivers, capabilities}` and receives its device id,
++   credential, publish key and the robot's profile. The owner sees the device appear and confirms it.
++3. **Three kinds of device connection, one agent.** **On-board**: the agent runs on the robot's own computer (Raspberry
++   Pi; ESP32 through a small library speaking the same protocol). **Bridge**: the agent runs on a computer next to the
++   robot and reaches it over the robot's own link (Cozmo first through PyCozmo; later Vector, Tello, Sphero, LEGO); a
++   bridge joins the robot's network on one interface and reaches OpenVibe on another. **Server-side**: Bot itself
++   connects to ONVIF/RTSP cameras (credentials by secret reference, never in the profile). The agent is a Python 3 package
++   (the Pi, PyCozmo and the kit libraries are Python), installed by `curl -fsSL https://openvibe.bot/install | sh` into a
++   virtual environment with a systemd unit and the hardware watchdog.
++4. **Control runs over one outbound WebSocket per device; video over WHIP.** The device dials Bot
++   (`wss://openvibe.bot/device`), authenticates with its credential, and keeps one connection for commands, telemetry and
++   heartbeats; this works behind any home router and on an ESP32. The camera publishes to OpenRe over WHIP; viewers watch
++   through OpenRe. Operators reach Bot over a WebSocket from the panel. A WebRTC data channel may be added later as a
++   second control transport when measured latency asks for it; the message set does not change.
++5. **One message set** (JSON, fields `v`, `seq`, `ts` on every frame): server→device `hello`, `config` (limits, heartbeat,
++   the operator's allowed commands), `command` (`id` as an idempotency key, `kind` drive/actuator/ptz/say/display/halt,
++   `value`, `deadline_ms`, operator and role), `estop`, `heartbeat_ack`; device→server `status`, `telemetry` (≤ 2 Hz),
++   `ack`/`nack` (with a fault code), `heartbeat`, `estop_state`. Commands are never queued for an offline device and
++   never replayed after a reconnect.
++6. **Safety is not optional.** Every motion command carries an absolute deadline (default 300 ms, at most the robot's
++   `max_command_ms`); a held control re-sends every 150 ms; the **device** stops the motors at the deadline, on a lost
++   heartbeat (1 s interval, stop after 2 missed) and on every disconnect or crash path, without asking the network. The
++   e-stop is latched on the device and in Bot and only the owner clears it. Speed, turn and range limits and time windows
++   are set by the owner; an operator never exceeds them. Cozmo additionally stops on a cliff or pick-up event. The agent
++   never runs or exposes a kit's stock control server (the Adeept `admin:123456` port stays off).
++7. **Robot profiles, not rows.** `bot.robot-profile@1` (Contracts): capabilities (drive differential/mecanum, pan-tilt,
++   lift, head, servos, lights, speaker/say, display, sensors, cameras, battery), panel widgets bound to capabilities,
++   limits and the driver mapping. The panel is a function of the profile; a new robot needs a profile, not code. First
++   profiles: `adeept.adr036` (ordinary and mecanum wheels), `cozmo`, `camera.onvif`, `sim.rover` (the browser simulator on
++   the openvibe.bot home). Capability and widget names are open strings checked against a registry in code, so a new
++   widget never needs a schema change.
++8. **Access.** Owner, operators (invited), viewers. A robot is private by default; public control exists only as a
++   timed queue (a visible turn timer, a per-turn command budget, cooldowns, per-role command allowlists) with an owner
++   kill switch. Chat control (Live, openvibe.chat) is a caller of the same gate: Chat or Live sends a command on behalf of
++   the viewer with a service token holding `bot.robot.control`, and Bot applies the role, the allowlist and the limits.
++9. **Everything is recorded.** Each command (robot, device, operator principal, kind, result, latency) goes to an audit
++   table kept 30 days; `bot.robot.online|offline`, `bot.command.refused`, `bot.estop.set|cleared` and telemetry summaries
++   are Events; Actor agents drive robots only through a delegated `bot.robot.control` grant and the owner's approval.
++10. **The service.** OpenVibe.Bot is its own repository and service on PostgreSQL (the platform chassis: openvibe-sdk db,
++    auth, limits, outbox; openvibe-shared Frame and showcase), public origin openvibe.bot. Capabilities
++    `bot.robot.read`, `bot.robot.manage`, `bot.robot.control`, `bot.device.connect`. Live's `server/controls/`, its
++    control tables and the stream-key device path are deleted once the panel embed works on Live channel pages and the
++    existing robot owners have paired again (converting presets to profiles and whitelists to operators).
++
++## Alternatives considered
++
++- **WebRTC data channel as the only control transport:** rejected for now. It ties control to video negotiation, needs
++  a TURN path for control alone, and does not run on an ESP32; one WebSocket carries control everywhere, and the message
++  set leaves room for a data channel later.
++- **Keep the stream key as the robot credential:** rejected. One string with three jobs (publish, control, URL) is the
++  largest standing risk in today's design.
++- **Run a kit's own server behind a proxy:** rejected. The Adeept server's fixed password and open MJPEG cannot be made
++  safe by wrapping; the agent drives the hardware itself.
++- **Generate per-robot scripts (Live's Cozmo approach):** rejected in favour of drivers plus profiles.
++
++## Migration consequences
++
++- Contracts: `bot.robot-profile@1`, `bot.device-message@1` (the envelope and each message type), the four capabilities,
++  the `bot` service manifest and its events.
++- Network: a `bot` service principal; the `bot.robot.control` grant for Live and Chat (on behalf of viewers) and for
++  Actor agents (delegated).
++- OpenRe: per-device publish keys for WHIP sessions created by Bot.
++- Live: the panel embed on channel pages, then the deletion in decision 10; Extensions `hardware/` becomes a pointer to
++  the Bot agent.
++
++## Rollback
++
++- The service is additive until Live's controls are deleted; before that, a robot owner can keep using Live's panel.
++- After the deletion, the rollback is the previous Live release plus the database backup.
++
++## Acceptance tests
++
++- Pairing: a code works once, expires after 10 minutes, dies after 5 wrong tries; the credential is never logged or
++  returned twice; rotation keeps the old credential for 60 s; revocation disconnects the device at once.
++- Safety: a drive command without a newer one stops the motors at its deadline; killing the network, the WebSocket or
++  the agent process stops the motors; the e-stop latches on the device and only the owner clears it; limits cap every
++  operator; Cozmo stops on a cliff event.
++- Access: a viewer cannot drive a private robot; a queued turn ends on its timer; chat commands pass the same gate.
++- Profiles: the Adeept and Cozmo profiles validate and render a panel with no robot-specific frontend code.
++- End to end: the agent in dry-run mode pairs, publishes a test pattern over WHIP, receives commands, answers
++  telemetry, and the panel shows video, latency and battery.
ddiff --git a/docs/HANDOFF.md b/docs/HANDOFF.md
nnew file mode 100644
iindex 0000000..e677651
---- /dev/null
++++ b/docs/HANDOFF.md
@@@ -0,0 +1,131 @@
++# Handoff: build the OpenVibe Node (cloud session brief)
++
++You are starting the OpenVibe Node from an empty repository. Read this whole file and `docs/ADR-043-bot-devices-and-control.md`
++first; they are binding. Work on a branch `node-core`, commit in small steps with clear messages, push, and open a pull
++request when the core and both robot plugins pass their tests. Do not deploy anything; you have no access to OpenVibe's
++servers and do not need it.
++
++## What the Node is
++
++One service people install on any computer, server, Raspberry Pi or phone. It pairs with OpenVibe once, connects
++**out** (no open ports), and lets OpenVibe products use the device: first **OpenVibe.Bot** (robots: drive, cameras,
++sensors, with safety), later **OpenVibe.Actor** (computer control for AI agents: terminal, files, screen, keyboard and
++mouse, the machine's own coding agents). One install serves robots and computers. Owner decisions (2026-09-29): Bot is an
++open control panel for robots; the owner's first robots are an **Adeept 4WD Smart Car Kit for Raspberry Pi (ADR036)**
++and a **Cozmo**.
++
++## Architecture (decided)
++
++- **Core: Go**, one static binary per platform (linux amd64/arm64/armv7, darwin amd64/arm64, windows amd64). Module path
++  `github.com/OpenVibers/OpenVibe.Node`. Libraries: `github.com/pion/webrtc/v4` (WHIP publishing), `nhooyr.io/websocket`
++  or `gorilla/websocket`, `github.com/kardianos/service` (systemd / launchd / Windows service). Keep dependencies few.
++- **Drivers are plugins**: separate executables the core starts, speaking **JSON lines over stdin/stdout** (one object per
++  line). Robot plugins are **Python 3** (the kit libraries and PyCozmo are Python). A plugin must stop every actuator
++  itself when its stdin closes, when a command's deadline passes, or when it has not heard a heartbeat from the core for
++  1 s — the core dying must never leave motors running.
++- **Layout**: `cmd/openvibe-node/` (CLI), `internal/{config,credentials,link,protocol,safety,plugins,video,service}/`,
++  `plugins/{dryrun,adeept_adr036,cozmo}/` (Python packages with their own tests), `install/install.sh`,
++  `.github/workflows/ci.yml`, `docs/{protocol.md,plugins.md,install.md}`.
++
++## The CLI
++
++`openvibe-node pair <CODE>` (redeems a one-time pairing code, stores the credential), `openvibe-node run` (foreground),
++`openvibe-node install` / `uninstall` (as a service), `openvibe-node status`, `openvibe-node stop` (**the local kill
++switch**: stops every plugin's actuators immediately and holds them stopped until `openvibe-node resume`), `openvibe-node
++plugins` (list, with capabilities). Config in `/etc/openvibe-node/` (or the platform's equivalent); the credential file is
++mode 0600 and its contents never appear in logs, errors or `status`.
++
++## Talking to OpenVibe.Bot (ADR-043 decisions 1, 2, 4, 5, 6)
++
++- Pairing: `POST https://openvibe.bot/api/v1/pair` with `{code, agent_version, device_kind: "onboard"|"bridge",
++  drivers: [...], capabilities: {...}}` → `{device_id, credential, publish_key, profile}`. Store credential and publish key.
++- Control link: `wss://openvibe.bot/device`, credential in the `Authorization: Bearer` header of the upgrade (never in the
++  URL). Every frame is JSON with `v` (1), `seq` (per-direction counter), `ts` (ms). Server→device: `hello`, `config`
++  (limits, heartbeat_ms, deadman_ms), `command` (`id`, `kind` drive|actuator|ptz|say|display|halt, `value`, `deadline_ms`,
++  `operator`, `role`), `estop` (latched), `heartbeat_ack`. Device→server: `status` (agent version, drivers, faults,
++  estop_latched), `telemetry` (≤ 2 Hz: battery, rssi, sensors), `ack` / `nack` (`id`, `fault_code`), `heartbeat` (1 s),
++  `estop_state`. A repeated command `id` is answered with the first result and never executed twice. Commands are never
++  queued while offline and never replayed after a reconnect. Reconnect with exponential backoff and jitter.
++- The service side (OpenVibe.Bot) is being built at the same time; its `docs/protocol.md` will be the exact wire format.
++  Keep every wire detail inside `internal/protocol/` so aligning later is one package. Build a **fake Bot server** in Go
++  test code that speaks this protocol and drive all link tests against it.
++
++## Safety (ADR-043 decision 6; not optional)
++
++- Every motion command carries an absolute deadline (default 300 ms, capped by the profile's `max_command_ms`); the
++  plugin stops at the deadline unless a newer command arrived. Held controls are re-sent by the operator every 150 ms.
++- Stop all actuators on: 2 missed heartbeats, link loss, core shutdown, plugin crash (the core restarts it with backoff
++  and it starts stopped), `openvibe-node stop`, an `estop`.
++- The e-stop is latched locally (persisted across restarts) and only a server `estop_clear` from the owner (or the local
++  `resume`) clears it. Owner limits (`max_speed`, `max_turn`) clamp every value in the core before it reaches a plugin.
++- Never run or expose a kit's stock control server (the Adeept kit ships one on 0.0.0.0:8888 with the fixed login
++  `admin:123456` and an MJPEG stream on :5000 — the Node replaces it; `install.sh` disables it if it finds it enabled).
++
++## Plugin protocol (write `docs/plugins.md`)
++
++Core→plugin: `{"op":"hello","config":{...}}`, `{"op":"command","id":..,"kind":..,"value":..,"deadline_ms":..}`,
++`{"op":"heartbeat","t":..}`, `{"op":"stop"}`, `{"op":"estop"}`. Plugin→core: `{"op":"describe","capabilities":{...},
++"driver":"...","version":"..."}`, `{"op":"ack"|"nack","id":..,"fault_code":..}`, `{"op":"telemetry",...}`,
++`{"op":"event","name":"cliff"|"picked_up"|"low_battery"|...}`, `{"op":"video","format":"jpeg","path":...}` for plugins
++that produce camera frames.
++
++## Plugin 1: `adeept_adr036` (the owner's first robot)
++
++Raspberry Pi OS Bookworm, Python 3, `adafruit-circuitpython-pca9685`, `adafruit-circuitpython-motor`, `gpiozero`,
++`spidev`, `smbus2`. From the kit's own code (Adeept ADR036, 2025–2026):
++- **Motors**: PCA9685 at I²C **0x5f**, frequency 50; DC motors M1 = channels (15, 14), M2 = (12, 13), M3 = (11, 10),
++  M4 = (8, 9) via `adafruit_motor.motor.DCMotor`, `SLOW_DECAY`; throttle -1..1. Two variants: **ordinary wheels**
++  (differential: throttle + steer) and **mecanum** (x, y, rotation). Check the kit's wheel-to-motor assignment in its
++  `Move.py` (`move(speed, direction, turn, radius)`) and mirror it; make the mapping a table in the plugin config.
++- **Servos**: same PCA9685, pan = channel 0, tilt = channel 1, `adafruit_motor.servo.Servo(min_pulse=500,
++  max_pulse=2400, actuation_range=180)`; limits in config.
++- **Sensors**: ultrasonic `gpiozero.DistanceSensor(echo=24, trigger=23, max_distance=2)`; line tracking inputs GPIO 22
++  (left), 27 (middle), 17 (right); battery through an **ADS7830 at I²C 0x48** (`read_byte_data(0x48, cmd)` per channel;
++  report volts and a percentage for a 2×18650 pack).
++- **Buzzer**: `gpiozero.TonalBuzzer(18)`; **WS2812 LEDs** over SPI (`spidev`, bus 0 device 0).
++- **Camera**: Picamera2/libcamera. The core publishes it: prefer `rpicam-vid --codec h264 --inline -o -` piped into the
++  WHIP publisher; fall back to MJPEG frames from the plugin.
++- Tests: a fake I²C/GPIO layer so the plugin runs on any machine; assert the deadline stop, stdin-EOF stop, estop, and the
++  exact channel numbers.
++
++## Plugin 2: `cozmo` (a bridge plugin)
++
++Cozmo runs closed firmware and makes its own Wi-Fi access point with no internet. The Node runs on a computer next to it
++(a Pi or a laptop) joined to Cozmo's Wi-Fi on one interface and to the internet on another. Use **PyCozmo** (MIT,
++`pip install pycozmo`, github.com/zayfod/pycozmo): `pycozmo.connect()` / `Client`, `drive_wheels(l, r, duration)`,
++`set_head_angle`, `set_lift_height`, `play_audio` (for say: synthesize with `espeak-ng` or `pico2wave` to 22 kHz mono
++PCM), `display_image` (text/faces rendered with Pillow to 128×32/64), backpack and cube lights, camera frames
++(`enable_camera`, 320×240, grey or colour) handed to the core as JPEG, battery voltage, **cliff and pick-up events that
++stop the wheels at once**. Check the robot's firmware at connect and report `nack` with a clear fault if PyCozmo does not
++support it. Map commands so Cozmo's head and lift appear as ptz-like actuators. Tests with a fake PyCozmo client.
++
++## Plugin 0: `dryrun`
++
++Accepts every command, logs it, answers telemetry and a test-pattern video source — used by CI, by people trying the
++Node on a laptop, and by the service's end-to-end tests.
++
++## Video (WHIP)
++
++`internal/video`: publish H.264 over WHIP with pion to the `whip_url` + `publish_key` the pairing returns. Sources: test
++pattern (dry-run), an H.264 byte stream from a child process (`rpicam-vid`, `ffmpeg -f v4l2`), JPEG frames from a plugin
++(encoded through `ffmpeg`). Reconnect on failure; video never blocks control.
++
++## install.sh and CI
++
++`install/install.sh` (`curl -fsSL https://openvibe.bot/install | sh -s -- <CODE>`): detect OS/arch, download the release
++binary and the plugin bundle, create a Python virtual environment for plugins, install the service, pair with the code.
++CI: `go vet`, `go test ./...` (race detector), cross-compile every target, Python plugin tests, and a release workflow on
++tags that attaches the binaries.
++
++## Later, not in this session
++
++Actor's computer control plugin (terminal, files, screen, input, browser, local coding agents) with control levels
++(Observe, Ask, Trusted, Full control) — design the plugin and capability interfaces so it drops in without changing the
++core. Say in `docs/` where it will attach.
++
++## Done means
++
++`go test ./...` and the Python plugin tests green in CI on the PR; `openvibe-node run` with `dryrun` pairs against the fake
++server, publishes a test pattern, obeys commands and stops on every safety path; the Adeept and Cozmo plugins pass their
++tests with fake hardware; `docs/protocol.md`, `docs/plugins.md` and `docs/install.md` written; README says what the Node
++is and how to install it.