feat: expand floating parameters

[rauhryan]

Motivation

Clay exposes more floating-element controls than clayterm previously made available through the TypeScript directive API. Higher-level UI code needs those controls for popovers, tooltips, modals, and attached floating surfaces without reaching through to renderer internals.

Approach

Expands the open(..., { floating }) surface to cover the currently needed Clay floating options:

• expand.{ width, height }
• structured attachPoints.{ element, parent }
• pointerCaptureMode
• clipTo
• zIndex

The public TypeScript API uses string literal values for enum-like options, while ops.ts privately maps those strings to Clay's numeric transfer representation during packing.

The root renderer spec documents the complete current floating shape, and tests cover packing/rendering plus validation of the new fields.

Alternate Designs

Considered exporting numeric constants that mirror Clay's C enums. That was rejected because it leaks implementation details into the public TypeScript surface. String literals better match the existing clayterm API style.

Possible Drawbacks or Risks

floating.parent remains a numeric parent id in this PR. Converting that to an element-id string would require an additional design pass around hashing and transfer encoding, so this PR keeps the scope focused on the enum-like floating controls.

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/clayterm@29

commit: ea34f5b

[cowboyd]

For some reason it looks like your agent isn't picking up the organization's PR template. Have a look at this one for an example.

#17

[cowboyd]

Remove current. The spec addresses what is.

[cowboyd]

Approved. Can you remove the references to current in the comment?