Add clear-then-type field entry (Playwright fill idiom)

[JE-Chen]

Summary

Round-11, automation-core. Setting a field reliably means clearing it first then entering the new text. The framework has write (raises on emoji/CJK) and set_clipboard/hotkey separately, but no single "focus → clear → set value" primitive and no paste strategy for Unicode write can't type.

Layers

• Headless core: je_auto_control/utils/field_entry/field_entry.py — plan_field_set (pure op-plan), set_field_text (dispatch via injectable sink). clear select_all/none; paste=True enters text via clipboard (Unicode/emoji/CJK-safe); modifier ctrl/command. No PySide6.
• Facade: both re-exported + __all__.
• Executor: AC_set_field_text.
• MCP: ac_set_field_text (SIDE_EFFECT_ONLY).
• Script Builder: one CommandSpec under Keyboard.

Tests / docs

• test/unit_test/headless/test_field_entry_batch.py — 9 headless tests (default clear+type plan, paste plan, clear=none, macOS modifier, unknown-clear ValueError, sink dispatch + wiring + facade). Dispatch tested via injected sink (no real input).
• EN/Zh feature docs v117_features_doc.rst + toctrees; 3 WHATS_NEW changelog entries.

Note: Codacy may show action_required from its coverage gate only (issues=0); SonarCloud + all GitHub Actions are the substantive gates.

[codacy-production]

Not up to standards ⛔

_{NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud