Chinesezjc 2cb0dddb40 docs(tools): stop over-quantifying what String does to a big integral double ...

The pyScalar paragraph read as a universal over every beyond-safe-range
integral number, and three of its clauses have counterexamples inside
that very domain: String(2 ** 53) and String(1e20) are byte-identical to
BigInt's digits, so the "different integer or no integer literal at all"
split is not exhaustive, "the 16 digits" is 2 ** 60's instance count
rather than the mechanism (shortest round-trip is 1 to 17 significant
digits), and padded digits do name a held integer for 1e20. Say shortest
decimal string then padded to the exponent, give both counts, condition
the no-double-holds-it clause, and state the invariant that makes the
rule unconditional: where String is already exact the two agree, and
where it is not, BigInt is the exact one.

Also align one README.zh.md term: the same file already translates
"exotic names" as 特殊名称 in the SDK-section bullet.

2026-08-05 20:06:06 +08:00

..

code-mode.ts

fix(tools): attach Python SDK docstrings to their own methods

2026-08-05 14:02:47 +08:00

index.ts

fix(tools): name the two bound SDK names and escape NEL

2026-08-05 17:45:38 +08:00

invariant.ts

…

json-schema.ts

…

presentation.ts

Merge remote-tracking branch 'origin/master' into feat/search-presenter

2026-07-31 14:40:29 +08:00

py-types.ts

docs(tools): stop over-quantifying what String does to a big integral double

2026-08-05 20:06:06 +08:00

schema.ts

…

testing.ts

…

ts-types.ts

…