Compatibility and tested scope

The application uses the frozen engine 1.0.0, a behavior-preserving port of WORDS 1.99.0 at commit 1f2f0fb0867a896d7b9284a03d615ed635d6f992. Version 1.0.2 adds English passage lookup in the browser. The engine release manifest still fixes all 28 engine, data and adapter paths. The comparison profile is upstream-tests-v1.

Engine qualification

CheckRecorded result
Complete Latin replay4,144,877 inputs; 4,144,873 matching normal outputs
Native Latin errors2 matching failures: pilarium, pilarivm
Console comparator exclusions2: empty input and the ! developer menu
Unexplained differences and regressions0
English index and input probes24,000 matching observations, including 5 native failure outcomes
Boolean option combinations4,096
Ordered sessions2,048
Input and failure boundaries454 comparable sessions match; 2 single-lookup boundaries recorded separately
Original executable fixtures21 raw cases, including the five upstream regression groups
Expanded portable corpus3,953 frozen observations

These are the final 1.0 engine results, retained by the immutable manifests and fixtures. Application patch tests are described in their own release notes. Matching failures are not successful lookups, and matching unknown results do not measure dictionary coverage. Historical 0.2 differences were resolved before stable 1.0; they are not current failures.

Comparison contract

Reference comparisons remove terminal prompts and frame-edge/trailing whitespace under the declared runner. They preserve internal blank lines, token order, candidate multiplicity, morphology, meanings, flags, explanations and errors. The 21 raw baseline fixtures separately retain exact stdout, stderr and process state. Expected fixtures are not replaced by outputs of this port.

Browser macron adaptation, English passage batching, grouping and dictionary-frequency ordering operate outside the legacy engine contract. Original text and structured data retain engine results. See the browser guide, API and CLI, build instructions and legacy contract.

Retained behavior and limits

npm run verify checks source/data locks, the frozen backend and the portable regression suite. The 1.0 release record identifies its browser, recovery, offline and migration coverage. Automated browser testing does not claim physical-device installation testing.

Reproduce the full wordlist comparison

With the pinned Ada reference and an immutable classical-lexical-test-data release containing its manifest and four gzip lists:

node --max-old-space-size=8192 scripts/acceptance.mjs \
  --data /path/to/data --oracle /path/to/oracle --out /path/to/results --workers 6

The runner verifies input identities and preserves per-profile membership, ordered output hashes, differences, failures and resumable checkpoints. Reuse requires the same engine, input and runner identities. A zero process exit means the run completed; its comparison counters determine the result.