Chris Tsang 74da0efb84 Uncap watershed detail in the Node binding + sync docs ...

`6f163fc` widened watershed_detail from u8 to u32 in the core, CLI, and
Python binding but not the Node/wasm binding, which still assigned a u8 to
config.watershed_detail — a wasm build error (E0308). Widen the Node
Options field to u32 and refresh every "0..=255" watershed doc (CLI help,
Config field, .pyi, index.d.ts, and all three READMEs) to reflect that the
level is now uncapped (default 128; higher = more regions).

2026-08-08 21:50:55 +01:00

..

vtracer

Uncap watershed detail in the Node binding + sync docs

2026-08-08 21:50:55 +01:00

vtracer-bench

add vtracer-bench

2026-08-01 01:44:23 +01:00

vtracer-cli

Uncap watershed detail in the Node binding + sync docs

2026-08-08 21:50:55 +01:00

vtracer-py

Uncap watershed detail in the Node binding + sync docs

2026-08-08 21:50:55 +01:00