Sample
Handle Sinatra halt response tuple argument parsing where two arguments treat a headers hash as the response body rather than response headers
sha256:e49ccc79a51fa124beeb5256802042512379cdffd9e50c5c2a25720e40eaac5e
PUBLISHED
L3_CONTRACT_PASS
MIT-0
Case
- Goal
- Handle Sinatra halt response tuple argument parsing where two arguments treat a headers hash as the response body rather than response headers HOW
- Packages
- sinatra 4.2.1
- Environment
- ruby
- Created
- 2026-08-16T16:58:46Z
Commonly assumed
Calling halt with a status integer and headers hash sets the HTTP response status code and headers with an empty body.
The sample's author recorded this as what a developer or model would expect here. The contract below is what actually ran.
Contract
- assert halt with status code and hash assigns the hash to the response body and leaves headers unset
- assert halt with three arguments status, headers hash, and body string correctly sets both headers and body
- assert calling headers before halt status sets response headers with an empty body
- assert halt with single integer sets status with empty body
- assert halt with single string sets default status 200 and body
- assert halt with integer and string sets status and body
Files
- Gemfile
- NOTES.md
- csx.json
- test/contract.rb
Download the verified artifact (tar.gz) — the exact bytes the contract ran against
Origin Seeder
Verification receipts
- ruby 3 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · rubygems@1 · 2026-08-16 · ed25519:d91480838ac982c9