Development record
five nits from the round five ruthless review including a weak negative assertion in the control refusal test
issueresolvednitpickiss-2608301657350399
five nits from the round five ruthless review including a weak negative assertion in the control refusal test
Five nits from the round-5 ruthless review, held on one record because each is a sentence or a name rather than a behaviour.
grounds_test.go-- the guard added against the store-wide over-claim is bound to ONE spelling. Changing the refusal to say "no record field can CARRY" leaves the suite green and restores the defect iss-2608301646042379 records, verbatim in meaning. The test's second half (the four runes the store holds must not be refused) is substantive; only the negative substring is weak. This is the orchestrator's own test and the hit is fair.cli.go--requireGroundsFlag's doc comment sits in the block that terminates atfunc groundsUsageError, so godoc attributes it to the wrong function andrequireGroundsFlaghas no doc at all.intent/ready.go--groundsCheckreusesclaimCheckExemption, so the grounds row on a shipped record reads "a shipped record's CLAIMS are never backfilled". Wrong noun for the check reporting it; the same detail-string class as the resolved iss-2608300210588414.lint/schema_test.go--TestCaptureReaderAcceptsGroundsKey's name and doc claim it proves the allow-list through the READER, but the body only callsLintand never invokes capture. Packagelintcannot importcapture, so the name promises coverage the package cannot hold; the reader side is proved incapture.TestReaderVerdictOnGroundsSpellings.grounds.go--isTextLetter's comment says the rest of the default-ignorable set is format characters and variation selectors. Measured: the table holds 3776 code points, of which 4 are Lo, 3 are Mn, and 3769 are unassigned; zero Cf and zero variation selectors, which live in the DERIVED property rather than this one. The conclusion the sentence supports is correct and was verified exhaustively; the description of the remainder is not. The same loose phrasing is in the round-4 decision dcn-2608300000000015.
Grounds
- pursued: we expect a guard bound to one spelling to be defeated by the next rewording rather than by malice, and a mutation that swapped only the verb leaving the old assertion green while the new one fails on three counts is what shows the anchor moved
Frontmatter
| id | iss-2608301657350399 |
|---|---|
| type | issue |
| lifecycle | resolved |
| severity | nitpick |
.abcd/work/issues/resolved/iss-2608301657350399-five-nits-from-the-round-five-ruthless.md
open on GitHub ↗ · commit history ↗
mentions5
- dcn-26083000000000152026-08-30 — itd-179 round-4: the grounds floor's character half counts LETTERS (`MinTextLetters = 20`, `isTextLetter`) and is asked AFTER the unit half. Both halves stay, as the round-3 entry above requires — what changes is the unit each is measured in and the order they are asked in. A rune count is answered by whatever occupies a rune: `a b c` plus seventeen dots cleared twenty "characters" carrying three letters of reasoning, and a text of Hangul fillers cleared the whole floor while rendering as nothing end to end. Rejected: asking the letter count first, which makes the scriptio-continua refusal unreachable — every unit that refusal speaks for is a single letter, so a text with twenty letters has twenty units and can never be below the three-unit floor, and one with fewer would be refused for its letters instead. Rejected: filtering only the zero-width format characters, which leaves the filler class open because U+115F, U+1160, U+3164 and U+FFA0 are category Lo; `unicode.Other_Default_Ignorable_Code_Point` names exactly those four letters and nothing else. Corpus: the 25 recorded grounds texts in the tree are refused by neither the old floor nor the new one.
- dcn-26083000000000182026-08-30 — itd-179 round-5, correction to the round-4 letter-floor entry above: `unicode.Other_Default_Ignorable_Code_Point` does NOT "name exactly those four letters and nothing else", and the remainder is not "format characters and variation selectors". Measured over the whole code space: the table holds 3776 code points, of which exactly seven are assigned — the four Hangul filler letters (Lo) and three non-spacing marks (Mn) — and the other 3769 are unassigned; it carries zero format characters and zero variation selectors, which reach `Default_Ignorable_Code_Point` through the other contributors to that derived property. The conclusion the round-4 entry drew is unchanged and was verified exhaustively — the only LETTERS the table can exclude are those four — but the description of the rest of it was wrong, so it is corrected here rather than left to be re-derived (iss-2608301657350399).
- iss-2608300210588414intent ready reports a scope_conditions failure with a backfill remedy on shipped and superseded intents (18 shipped records), which spc-55's Out of scope forbids; and an untouched Mechanism scaffold line is reported as a stated mechanism claim, contradicting the plugin surface's line that the scaffold is not a claim. Detail strings on checks whose verdicts are already settled by the bucket check, so misleading output rather than a wrong gate.
- iss-2608301646042379the control character refusal claims no record field can hold the rune when DEL C1 and bidi all round trip through committed scalars
- itd-179The reasoning behind what was pursued no longer evaporates at the gate — readiness and triage record grounds for the conjecture, not only the decision