Add context workflow identifier support

[nicfix]

Summary

• allow Purchases.configure to accept an optional context with a workflow identifier
• store the workflow identifier in EventsTracker and include it on emitted events
• update API report and tests for the new configuration surface

Testing

• npm run build
• npm run extract-api
• npm run test -- src/tests/behavioral-events/events-tracker.test.ts

---

Codex Task

[tonidero]

I'm just wondering if this should be a parameter for presentPaywall/purchase methods, instead of a configuration parameter... thoughts?

[elenaperezrioja]

So this will be passed when calling _trackEvent, right? which is good, but we're already passing it in the properties of the event.

We're not passing the workflow id when a purchase is happening so that we can access it in khepri after the transaction is created, right?

[tonidero]

As long as we make these APIs internal, this looks good! And also, I would consider renaming the PurchasesContext to PresentedWorkflowContext, so it's more concrete and similar to the PresentedOfferingContext that has a similar utility.

[nicfix]

What about:

  @internal
  context: { presentedWorflowContext: { workflowId}}

So that in the future we can extend the context and still have an object for the presentedWorkflowContext?

[tonidero]

What about:

  @internal
  context: { presentedWorflowContext: { workflowId}}

So that in the future we can extend the context and still have an object for the presentedWorkflowContext?

I like that!

[elenaperezrioja]

What about:

  @internal
  context: { presentedWorflowContext: { workflowId}}

So that in the future we can extend the context and still have an object for the presentedWorkflowContext?

That's great :) I can imagine needing to pass some additional info like workflowRevision at some point

[tonidero]

Makes sense! 🚢