Bound native group-key generation and wrapping allocations

[iFixRobots]

Releasing the generated registration key is not enough to stop native allocation growth. A local 1,000-iteration generate/wrap/destroy run grew the authoritative heap from 6,352 to 1,198,696 live bytes. Generation/destruction alone grew it to 198,392 bytes.

Run the complete registration batch on the existing disposable crypto snapshot instead: generate one group key, wrap that same key for all recipients, and return only copied ciphertext bytes. Mark the snapshot dirty after every batch, including errors and panics. No temporary native key pointer is published in the session heap, and no destructor runs on a damaged snapshot.

The real Manager takes this batch path. Existing fake/legacy Generate/Wrap/Release callers remain compatible; their native generation path is not made leak-free by this change. Existing single-key wrapping also uses the disposable snapshot. Shadow aborts return an error without quarantining the healthy authoritative heap; authoritative channel-creation aborts still quarantine it.

[indent]

Issues

No issues found.

CI Checks

All CI checks passed on 9fb4867.

Review agents

Select any unchecked box below to run or rerun that agent.

Passed (1)

• Indent Review Agent · Rebase only; PR changes are identical and still work with the base connector changes. No bugs found.

Full results

Indent Review Agent

• Summary: Rebase only; PR changes are identical and still work with the base connector changes. No bugs found.
• Last ran on commit: 9fb48676
• Latest result

  {
    "summary": "Rebase only; PR changes are identical and still work with the base connector changes. No bugs found.",
    "findings": []
  }