Files
sim/apps
Waleed c9aed7af99 fix(jsm): accept the numeric pagination the JSM tools actually send (#6386)
* fix(jsm): accept the numeric pagination the JSM tools actually send

The JSM tools declare start/limit as type: 'number' and the block coerces
Max Results with Number.parseInt, but every /api/tools/jsm/* contract typed
them as z.string(). Any JSM read with pagination filled in 400'd before
reaching Atlassian, and get_queues 400'd unconditionally because the block
always sends includeCount as a boolean.

Normalize both shapes at the contract boundary, add the missing Start Index
block input, and route Max Results through the existing toOptionalInt helper
so a non-numeric entry no longer sends NaN.

* improvement(forking): widen the fork mapping target picker further

320px still clipped the longest secret keys the picker shows.

* fix(jsm): cap pagination at the documented int32 maximum

Addresses review: the schema claimed the int32 range but only floored at 0,
so values above 2147483647 were forwarded to Atlassian instead of being
rejected at Sim's boundary. Also restores the const tuple for the paginated
operation list and drops the widened ToolConfig from the test table.
2026-08-07 12:40:20 -07:00
..