Skip to content

Identify status publisher sessions for demonstration recording - #76

Draft
Jepson2k wants to merge 8 commits into
feat/execution-speed-overridefrom
feat/demonstration-recording
Draft

Jepson2k wants to merge 8 commits into
feat/execution-speed-overridefrom
feat/demonstration-recording

Conversation

@Jepson2k

@Jepson2k Jepson2k commented Sep 8, 2026

Copy link
Copy Markdown
Owner

Distinguish a controller publisher's lifetime from its configured controller ID. Append session_id to STATUS and expose it alongside the existing sequence and snapshot timestamp. The client accepts a new session with a restarted sequence and drops duplicate/out-of-order frames within a session.

The Python client advertises timed observations for recording. Client and daemon must both include this STATUS extension. No RT motion algorithm changes are needed: Commander waypoint replay uses the existing planner and execution controls.

Depends on #75. Coordinated with the waldoctl, PAROL6-python-API and Waldo-Commander feat/demonstration-recording branches.

Validation: protocol codec/hostile-input suite, real server publisher-session and client transport tests, Python daemon session, Commander native capture/export/import/replay, all-target workspace clippy, formatting and Python type checks pass.

Companion PRs: waldoctl #33, PAROL6 #46, PAR6 #76, Waldo Commander #59.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants