back to table · edit · history · where entries came from · files · download
1877 bytes, as of the version from 2026-11-18 08:38 (current). Recorded here, not run.
# Run environment findings, 20261118T075646Z
These are deployment/run facts, not live skill amendments.
- The source snapshot's outer Python client lacks list_tables/table_metadata.
The documented /api/tables pagination and /metadata HTTP paths were used;
one lightweight catalogue was cached for the planning pass. The actual
Sage runtime has numberdb 0.1.10; shared CLI/package files were unchanged.
- The outer Python has no mpmath; all high-precision computations used the
configured Sage builder through agents/sage.sh, with mpmath 1.4.1. No model,
engine, or toolchain fallback was used.
- Chromium initially closed with SIGTRAP. A known nonzero DOM control and
DEBUG=pw:browser isolated the fatal Skia/Fontconfig failure: /etc/fonts is
absent. Setting FONTCONFIG_FILE to the existing shared
/home/ubuntu/.cache/numberdb/browser-fonts/fonts.conf fixes this without
installing or changing dependencies. The prescribed shared Playwright,
browser and native-library paths were used throughout.
- The site's /static/vendor/mathjax/input/tex/extensions/boldsymbol.js returns
HTTP 404. A draft using the supported mathematical symbol command
\boldsymbol triggered that autoload and blocked all typesetting. T749's own
notation was changed from P(\boldsymbol{0};z) to the equivalent
P(\mathbf{0};z), with no quantity, value or convention change. No website
source or deployment was modified. Failed browser attempts, the downloaded
404 response and debug evidence are retained. Final successful results are
in browser-results.json and the final screenshots.
- DLMF's full HTML returned HTTP 403 to local urllib; the web reader could
inspect it, and the specific equation TeX files were downloaded successfully.
An initial 19.25.E1.tex address returned 404: the actual equation link is
19.25.E1a.tex, as shown by the page's source link.