fix(transaction-controller): use provided batchId in hook batches

[matthewwalsh0]

Explanation

• What is the current state of things and why does it need to change?
  The addTransactionBatchWithHook function in the TransactionController was always generating a new batchId, even when a batchId was explicitly provided in the userRequest. This meant that the provided batchId was ignored when processing a batch through the publish batch hook route.
• What is the solution your changes offer and how does it work?
  This change modifies addTransactionBatchWithHook to check for a batchId in the userRequest (via batchIdOverride) and use it if present. If no batchId is provided, it falls back to generating a new one, aligning its behavior with addTransactionBatchWith7702.
• Are there any changes whose purpose might not obvious to those unfamiliar with the domain?
  No.

References

Checklist

• I've updated the test suite for new or updated code as appropriate
• I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate
• I've communicated my changes to consumers by updating changelogs for packages I've changed
• I've introduced breaking changes in this PR and have prepared draft pull requests for clients and consumer packages to resolve them

---

 

---

Note

Fix: batch ID propagation in hook path

• addTransactionBatch (hook route) now uses request.batchId if provided, falling back to a generated ID (batch.ts)
• Adds tests verifying returned batchId and propagation to nested addTransaction calls when using publishBatchHook (batch.test.ts)
• Updates changelog entry under Fixed noting the behavior change

^{Written by Cursor Bugbot for commit 84c0534. This will update automatically on new commits. Configure here.}

[cursor]

Cursor Agent can help with this pull request. Just @cursor in comments and I'll start working on changes in this branch.
_{Learn more about Cursor Agents}