lessons-proposed.md

back to table · edit · history · where entries came from · files · download

1692 bytes, as of the version from 2026-11-16 11:10 (current). Recorded here, not run.

# Contributor lessons proposed by this build, not promoted to the skill

## Check the exact-zero case in a stored-interval parser
What happened: the companion identity checker parsed the literal `0` using a
decimal-last-place rule, giving [-1,1]. T665's exact zero real components then
produced huge propagated residual intervals. The checker, not either table,
was wrong. Its corrected parser treats plain integer strings as exact, and
controls now require exact zero and rejection of an imaginary-only perturbation
in the exactly real period rows. All 165 companion identities then passed.
What the skill says now: plain integers are exact; decimals denote intervals.
What it should say: a small executable parser-control example should cover both
the literal zero and a decimal zero such as `0.0`, which have different meanings.
Evidence: companion-parser-failure.json, corrected check_periods.py,
companion-results.json and stored-check-results.json for T722.

## Do not assume a NumberDB read-back preserves flat storage shape
What happened: a flat `Numbers` list submitted to T722 was returned by
numberdb.table as nested n/d/a dictionaries. A checker assuming a flat list
failed before numerical comparison. The generator's native verify() already
handled that representation and reported 226/226 matches.
What the skill says now: numberdb.table returns a full document, not a URL.
What it should say: code consuming the full document must support the documented
nested and flat Numbers forms, or use the maintained flattening/client helpers.
Evidence: stored.json, stored-check-results.json, verify.log and records_from()
in check_periods.py. No website or client source was changed.