STET

flux-pr-891

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

fail_guardrail

Tests: unknown. 0/1 commands passed. Strength: missing.

57.1% run pass rate
Tier 1
guardrail preflight failedprimary equivalenceunknownnon equivalentneeds generated testsweak signal riskall commands ignoredunknown no gold pass commands
go test -C v2 ./... -count=1 -timeout=300s
gold unknownagent

Partial score: 0/0

Publishable: noWeak signal risk: yes

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 0

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 0

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 1

tool call
Command started
#48

shell command

patch written
Patch captured
#49

Flux captured agent.patch for this trial

validation
Validation recorded
#50
equivalence
Equivalence judgment
#51

non_equivalent

code review
Code review judgment
#52

fail

decision
Final decision
#53

fail_guardrail

Quality

equivalence
non_equivalent
89% confidence
code review
fail · 30/100
3 findings
footprint
low (0.32)
behavioral
cost

Equivalence Reasoning

behavioral

Code Review

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

Patch appears incomplete/misaligned with the intended PR: it likely has a compile-time API mismatch in tests and implements typename validation/error semantics differently enough to risk failing expected behavior.

3 findings
fastjsonext test calls do not match function signature
major

`CreateErrorObjectWithPath` remains defined as `(message, path)`, but tests call it as `(arena, message, path)`, which is a compile-time mismatch.

v2/pkg/fastjsonext/fastjsonext.go:24
Typename error contract differs from intended implementation
major

Invalid typename errors use `INVALID_TYPENAME` and omit subgraph source attribution, while the intended change uses a standardized extension code path and source-aware message; this likely breaks expected output semantics.

v2/pkg/engine/resolve/resolvable.go:50
Validation is attached to object node, not merged __typename field context
major

Allowed typenames are stored as object-level `PossibleTypeNames` and checked in `walkObject`; this can diverge from per-selection-context typename validation, especially where field contexts are merged.

v2/pkg/engine/plan/visitor.go:659