STET

flux-pr-1351

graphql-go-tools (Go) · W1 · GPT-5.1 Codex Mini

pass_with_warn

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

57.1% run pass rate
Tier 1
primary testspasseddecision conflictnon equivalentunsure
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
tool call
Command started
#2

shell command

tool result
Command finished
#3

shell command exit code 0

tool call
Command started
#4

shell command

tool result
Command finished
#5

shell command exit code 0

tool call
Command started
#6

shell command

tool result
Command finished
#7

shell command exit code 1

tool call
Command started
#8

shell command

tool result
Command finished
#9

shell command exit code 0

tool call
Command started
#10

shell command

tool result
Command finished
#11

shell command exit code 0

tool call
Command started
#12

shell command

tool result
Command finished
#13

shell command exit code 1

tool call
Command started
#14

shell command

tool result
Command finished
#15

shell command exit code 0

tool call
Command started
#16

shell command

tool result
Command finished
#17

shell command exit code 0

tool call
Command started
#18

shell command

tool result
Command finished
#19

shell command exit code 0

tool call
Command started
#20

shell command

tool result
Command finished
#21

shell command exit code 0

tool call
Command started
#22

shell command

tool result
Command finished
#23

shell command exit code 0

tool call
Command started
#24

shell command

tool result
Command finished
#25

shell command exit code 0

tool call
Command started
#26

shell command

tool result
Command finished
#27

shell command exit code 0

tool call
Command started
#28

shell command

tool result
Command finished
#29

shell command exit code 0

tool call
Command started
#30

shell command

tool result
Command finished
#31

shell command exit code 0

tool call
Command started
#32

shell command

tool result
Command finished
#33

shell command exit code 0

tool call
Command started
#34

shell command

tool result
Command finished
#35

shell command exit code 0

tool call
Command started
#36

shell command

tool result
Command finished
#37

shell command exit code 0

tool call
Command started
#38

shell command

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 result
Command finished
#43

shell command exit code 0

tool call
Command started
#44

shell command

tool result
Command finished
#45

shell command exit code 0

tool call
Command started
#46

shell command

tool result
Command finished
#47

shell command exit code 0

tool call
Command started
#48

shell command

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

unsure

decision
Final decision
#53

pass_with_warn

Quality

equivalence
non_equivalent
88% confidence
code review
unsure
1 finding
footprint
medium (0.46)
behavioral
100.0%
cost
$1.66 · 4.6M

Equivalence Reasoning

behavioral

The patch does add grouped storage and deterministic joining, but it misses core intended behavior for per-subgraph attribution in loader hook responses: `newResponseInfo` call sites now pass `ctx.SubgraphErrors()` (the global joined error), so `ResponseInfo.Err` is still not scoped to the current subgraph. The gold intent is to provide each response with its own subgraph’s error (`subgraphErrors[res.ds.Name]`). Also, the new grouped store appears to be map-backed without clone deep-copy updates, which can cause aliasing across cloned contexts.

Code Review

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

The patch mostly implements grouped subgraph error storage and deterministic ordering, but a key integration point still appears to propagate aggregated errors to loader hook response info, so it likely does not fully satisfy the intended per-subgraph attribution change.

1 finding
Loader hook still receives globally joined subgraph errors
major

`newResponseInfo` call sites were switched to pass `l.ctx.SubgraphErrors()`, which is the aggregate joined error, so `ResponseInfo.Err` can still represent all subgraphs rather than the current result subgraph. This conflicts with the intended per-subgraph attribution behavior.

v2/pkg/engine/resolve/loader.go:252