Skip to content

fix(harness): integrate the conflicting runtime corrections - #2509

Open
rudycelekli wants to merge 1 commit into
ruvnet:mainfrom
rudycelekli:integrate/harness-runtime-20261109
Open

rudycelekli wants to merge 1 commit into
ruvnet:mainfrom
rudycelekli:integrate/harness-runtime-20261109

Conversation

@rudycelekli

Copy link
Copy Markdown

Summary

The ten open harness pull requests each regenerate manifest.json / manifest.sha256, so GitHub reports all of them as conflicting and they cannot land one at a time. This rebases the code and tests onto current main (e24be921) and regenerates both RuView and HomeCore provenance manifests once.

Supersedes:

Same shape as #2248: one reviewed integration instead of a stack of manifest conflicts.

Test plan

  • npm test in harness/ruview on this tree: 451 passed, 5 skipped, 2 failed. The two failures are test/hosts.test.mjs comparing /var/folders/... with /private/var/folders/... on this Mac. They do not touch these patches.
  • New regressions in this PR all passed inside that run (brain citations, ESPHome notation and disconnect, MCP framing, process cancellation, redaction, room output, serial-pump cleanup, spaces legacy kind, training score range).
  • node harness/ruview/scripts/verify-manifest.mjs and node harness/homecore/scripts/verify-manifest.mjs both report ok: true.
  • Maintainer: approve fork workflows so the hosted suite runs on this head.

Made with Cursor

These ten patches each rewrote the provenance manifests, so they could not merge independently. Rebase the code and tests together and regenerate both manifests once.

Co-authored-by: Cursor <cursoragent@cursor.com>

This branch has not been deployed

No deployments
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.

1 participant