Cannot correctly enter float parameters

[mrexodia]

Describe the bug
You cannot correctly enter floats.

To Reproduce
Steps to reproduce the behavior:

1. Enter 1. as a parameter, the . will disappear you can never enter 1.5 or 1.0 (worse behavior than the bug in V1 It is not possible to enter 1.0 as a value #918)

Expected behavior
It should work.

Logs
N/A

Additional context
N/A

[cliffhall]

Triage: Priority = High

Scored 9/16 with the priority rubric added to AGENTS.md in #1891, as part of the backlog triage in #1872. Added to project board #28 with Status Incoming — meaning filed and scored but not yet approved for work. A maintainer decides whether it moves to Todo.

Axis	Score	Reasoning
Severity / impact	4/5	Float parameters can't be entered at all — the decimal point is swallowed — so any tool taking a non-integer number is uncallable from the UI. The reporter notes this is worse than the v1 behaviour.
Urgency / staleness	4/5	On the published v2, and it's a regression against v1 rather than a longstanding gap.
Signal bonuses	+1	bug label (+1)
Total	9	Lands in the High band (9-11).

Related issues. These look connected and may be worth reading together:

• Fix JSON parameter editor escaping while typing #1853 — the JSON editor escaping family this input surface belongs to
• Backspace recursively escapes JSON tool inputs #1856 — backspace variant
• JSON editor corrupts null values with cascading escape characters on nullable parameters #1885 — null-value variant
• It is not possible to enter 1.0 as a value #918 — the v1 predecessor (closed in the Triage the open issue backlog: backfill v1/v2 labels, close legacy, board the rest #1872 deprecation sweep) that this issue says v2 regressed past

Scores are a starting point, not a verdict — the rubric is meant to be overruled when it's plainly wrong, provided the reason is written down.