docs(788): two precision fixes in the vocabulary record
Build ErsatzTV Image / CI toolchain image resolves (pull_request) Successful in 6s
PR Gates / Docs update reminder (pull_request) Successful in 14s
Build ErsatzTV Image / Delimiter ban (release path) (pull_request) Successful in 20s
PR Gates / Fix proofs (Proves trailers) (pull_request) Successful in 15s
review-verdict/h10 Review-verdict: MERGEABLE @ e66196f (base: main)
PR Gates / decisions lifecycle (pull_request) Successful in 25s
PR Gates / CI image pin matches docker/ci (pull_request) Successful in 15s
Review verdict / Set review-verdict status (pull_request_target) Successful in 21s
PR Gates / Script lint and tests (ruff + pytest) (pull_request) Successful in 4m57s
Build ErsatzTV Image / Build & test (.NET) (pull_request) Successful in 8m53s
Build ErsatzTV Image / EF migration integrity (SQLite + MySql) (pull_request) Successful in 6m15s
Build ErsatzTV Image / Build & push image (amd64) (pull_request) Skipped
Build ErsatzTV Image / Functional E2E (curl + UI contracts) (pull_request) Successful in 5m50s
Build ErsatzTV Image / API docs in sync (OpenAPI + endpoint index) (pull_request) Successful in 7s
Build ErsatzTV Image / Formatting (changed .cs conform to .editorconfig) (pull_request) Successful in 6s
Build ErsatzTV Image / CI toolchain image resolves (pull_request) Successful in 6s
PR Gates / Docs update reminder (pull_request) Successful in 14s
Build ErsatzTV Image / Delimiter ban (release path) (pull_request) Successful in 20s
PR Gates / Fix proofs (Proves trailers) (pull_request) Successful in 15s
review-verdict/h10 Review-verdict: MERGEABLE @ e66196f (base: main)
PR Gates / decisions lifecycle (pull_request) Successful in 25s
PR Gates / CI image pin matches docker/ci (pull_request) Successful in 15s
Review verdict / Set review-verdict status (pull_request_target) Successful in 21s
PR Gates / Script lint and tests (ruff + pytest) (pull_request) Successful in 4m57s
Build ErsatzTV Image / Build & test (.NET) (pull_request) Successful in 8m53s
Build ErsatzTV Image / EF migration integrity (SQLite + MySql) (pull_request) Successful in 6m15s
Build ErsatzTV Image / Build & push image (amd64) (pull_request) Skipped
Build ErsatzTV Image / Functional E2E (curl + UI contracts) (pull_request) Successful in 5m50s
Build ErsatzTV Image / API docs in sync (OpenAPI + endpoint index) (pull_request) Successful in 7s
Build ErsatzTV Image / Formatting (changed .cs conform to .editorconfig) (pull_request) Successful in 6s
Round 5 returned MERGEABLE with no must-fix items. These are its two nits, taken
because this branch's failure mode has been imprecise prose and leaving a known
imprecision to save a round would be the same trade that produced the previous
five.
* The comma-separated enumeration the sweep cannot see is in the doc COMMENT
above `etv_verdict_words_display`, not inside it — the body builds its list
from the data. Verified: the comment is at review-verdict-vocabulary.sh:195,
the function opens at :198.
* The separator parenthetical omitted `\/`, which `(\\?[|/])` also accepts.
That was an understatement rather than an overclaim, and it is the one
direction this record can afford, but it is still not what the pattern does.
Verified by feeding `MERGEABLE\/APPROVED` to the pattern: it matches.
No executable line changed. The sweep still runs verbatim and still returns nine
real sites including the catalog; catalog regenerated; decisions-validate OK;
989 passed / 2 skipped.
Refs: #788
Decisions-Edit: yes
Co-authored-by: Timothy <timothy@noreply.gitea.tblindustries.be>
This commit is contained in:
@@ -104,11 +104,11 @@ done
|
||||
```
|
||||
|
||||
**This sweep is a starting point, not a completeness proof, and the difference is the whole lesson
|
||||
of this record.** It finds vocabulary words joined by a bare or markdown-escaped separator (`|`,
|
||||
`/`, `\|`). It does NOT find an enumeration written any other way — the comma-separated list inside
|
||||
`etv_verdict_words_display` is invisible to it, and so was the generated catalog until the `\\?` was
|
||||
added, because a Markdown table escapes its pipes. That omission was not hypothetical: the catalog
|
||||
is a site this record had just repaired, and the sweep reported it as clean.
|
||||
of this record.** It finds vocabulary words joined by a bare or markdown-escaped separator (`|`, `/`,
|
||||
`\|`, `\/`). It does NOT find an enumeration written any other way — the comma-separated list in the
|
||||
comment above `etv_verdict_words_display` is invisible to it, and so was the generated catalog until
|
||||
the `\\?` was added, because a Markdown table escapes its pipes. That omission was not hypothetical:
|
||||
the catalog is a site this record had just repaired, and the sweep reported it as clean.
|
||||
|
||||
Each earlier attempt at this — three counts, then a pattern — failed the same way, by asserting a
|
||||
completeness its author had not established. A string predicate over prose does not converge, which
|
||||
|
||||
Reference in New Issue
Block a user