feat(firmware): validate configuration and migrate sensor-driven flight APIs

Validate configuration through its owning schemas and keep board
declarations separate from shared F722 resource ownership. Bound USB
transitions, isolate transport failures and retain restart-only activation.

Migrate navigation and flight consumers with the sensor and schema
contracts. Require explicit installation data and synchronous output
authority; board motor outputs remain inhibited.

Validation: assembled-prefix host tests, strict Clippy, platform/USB tests
and both ARM release builds. Final-source coverage and scoped Miri/Kani
evidence are retained separately from hardware qualification.

firmware/tools/configurator/web/index.html

@@ -35,11 +35,15 @@
 
         <aside id="restart-guidance" class="important" role="status" hidden>
           Saved configuration becomes active after the controller restarts.
+          The current serial link keeps its boot-active settings until restart.
         </aside>
+        <p class="hint">Inputs edit the saved draft. Boot-active values stay in use until restart.
+          USB remains available for configuration and recovery.</p>
         <ul id="validation"></ul>
         <form id="draft-fields" class="draft-fields"></form>
         <div class="actions" aria-label="Configuration actions">
           <button id="save" type="button">Save</button>
+          <button id="reset-saved" type="button">Reset saved configuration</button>
         </div>
       </section>
 
@@ -69,6 +73,7 @@
         </div>
       </section>
     </main>
+    <script src="/view.js"></script>
     <script src="/app.js"></script>
   </body>
 </html>