Kjell Tore Guttormsen
47905dacae
Closes the gap STATE has been carrying since e1511f9. Section 1.1's runtime
behaviour has been correct since then -- the third verdict is real, the
declared set is one constant with two uses -- but what we PUBLISHED was a
console.log summary: the right facts in a format only its author could
parse, which is most of what section 1.1 exists to prevent. Commons
shipped a shape for it in v0.3.0
(schema/conformance-declaration.schema.json 0.1.0), so the artifact can
now exist.
Every field is counted from the run rather than restated. The cases record
their own verdict as they execute, keeping `failed` (ran and disagreed)
apart from `error` (could not run) on exactly the distinction section 1
turns on. `commons_commit` is read out of the subtree-pull subject in our
own history rather than transcribed into a constant that would drift at
the next pull, and it refuses to publish a coordinate it cannot determine
-- a fabricated commit is worse than no declaration. The artifact is
gitignored: a committed declaration keeps asserting what was true once,
and nothing makes it wrong out loud when it stops being.
Validated once against the vendored schema with a real 2020-12
implementation: VALID, and the validator proven discriminating by six
negative controls it rejected (dropped zero-count, unknown key,
out-of-enum source, non-integer count, missing enumeration, malformed
case id). Continuous validation would mean a Python dependency in a suite
that has none, so what stays is the cheap half that actually drifts -- the
two key sets, asserted exactly.
TWO DEFECTS FOUND BY MUTATING THIS GATE, both in its own first draft:
1. It lived in `after()`. Measured on Node 25.8.2: an assertion that fails
in an after hook prints under "failing tests" and marks the suite red,
but leaves `fail 0` and exit code ZERO. `npm test` and CI would have
read a falsified declaration as green. The gate against "reports
success without running" was itself reporting success without running.
It is now a test, declared last, and the verdict-count assertion is
what guards the ordering that makes "last" meaningful.
2. Nothing tied the PUBLISHED `declared_tables` to the runner's constant.
Substituting a literal list left every other assertion green, because
they all read the constant rather than what was published -- so
`declaration_source: derived-from-runner` could be a lie with no code
change to point at. Now asserted identical.
Seven mutations, all exiting non-zero: dropped zero-count, falsified
not_applicable, unpublished field, hand-maintained tables, lied-about
source, and a hardcoded `passed` combined with a genuine case failure.
Published this run: 90 total, 84 passed, 0 failed, 6 not-applicable,
0 error, at commons 4641a7b (v0.3.0). Full suite 2192 pass / 0 fail /
6 skipped.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017XDdiKC9ZXmcSUQ2m84s6y
38 lines
961 B
Text
38 lines
961 B
Text
node_modules/
|
|
.DS_Store
|
|
coverage/
|
|
harness-events.jsonl
|
|
*.log
|
|
reports/baselines/*.json
|
|
reports/watch/config.json
|
|
reports/watch/latest.json
|
|
# spec §1.1 conformance declaration — regenerated by every corpus run, so it
|
|
# cannot outlive (and misreport) the measurement that produced it
|
|
reports/conformance-declaration.json
|
|
.env
|
|
.env.*
|
|
*.key
|
|
*.pem
|
|
credentials.*
|
|
secrets.*
|
|
.local/
|
|
HANDOFF-FINDINGS.local.md
|
|
|
|
# --- session/local state ---
|
|
# STATE.md is LOCAL-ONLY here: llm-security has a public remote (open/llm-security),
|
|
# and the global ~/.claude/CLAUDE.md convention is public remote => gitignored.
|
|
# Untracked 2026-08-01 (org-ops finding) after being tracked since project start;
|
|
# git history keeps the old commits, this only stops future ones.
|
|
STATE.md
|
|
REMEMBER.md
|
|
ROADMAP.md
|
|
TODO.md
|
|
NEXT-SESSION-PROMPT*.local.md
|
|
*.local.md
|
|
*.local.json
|
|
*.local.sh
|
|
.DS_Store
|
|
.claude/
|
|
|
|
# Voyage-generated plan annotation HTML (regenerable via annotate.mjs)
|
|
docs/plans/*.html
|