Repository navigation
Harness: accept opencode2 as an alias of runner - #1364
Merged
Merged
Conversation
Thalamus's OpenCode 2 runner binds with harness opencode2, and AFT refused
core's plan preflight for its first head ('configure payload invalid field
harness'). Those sessions' AFT calls arrive over Thalamus's scoped routes,
consent goes through core, and AFT's OpenCode plugin is never loaded on that
server, so they are runner sessions: opencode2 parses as Harness::Runner
(storage, consent route, reply shape). The route identity keeps the name the
daemon sent. thalamus-harness binding for opencode2 is first-party, like its
existing opencode pair.
Co-authored-by: alfonso-aft <289616620+alfonso-aft@users.noreply.github.com>
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Thalamus's OpenCode 2 runner binds with harness
opencode2(live since 14:41Z), and AFT refused core's plan preflight for its first head:configure payload invalid field 'harness'.THALAMUS confirmed what these sessions are: their AFT calls arrive over Thalamus's own scoped routes as tool-provider calls (call_key, schema pin), consent goes through core and Cingulate, and AFT's OpenCode plugin is never loaded on that server. So they are runner sessions.
Harness::from_str("opencode2")→Harness::Runner(storage namespacerunner, consent through core, runner reply shape). Only the exact spelling is an alias. The route identity keeps the name the daemon sent, so wakes, pushes and catalog params still addressopencode2.(thalamus-harness, opencode2)joins(thalamus-harness, opencode)as a first-party pair; THALAMUS confirmed its routes bind asreserved:thalamus-harness. Any other module onopencode2stays untrusted.Tests:
opencode2_parses_as_the_runner_harness,thalamus_harness_on_opencode2_is_first_party, andopencode2(trailing space) added to the stays-untrusted list. Gate: 386 harness, subc trust, configure, subc_config, access-grant and semantic-admission tests, formatting and the Windows check.Summary by cubic
Treats sessions Thalamus runs on an OpenCode 2 server as runner sessions so AFT's plan preflight no longer rejects them with
configure payload invalid field 'harness'.opencode2now parses asHarness::Runner, keeping therunnerstorage namespace, consent route, and reply shape; only the exact spelling is aliased.opencode2.(thalamus-harness, opencode2)is now a first-party pair like the existing(thalamus-harness, opencode); any other module bindingopencode2stays untrusted.Written for commit 4217402. Summary will update on new commits.