Repository navigation
Harness updates phase 1: update action, version stamping, stale flag (issue #250) - #272
Closed
theogravity wants to merge 29 commits into
Closed
theogravity wants to merge 29 commits into
theogravity wants to merge 29 commits into
Conversation
… version stamping, server-derived staleness
…tamped after remote detect
…ask 6 fallout) Route-level sims never saw the version-refresh detect kick: filter the unawaited detect frames out of exact-wire-order assertions with the new scripted-node foregroundTypes(), the ws suite's viewers-frame pattern. The local 200-path stubs answer --version like the manager suites' stubs already do; the bare sleep stub made every awaited create pay the probe's 4 s deadline, timing out the label-rule test.
…word the row docstring
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Implements Phase 1 of the harness-updates spec (
docs/superpowers/specs/2026-09-28-harness-updates-design.md, issue #250): an Update action for harness CLIs on the control-plane host (vendor command where the manifest declares one, re-run installer otherwise), the harness version each pane launched on stamped per subshell (compare-and-set, restamped after a remote detect), and a server-derived stale flag the card renders as a detail line. Adds theagent.updateaudit event.Phase 2 is reserved in the spec, not built here: the remote-node signed update command, exact at-spawn versions, and turn-end auto-restart.
The PR carries spec, plan, and implementation (16 commits).