Repository navigation
Conversation
adewale
force-pushed
the
claude/interop-2026-10-24
branch
from
October 29, 2026 18:18
de613e0 to
6b32b10
Compare
adewale
force-pushed
the
claude/interop-2026-10-24
branch
from
November 12, 2026 23:35
d02855e to
a013051
Compare
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.
A live Company without conversations or MCP currently produces failed interop cells. This change reports those absent capabilities as unsupported, while keeping failures for manifest-backed adapters that claim the scenario and for broken advertised features. Missing statically required fixture data also stops a live cell before any scenario request.
The PR now targets current
mainand Poppy 0.4 only. It retains the harness fixes and their regression tests. Main's newer currency and deterministic feedback concurrency tests are preserved. The October reports and 0.3 evidence remain in the previous immutable snapshot.Changes
C,CLandMLwithoffers: true; only a live capability miss becomes unsupported. An advertised MCP API returning no tools still fails.Verification
S0fixture still runs.Visual evidence
Reviewer cue:
fixture-livechanges from red fail to grey n/a (unsupported) in bothCLandML.fixture-claimedremains red fail in both.Base SHA:
b2fc42893ce719023681ff0df14a2b485e6d75d3Head SHA:
a013051d270a006b1507002b3ef0893b7cc17ce3The same synthetic discovery response uses actual immutable runner/scenario sources and the production renderer at the same viewport. The renderer's full runtime dependency closure is pinned, checked and hashed. Assertions check all four cell outcomes and the rendered counts. Capture source:
3f240b5f43c97a6012b612f1d0f4e2e0cb7e15e9; the final head adds evidence files only.Limits and risk
No live Company was contacted. The screenshots demonstrate synthetic classification, and CLI preflight has separate regression tests. A live Company dropping a capability will now appear as unsupported;
--require-supportedstill fails runs that require every cell to execute. Current production discovery and sandbox discovery/Session permissions remain unchanged.