STET

flux-pr-891

graphql-go-tools (Go) · W2 · GPT-5.4

pass_with_warn

Tests passed. 1/1 commands passed. Strength: strong.

89.7% run pass rate
Tier 1
primary testspassednon equivalentdecision conflictfail
go test -C v2 ./... -count=1 -timeout=300s
gold passagent pass

Partial score: 1/1

Publishable: yesCache: miss

Trajectory

codex · partial order only

provider-native trajectory captured; validation and decision steps are appended with coarse ordering only

session start
Session started
#1
assistant turn
Assistant turn
#2
tool call
Command started
#3

shell command

tool call
Command started
#4

shell command

tool result
Command finished
#5

shell command exit code 0

tool result
Command finished
#6

shell command exit code 0

tool call
Command started
#7

shell command

tool result
Command finished
#8

shell command exit code 128

assistant turn
Assistant turn
#9
tool call
Command started
#10

shell command

tool call
Command started
#11

shell command

tool result
Command finished
#12

shell command exit code 0

tool result
Command finished
#13

shell command exit code 0

tool call
Command started
#14

shell command

tool call
Command started
#15

shell command

tool result
Command finished
#16

shell command exit code 0

tool result
Command finished
#17

shell command exit code 0

assistant turn
Assistant turn
#18
tool call
Command started
#19

shell command

tool call
Command started
#20

shell command

tool result
Command finished
#21

shell command exit code 0

tool result
Command finished
#22

shell command exit code 0

tool call
Command started
#23

shell command

tool call
Command started
#24

shell command

tool result
Command finished
#25

shell command exit code 0

tool result
Command finished
#26

shell command exit code 0

tool call
Command started
#27

shell command

tool call
Command started
#28

shell command

tool result
Command finished
#29

shell command exit code 0

tool result
Command finished
#30

shell command exit code 0

tool call
Command started
#31

shell command

tool result
Command finished
#32

shell command exit code 0

tool call
Command started
#33

shell command

tool result
Command finished
#34

shell command exit code 0

assistant turn
Assistant turn
#35
tool call
Command started
#36

shell command

tool call
Command started
#37

shell command

tool result
Command finished
#38

shell command exit code 0

tool result
Command finished
#39

shell command exit code 0

tool call
Command started
#40

shell command

tool result
Command finished
#41

shell command exit code 0

tool call
Command started
#42

shell command

tool call
Command started
#43

shell command

tool result
Command finished
#44

shell command exit code 0

tool result
Command finished
#45

shell command exit code 0

tool call
Command started
#46

shell command

tool call
Command started
#47

shell command

tool result
Command finished
#48

shell command exit code 0

patch written
Patch captured
#49

Flux captured agent.patch for this trial

validation
Tests passed
#50

go

equivalence
Equivalence judgment
#51

non_equivalent

code review
Code review judgment
#52

fail

decision
Final decision
#53

pass_with_warn

Quality

equivalence
non_equivalent
86% confidence
code review
fail · 25/100
4 findings
footprint
medium (0.35)
behavioral
100.0%
cost
$2.64 · 4.6M

Equivalence Reasoning

behavioral

Code Review

correctness: 1/4edge case handling: 1/4introduced bug risk: 1/4maintainability idioms: 1/4

The patch partially addresses typename validation and quote escaping, but it likely does not satisfy the intended change due to mismatched error contract (`INVALID_GRAPHQL`), different validation location/semantics, and non-idiomatic global metadata handling.

4 findings
Extension code does not match intended contract
major

The patch emits `INVALID_GRAPHQL_RESPONSE` for invalid typename errors, while the intended change specifies an `INVALID_GRAPHQL` code. This is a behavioral/API mismatch for downstream error handling.

v2/pkg/engine/resolve/const.go:45
Validation moved to object walk instead of `__typename` field resolution
major

The implementation validates `value.__typename` during object traversal and can null objects on failure, rather than validating returned values in the `__typename` scalar selection context. This changes semantics and can trigger errors when `__typename` is not part of the selected field set.

v2/pkg/engine/resolve/resolvable.go:456
Error payload omits subgraph source context required by the change
major

Invalid typename errors are generated without datasource/source attribution; intended behavior requires descriptive subgraph-origin messaging for federated responses.

v2/pkg/engine/resolve/resolvable.go:1037
Global pointer-keyed metadata map introduces hidden lifecycle/state complexity
major

Storing possible typename metadata in a package-level `sync.Map` keyed by `*Object` creates implicit shared state and potential leaks/stale metadata concerns, instead of explicit schema metadata on the node itself.

v2/pkg/engine/resolve/node_object.go:8