fix(conformance): mark the ambiguous-forge probe's expected server ERROR log #388
No reviewers
Labels
No labels
breaking
bug
documentation
enhancement
epic
good first issue
help wanted
refactoring
resolution/duplicate
resolution/invalid
resolution/wontfix
security
severity/critical
severity/high
severity/low
severity/medium
status/abandoned
status/blocked
status/needs-decision
status/needs-info
status/needs-verification
testing
upstream
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
sixfold-space/madtea!388
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix-mcp-conformance-mark-expected-error"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
The T9 fail-closed probe deliberately triggers the server's ambiguous-forge refusal, and the serve child logs that refusal at ERROR level. In a passing run the ERROR line printed with nothing marking it as expected, so the output read as an escaped failure.
Add a "note: EXPECTED server ERROR follows" line before the probe call, so the ERROR log reads as the asserted fail-closed refusal.
Verified: mcp-conformance PASS, the marker prints directly above the ERROR line.