feat(tools): onParameterParseFailure teardown boundary (split 4/6 of #1066)

[easonLiangWorldedtech]

U3 — onParameterParseFailure teardown boundary

Part of the PR Zoo-Code-Org#1066 split (tracking issue Zoo-Code-Org#703) split (content source of record: 72143527fd33306e5541116093c2cbf803cce9e0..pr-1066-audit).

Why this unit exists: BaseTool.onParameterParseFailure() teardown boundary plus the WriteToFileTool override, so a truncated final block still finalizes the open partial ask.

Boundaries

• base: feedc5dafbf4
• head: e2a03d949257
• content source: 72143527fd33306e5541116093c2cbf803cce9e0..pr-1066-audit (local)

Fidelity (machine-verified)

zdt split verify --contract U3.json --worktree <wt> --head e2a03d949257

Result: PASS — standalone 253 a+d / 3 files (UNDER-SOFT)

• src/core/tools/BaseTool.ts: OK (content subset of source)
• src/core/tools/WriteToFileTool.ts: OK (content subset of source)
• src/core/tools/__tests__/writeToFileTool.spec.ts: OK (content subset of source)

Design contract

• issue: [BUG] Agent loop stalls permanently when write_to_file partial streaming hits a filesystem error (EROFS/EACCES) Zoo-Code-Org/Zoo-Code#703

Verification (this unit, as pushed)

• Tests: 243 passed / 5 skipped
• changed-line coverage: 20 covered / 0 uncovered — PASS
• ESLint: clean on every touched file; suppression counts unchanged
• No .changeset file, no CHANGELOG edit.

Recreate policy

If the bot stalls on a pre-merge check and the existing head cannot obtain bot review/approval (empty-commit re-trigger attempted and failed), the unit is recreated from the tagged content source of record — never from a per-PR head. At most 1 PR per issue.

[easonLiangWorldedtech]

Moved to the upstream repo (base = main); the split chain is tracked in Zoo-Code-Org#703.