Update demo replay validation and testing documentation

- Modified the autodev state to reflect the current testing phase and details of the new `jetson-e2e` tests.
- Enhanced the "How to Test" documentation to provide clearer instructions on the demo replay validation process, including video and tlog alignment steps.
- Updated architectural documentation to include the new demo replay operator flow and its dependencies.
- Documented the removal of deprecated auto-sync features and clarified the operator-facing UI for replay validation.
- Added new entries in the dependencies table for upcoming tasks related to the demo replay flow.

These changes improve clarity and usability for operators and developers working with the demo replay system.

.cursor/rules/openapi.mdc

@@ -0,0 +1,15 @@
+---
+description: "OpenAPI/Swagger API documentation standards — applied when editing API spec files"
+globs: ["**/openapi*", "**/swagger*"]
+alwaysApply: false
+---
+# OpenAPI
+
+- Use OpenAPI 3.0+ specification
+- Define reusable schemas in `components/schemas`; reference with `$ref`
+- Include `description` for every endpoint, parameter, and schema property
+- Define `responses` for at least 200, 400, 401, 404, 500
+- Use `tags` to group endpoints by domain
+- Include `examples` for request/response bodies
+- Version the API in the path (`/api/v1/`) or via header
+- Use `operationId` for code generation compatibility