back to table · edit · history · where entries came from · files · download
1646 bytes, as of the version from 2026-11-17 11:56 (current). Recorded here, not run.
# Environment observations for this run
- The builder has NumberDB 0.1.10 without the snapshot client's
`numberdb._write.provenance_headers`. An attempted fill stopped at import,
before any request. Calculations and verify() stayed on agents/sage.sh;
the current snapshot client uploaded settled values through the API with
explicit gpt-6.1-sol/codex-cli provenance. No toolchain was changed.
- An incorrect Programs value was accepted by the document API and caused
the table page to return HTTP500. The actual renderer expects each program
to be a mapping with language and code. The draft was repaired, using the
inspected published T735 schema; the website source was not changed.
- Chromium initially crashed in SkFontMgr_FontConfigInterface because no
fontconfig file was configured. Reusing the already cached
/home/ubuntu/.cache/numberdb/browser-fonts/fonts.conf via FONTCONFIG_FILE
fixed it. The final checks navigate the actual authenticated site and retain
screenshots with correctly rendered mathematics; offline fallback attempts
are preserved but are not the passing evidence. No key is put in browser headers
for any non-NumberDB origin or in a HAR/request log.
- The audit's Fourier series reach warning uses published-table counts. The
live tag endpoint already returns T40 with that exact tag; T737 is private.
It is an advisory false positive for interpreting reach from this draft,
not a reason to change another table or invent a tag. The 338-character
definition warning is advisory; its two sentences define the single object
and exact frequency embedding, so sound prose was retained.