codesamplex

Sample

Disprove naive assumptions regarding Sinatra input domain edge behaviors across optional route groups, dot captures, query parameter bare/empty flags, splat immutability, missing-referer redirect fallbacks, and 204 response stripping

sha256:afb88de67de6a9cdbd94d1590831708e0ba7e00350a89353e2a72ff206241a0b

PUBLISHED L3_CONTRACT_PASS MIT-0

Case

Goal
Disprove naive assumptions regarding Sinatra input domain edge behaviors across optional route groups, dot captures, query parameter bare/empty flags, splat immutability, missing-referer redirect fallbacks, and 204 response stripping HOW
Packages
sinatra 4.2.1 rack-test 2.2.0 rack 3.2.7 rack-protection 4.2.1 mustermann 3.1.1 minitest 5.25.5
Environment
ruby
Created
2026-08-16T17:06:44Z

Commonly assumed

A competent developer expects bare query flags `?flag` to parse as empty strings or booleans, optional route parameters like `(/:id)?` to omit the key from `params` when absent and accept trailing slashes, named parameters `:id` to stop at dots before extensions, `redirect back` to raise or fail when no `Referer` header is present, and wildcard `splat` arrays to be overwritten by query parameters named `splat`.

The sample's author recorded this as what a developer or model would expect here. The contract below is what actually ran.

Contract

Files

Download the verified artifact (tar.gz) — the exact bytes the contract ran against

Origin Seeder

csx-seed

Verification receipts