osage imagemap (cmapx/imap) parity dashboard
Differential survey of @knowvah/dot-engine osage imagemap (cmapx/imap) output vs the native dot -K osage oracle (test/corpus/map-walk.ts), semantic comparison per docs/conformance.md (±0.01 deterministic tolerance, ±0.5 for the iterative engines). Regenerate: npx tsx test/corpus/map-walk.ts osage && npx tsx test/corpus/parity-report.ts.
Summary
- Surveyed: 762
- pass: 761 (99.9%) · diverged (tracked): 0 · accepted (documented, won't-fix): 1
- errors (oracle/port/timeout, excluded from scoring): 0
Diverged (0)
(none)
Accepted (1) — documented, not chased
| id | #diffs | firstDiff | reason |
|---|---|---|---|
graphs-xx | 1 | area[271].coords[2] | A8 rounding-boundary dust: 1 of 272 hotspot coords sits within the sub-0.01pt model tolerance of the integer rounding boundary (port 2654.5x vs native 2654.4x -> 2655 vs 2654); osage xdot track passes at 0.01. Irreducible print amplification. Journal 2026-07-24. |
Errors and timeouts (0)
(none)
Passing ids (761) are omitted for brevity — the full roster is in map-parity-osage.json.