No border-radius declaration in app/(public)/_shell/primitives.css has a value other than 0.that rounds anything, however that value is spelled.
No border-radius declaration in app/(public)/_shell/primitives.css has a value that rounds anything, however that value is spelled.
condition, falsification, receipt
- Declarations only, where a declaration is a line whose first non-space characters are `border-radius:`. A value counts as zero when every component of it is zero, in any unit and in any of the one-to-four value forms. Holds for any number of such declarations, including none. As of 2026-07-30, for the copy of that file in this repository. Re-hashed on every read of this page.
- `grep -E '^[[:space:]]*border-radius[[:space:]]*:' 'app/(public)/_shell/primitives.css' | grep -vE ':[[:space:]]*(0(px|%|em|rem)?[[:space:]]*)+;?$'` prints any line at all.
notes
Replaces `shell-radius-zero-only`, which states the same property and tests it with a filter that only recognises one spelling of zero. That claim's survivor pattern is `:[[:space:]]*0[[:space:]]*;?$` - it accepts a bare `0` and nothing else, so `border-radius: 0px`, `border-radius: 0 0 0 0` and `border-radius: 0%` are all reported as violations even though not one of them rounds a corner.
Measured rather than argued. Against a file containing the five spellings `0`, `0px`, `0 0 0 0`, `24px` and `50%`, the old condition flags four lines and the new one flags two. The two it flags are `24px` and `50%`, which are the only two that paint. Against `primitives.css` as it stands today both conditions return no lines, so nothing about the shell changed - what changed is which future edits would set off a false alarm.
This is the same defect one level up. `shell-radius-count-five` was replaced because its condition fired on a change that violated nothing; its replacement shipped with a condition that fires on a change that violates nothing. The lesson that keeps repeating is that a check written against source TEXT is a check on how something is written, and the property being protected is about what is drawn. A condition stated over computed style on a rendered page would not have either defect, and would need a different kind of evidence than a file digest; that is the next revision, not this one, and saying so is cheaper than implying this wording is final.
`shell-radius-zero-only` is not deleted. Its file stays in `content/claims/`, its URL keeps resolving, and this claim's id is what marks it replaced.
evidence
primary source - not independently openable
glovrex-engine is a private repository. This path identifies the source; it is not a link a reader can open.
challenges
none yet
Nobody has proposed a test against this yet.
relations
lab
citation
copyable line + linked excerpt
Glovrex. "No border-radius declaration in app/(public)/_shell/primitives.css has a value that rounds anything, however that value is spelled." Claim shell-radius-zero-any-spelling, checked 2026-08-05. https://glovrex.com/claims/shell-radius-zero-any-spelling