fix(cu): revalidate native keyboard targets

[hqhq1025]

Summary

• retain the clicked native editable field identity instead of reusing its old screen coordinate
• uniquely refetch the same AX field before set_value, so layout reflow cannot redirect text to another field
• fail closed when the original field is missing or ambiguous, and verify the write against a fresh identity match

Electron text identity is intentionally unchanged; stable DOM-local identity needs a separate protocol extension.

Verification

• built @maka/core, @maka/storage, and @maka/runtime serially
• npm --workspace @maka/computer-use test (129/129 passing)
• git diff --check

[Astro-Han]

Two P1 target-binding problems remain in the native text path:

• P1: The editable target is selected from a snapshot before the coordinate click. If layout changes before dispatch, the click can land elsewhere while keyboard ownership is still assigned to the pre-click field; subsequent text may be written to a field the user did not click.
• P1: role/label/value is not a stable AX identity. Re-resolution and post-write verification can bind to another matching field and cannot prove that the readback belongs to the node passed to set_value.
• P2: A successful write does not update the saved value, so retrying the same type operation is no longer idempotent.

Please establish ownership from the actual clicked/focused AX node and use a stable node identity through resolution, write, and readback. If the protocol cannot provide that identity, fail closed when the node changes.

[hqhq1025]

Superseded by #984, which consolidates #930-#933 into one target-identity boundary and addresses the requested changes. Stable AX token delivery is tracked in trycua/cua#2210.

[hqhq1025]

Summary

• retain the clicked native editable field identity instead of reusing its old screen coordinate
• uniquely refetch the same AX field before set_value, so layout reflow cannot redirect text to another field
• fail closed when the original field is missing or ambiguous, and verify the write against a fresh identity match

Electron text identity is intentionally unchanged; stable DOM-local identity needs a separate protocol extension.

Verification

• built @maka/core, @maka/storage, and @maka/runtime serially
• npm --workspace @maka/computer-use test (129/129 passing)
• git diff --check

[Astro-Han]

Two P1 target-binding problems remain in the native text path:

• P1: The editable target is selected from a snapshot before the coordinate click. If layout changes before dispatch, the click can land elsewhere while keyboard ownership is still assigned to the pre-click field; subsequent text may be written to a field the user did not click.
• P1: role/label/value is not a stable AX identity. Re-resolution and post-write verification can bind to another matching field and cannot prove that the readback belongs to the node passed to set_value.
• P2: A successful write does not update the saved value, so retrying the same type operation is no longer idempotent.

Please establish ownership from the actual clicked/focused AX node and use a stable node identity through resolution, write, and readback. If the protocol cannot provide that identity, fail closed when the node changes.

[hqhq1025]

Superseded by #984, which consolidates #930-#933 into one target-identity boundary and addresses the requested changes. Stable AX token delivery is tracked in trycua/cua#2210.

[hqhq1025]

Summary

• retain the clicked native editable field identity instead of reusing its old screen coordinate
• uniquely refetch the same AX field before set_value, so layout reflow cannot redirect text to another field
• fail closed when the original field is missing or ambiguous, and verify the write against a fresh identity match

Electron text identity is intentionally unchanged; stable DOM-local identity needs a separate protocol extension.

Verification

• built @maka/core, @maka/storage, and @maka/runtime serially
• npm --workspace @maka/computer-use test (129/129 passing)
• git diff --check

[Astro-Han]

Two P1 target-binding problems remain in the native text path:

• P1: The editable target is selected from a snapshot before the coordinate click. If layout changes before dispatch, the click can land elsewhere while keyboard ownership is still assigned to the pre-click field; subsequent text may be written to a field the user did not click.
• P1: role/label/value is not a stable AX identity. Re-resolution and post-write verification can bind to another matching field and cannot prove that the readback belongs to the node passed to set_value.
• P2: A successful write does not update the saved value, so retrying the same type operation is no longer idempotent.

Please establish ownership from the actual clicked/focused AX node and use a stable node identity through resolution, write, and readback. If the protocol cannot provide that identity, fail closed when the node changes.

[hqhq1025]

Superseded by #984, which consolidates #930-#933 into one target-identity boundary and addresses the requested changes. Stable AX token delivery is tracked in trycua/cua#2210.

[hqhq1025]

Summary

• retain the clicked native editable field identity instead of reusing its old screen coordinate
• uniquely refetch the same AX field before set_value, so layout reflow cannot redirect text to another field
• fail closed when the original field is missing or ambiguous, and verify the write against a fresh identity match

Electron text identity is intentionally unchanged; stable DOM-local identity needs a separate protocol extension.

Verification

• built @maka/core, @maka/storage, and @maka/runtime serially
• npm --workspace @maka/computer-use test (129/129 passing)
• git diff --check

[Astro-Han]

Two P1 target-binding problems remain in the native text path:

• P1: The editable target is selected from a snapshot before the coordinate click. If layout changes before dispatch, the click can land elsewhere while keyboard ownership is still assigned to the pre-click field; subsequent text may be written to a field the user did not click.
• P1: role/label/value is not a stable AX identity. Re-resolution and post-write verification can bind to another matching field and cannot prove that the readback belongs to the node passed to set_value.
• P2: A successful write does not update the saved value, so retrying the same type operation is no longer idempotent.

Please establish ownership from the actual clicked/focused AX node and use a stable node identity through resolution, write, and readback. If the protocol cannot provide that identity, fail closed when the node changes.

[hqhq1025]

Superseded by #984, which consolidates #930-#933 into one target-identity boundary and addresses the requested changes. Stable AX token delivery is tracked in trycua/cua#2210.

[hqhq1025]

Summary

• retain the clicked native editable field identity instead of reusing its old screen coordinate
• uniquely refetch the same AX field before set_value, so layout reflow cannot redirect text to another field
• fail closed when the original field is missing or ambiguous, and verify the write against a fresh identity match

Electron text identity is intentionally unchanged; stable DOM-local identity needs a separate protocol extension.

Verification

• built @maka/core, @maka/storage, and @maka/runtime serially
• npm --workspace @maka/computer-use test (129/129 passing)
• git diff --check

[Astro-Han]

Two P1 target-binding problems remain in the native text path:

• P1: The editable target is selected from a snapshot before the coordinate click. If layout changes before dispatch, the click can land elsewhere while keyboard ownership is still assigned to the pre-click field; subsequent text may be written to a field the user did not click.
• P1: role/label/value is not a stable AX identity. Re-resolution and post-write verification can bind to another matching field and cannot prove that the readback belongs to the node passed to set_value.
• P2: A successful write does not update the saved value, so retrying the same type operation is no longer idempotent.

Please establish ownership from the actual clicked/focused AX node and use a stable node identity through resolution, write, and readback. If the protocol cannot provide that identity, fail closed when the node changes.

[hqhq1025]

Superseded by #984, which consolidates #930-#933 into one target-identity boundary and addresses the requested changes. Stable AX token delivery is tracked in trycua/cua#2210.

[hqhq1025]

Summary

• retain the clicked native editable field identity instead of reusing its old screen coordinate
• uniquely refetch the same AX field before set_value, so layout reflow cannot redirect text to another field
• fail closed when the original field is missing or ambiguous, and verify the write against a fresh identity match

Electron text identity is intentionally unchanged; stable DOM-local identity needs a separate protocol extension.

Verification

• built @maka/core, @maka/storage, and @maka/runtime serially
• npm --workspace @maka/computer-use test (129/129 passing)
• git diff --check

[Astro-Han]

Two P1 target-binding problems remain in the native text path:

• P1: The editable target is selected from a snapshot before the coordinate click. If layout changes before dispatch, the click can land elsewhere while keyboard ownership is still assigned to the pre-click field; subsequent text may be written to a field the user did not click.
• P1: role/label/value is not a stable AX identity. Re-resolution and post-write verification can bind to another matching field and cannot prove that the readback belongs to the node passed to set_value.
• P2: A successful write does not update the saved value, so retrying the same type operation is no longer idempotent.

Please establish ownership from the actual clicked/focused AX node and use a stable node identity through resolution, write, and readback. If the protocol cannot provide that identity, fail closed when the node changes.

[hqhq1025]

Superseded by #984, which consolidates #930-#933 into one target-identity boundary and addresses the requested changes. Stable AX token delivery is tracked in trycua/cua#2210.

[hqhq1025]

Summary

• retain the clicked native editable field identity instead of reusing its old screen coordinate
• uniquely refetch the same AX field before set_value, so layout reflow cannot redirect text to another field
• fail closed when the original field is missing or ambiguous, and verify the write against a fresh identity match

Electron text identity is intentionally unchanged; stable DOM-local identity needs a separate protocol extension.

Verification

• built @maka/core, @maka/storage, and @maka/runtime serially
• npm --workspace @maka/computer-use test (129/129 passing)
• git diff --check

[Astro-Han]

Two P1 target-binding problems remain in the native text path:

• P1: The editable target is selected from a snapshot before the coordinate click. If layout changes before dispatch, the click can land elsewhere while keyboard ownership is still assigned to the pre-click field; subsequent text may be written to a field the user did not click.
• P1: role/label/value is not a stable AX identity. Re-resolution and post-write verification can bind to another matching field and cannot prove that the readback belongs to the node passed to set_value.
• P2: A successful write does not update the saved value, so retrying the same type operation is no longer idempotent.

Please establish ownership from the actual clicked/focused AX node and use a stable node identity through resolution, write, and readback. If the protocol cannot provide that identity, fail closed when the node changes.

[hqhq1025]

Superseded by #984, which consolidates #930-#933 into one target-identity boundary and addresses the requested changes. Stable AX token delivery is tracked in trycua/cua#2210.

[hqhq1025]

Summary

• retain the clicked native editable field identity instead of reusing its old screen coordinate
• uniquely refetch the same AX field before set_value, so layout reflow cannot redirect text to another field
• fail closed when the original field is missing or ambiguous, and verify the write against a fresh identity match

Electron text identity is intentionally unchanged; stable DOM-local identity needs a separate protocol extension.

Verification

• built @maka/core, @maka/storage, and @maka/runtime serially
• npm --workspace @maka/computer-use test (129/129 passing)
• git diff --check

[Astro-Han]

Two P1 target-binding problems remain in the native text path:

• P1: The editable target is selected from a snapshot before the coordinate click. If layout changes before dispatch, the click can land elsewhere while keyboard ownership is still assigned to the pre-click field; subsequent text may be written to a field the user did not click.
• P1: role/label/value is not a stable AX identity. Re-resolution and post-write verification can bind to another matching field and cannot prove that the readback belongs to the node passed to set_value.
• P2: A successful write does not update the saved value, so retrying the same type operation is no longer idempotent.

Please establish ownership from the actual clicked/focused AX node and use a stable node identity through resolution, write, and readback. If the protocol cannot provide that identity, fail closed when the node changes.

[hqhq1025]

Superseded by #984, which consolidates #930-#933 into one target-identity boundary and addresses the requested changes. Stable AX token delivery is tracked in trycua/cua#2210.