bench/limits-search.ts <url> runs the limits search per joint against the fake bus or a given arm server and prints a before/after table a person can paste on #439 #505

bench/limits-search.ts runs the limits search per joint, against the fake bus or a given arm URL. It prints a before/after table you can paste on #439. Software/README.md has a short entry for it. The code was already on this branch from the earlier attempt. This push adds no new code, only a merge of current main.

The earlier preview deploy failed, most likely because of main's own broken node-loads test. main fixed that in commit 1773519, which this merge brings in. I haven't confirmed that was the cause, since I never saw the failed deploy's log.

The bench and limits-search tests pass (26 pass, 0 fail). The type check reports errors, but they are in other files (src/ui/zone-notes.js, src/visitor-counts.ts); none mention the limits-search files.

I did not run the whole bun test suite, as the forge runs that on push. I did not run the search end to end against the fake bus or a live arm, so the table output itself is unchecked beyond the tests.

Closes #495

bench/limits-search.ts runs the limits search per joint, against the fake bus or a given arm URL. It prints a before/after table you can paste on #439. Software/README.md has a short entry for it. The code was already on this branch from the earlier attempt. This push adds no new code, only a merge of current main.

The earlier preview deploy failed, most likely because of main's own broken node-loads test. main fixed that in commit 1773519, which this merge brings in. I haven't confirmed that was the cause, since I never saw the failed deploy's log.

The bench and limits-search tests pass (26 pass, 0 fail). The type check reports errors, but they are in other files (src/ui/zone-notes.js, src/visitor-counts.ts); none mention the limits-search files.

I did not run the whole bun test suite, as the forge runs that on push. I did not run the search end to end against the fake bus or a live arm, so the table output itself is unchecked beyond the tests.

Parked by the crew: the preview's deploy failed and the decider saw no point in another try