[Nexus] Migrate event definition tests from HSM to CHASM#9597

Merged

gow merged 14 commits intonexus/hsm-to-chasm-migrationfrom

cg/nexus/history_events_registry_4

Mar 26, 2026

Contributor

gow commented Mar 20, 2026 •

edited by cursor bot

Loading

What changed?

Migrating all the event definition's Apply() method from HSM to CHASM. Also migrated unit tests.

Why?

HSM to CHASM migration

How did you test it?

Note

Medium Risk
Changes Nexus operation lifecycle handling by moving scheduling/cancellation and terminal event application into CHASM event definitions and adjusting state transition semantics; regressions could affect operation task emission, cancellation timing, and cleanup during replay/reset.

Overview
Implements CHASM-based Nexus operation event Apply() handlers: scheduled/cancel-requested/started now create or update the in-memory operation component (including spawning/scheduling a cancellation child once an operation token exists), and terminal events (completed/failed/canceled/timed-out) transition the operation then remove it from the workflow.

Refactors workflow Nexus operation storage to be keyed by ScheduledEventId (int64), simplifies command handlers to only emit history events (letting event definitions create/update components), and expands cancellation/operation state machines with concrete task emission and retry/backoff metadata. Updates chasm.Transition.Apply to run transition logic before mutating state (enabling source-state inspection) and adds new CHASM-focused unit tests for the migrated event definitions and updated transition behavior.

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

gow requested review from a team as code owners

March 20, 2026 05:05

gow force-pushed the cg/nexus/history_events_registry_4 branch from 56ab33a to 4f251ef Compare

March 20, 2026 05:07

cursor bot reviewed

View reviewed changes

chasm/lib/nexusoperation/workflow/events_test.go Show resolved Hide resolved

gow force-pushed the cg/nexus/history_events_registry_3 branch from 28694e4 to 2d24633 Compare

March 23, 2026 22:15

Base automatically changed from cg/nexus/history_events_registry_3 to nexus/hsm-to-chasm-migration

March 24, 2026 03:36

gow force-pushed the nexus/hsm-to-chasm-migration branch from f30fdd3 to 52e97cd Compare

March 24, 2026 03:45

gow requested review from a team as code owners

March 24, 2026 03:45

gow force-pushed the nexus/hsm-to-chasm-migration branch from 52e97cd to 447bbda Compare

March 24, 2026 06:06

gow force-pushed the cg/nexus/history_events_registry_4 branch from 4f251ef to 8a4616e Compare

March 24, 2026 06:06

cursor bot reviewed

View reviewed changes

cursor bot left a comment

Cursor Bugbot has reviewed your changes and found 1 potential issue.

There are 2 total unresolved issues (including 1 from previous review).

chasm/lib/nexusoperation/cancellation_statemachine.go Show resolved Hide resolved

gow force-pushed the cg/nexus/history_events_registry_4 branch from 8a4616e to 9c03b67 Compare

March 24, 2026 06:14

gow requested review from bergundy and stephanos

March 24, 2026 06:15

bergundy reviewed

View reviewed changes

Member

bergundy left a comment

This looks mostly good to me.

chasm/lib/nexusoperation/workflow/events.go Outdated

+              	key := strconv.FormatInt(scheduledEventID, 10)
+              	field, ok := wf.Operations[key]
+              	if !ok {
+              		return nil, "", fmt.Errorf("nexus operation not found for scheduled event ID %d", scheduledEventID)

Member

bergundy Mar 24, 2026

This should be a not found service error or something else that we can safely handle.

Contributor Author

gow Mar 25, 2026

Done.

chasm/lib/nexusoperation/workflow/events.go Outdated

+              	scheduledEventID int64,
+              ) (*nexusoperation.Operation, string, error) {
+              	key := strconv.FormatInt(scheduledEventID, 10)
+              	field, ok := wf.Operations[key]

Member

bergundy Mar 24, 2026

Operations should be a map of int64 to Operation, no need to do this formatting.

Contributor Author

gow Mar 25, 2026

Done.

chasm/lib/nexusoperation/workflow/events.go Outdated

+              	attrs := event.GetNexusOperationScheduledEventAttributes()
+              	scheduledTime := event.GetEventTime()
+              	if scheduledTime == nil {

Member

bergundy Mar 24, 2026

Is this ever going to be nil?

Contributor Author

gow Mar 24, 2026

I don't think so. except maybe in some tests where we hand construct events. This check is not needed removed it.

chasm/lib/nexusoperation/workflow/events.go Outdated

               	return chasmworkflow.ErrEventNotCherryPickable
               }
+              // CancelRequestedEventDefinition

Member

bergundy Mar 24, 2026

I like having docstrings on every exported member but this doesn't really do anything.

chasm/lib/nexusoperation/workflow/events.go

+              	}
+              	cancellation, ok := op.Cancellation.TryGet(ctx)
+              	if !ok {

Member

bergundy Mar 24, 2026

I think this is never expected because how would a cancelation request be submitted without a cancelation state machine?

Contributor Author

gow Mar 25, 2026

I added this just defensively. But could this happen in the event of data corruption?

chasm/lib/nexusoperation/workflow/events.go

+              	}
+              	if err := nexusoperation.TransitionStarted.Apply(op, ctx, nexusoperation.EventStarted{
+              		OperationToken: attrs.GetOperationToken(),

Member

bergundy Mar 24, 2026

We're going to need to store the links here for standalone.

Contributor Author

gow Mar 25, 2026

Added a TODO

chasm/lib/nexusoperation/workflow/events.go

    
              		return err

              	}

              	if err := nexusoperation.TransitionSucceeded.Apply(op, ctx, nexusoperation.EventSucceeded{}); err != nil {

Member

bergundy Mar 24, 2026

We're going to need more information here for standalone but we can handle that later.

chasm/lib/nexusoperation/workflow/events.go Outdated

               }
+              // getOperation looks up a Nexus operation from the workflow by its scheduled event ID.
+              func getOperation(

Member

bergundy Mar 24, 2026

You wouldn't need this function if we used a map of int64 to Operation as I've mentioned before to represent the operations in the workflow.

Contributor Author

gow Mar 25, 2026

Done.

chasm/lib/nexusoperation/workflow/events_test.go Outdated

+              }
+              func TestCancelRequestCompletedEventDefinitionApply(t *testing.T) {
+              	t.Run("transitions cancellation to succeeded", func(t *testing.T) {

Member

bergundy Mar 24, 2026

Do we need a separate subtest here?

Contributor Author

gow Mar 25, 2026

No. Removed it (here and in few other tests)

chasm/lib/nexusoperation/cancellation_statemachine.go Outdated

               	nexusoperationpb.CANCELLATION_STATUS_BACKING_OFF,
               	func(c *Cancellation, ctx chasm.MutableContext, event EventCancellationAttemptFailed) error {
-              		return serviceerror.NewUnimplemented("unimplemented")
+              		// TODO: implement backing off logic similar to operation's transitionAttemptFailed

Member

bergundy Mar 24, 2026

Why the TODO?

Contributor Author

gow Mar 25, 2026

Was thinking of doing it along with cancellation executors.
Migrated it from HSM

gow force-pushed the nexus/hsm-to-chasm-migration branch from 447bbda to 3bd0557 Compare

March 25, 2026 21:10

gow force-pushed the cg/nexus/history_events_registry_4 branch from d14344b to 18f14c3 Compare

March 25, 2026 21:11

gow force-pushed the nexus/hsm-to-chasm-migration branch from 3bd0557 to 66234d5 Compare

March 26, 2026 06:09

gow requested a review from a team as a code owner

March 26, 2026 06:09

gow added 10 commits

March 25, 2026 23:09


          TODO

4e0f821


          Implement OperationStore interface in Operation

e5d9971


          Implement OperationStore interface in workflow component

9660e52


          Handle errors

2f7624a


          Inject event registry

39b7718

nit

c42329f


          Migrate eventdefinition.Apply from HSM to CHASM

9e26c4b


          Migrate event definition tests from HSM to CHASM

59d30ca


          Fix lint error


          Use service errors

ec5ec8d

gow added 4 commits

March 25, 2026 23:09


          Remove the strconv stuff

e51f682


          Address review feedback

99143a3


          Call apply() function before transitioning to the new state

fa67ba3


          Fix review feedback

c0f4e55

gow force-pushed the cg/nexus/history_events_registry_4 branch from 18f14c3 to c0f4e55 Compare

March 26, 2026 06:11

gow merged commit 7c63225 into nexus/hsm-to-chasm-migration

47 checks passed

gow deleted the cg/nexus/history_events_registry_4 branch

March 26, 2026 16:59

gow added a commit that referenced this pull request


          [Nexus] Migrate event definition tests from HSM to CHASM (#9597)

97bffef

## What changed?
Migrating all the event definition's `Apply()` method from HSM to CHASM.
Also migrated unit tests.

## Why?
HSM to CHASM migration

## How did you test it?
- [x] built
- [ ] run locally and tested manually
- [x] covered by existing tests
- [ ] added new unit test(s)
- [ ] added new functional test(s)


<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> **Medium Risk**
> Changes Nexus operation lifecycle handling by moving
scheduling/cancellation and terminal event application into CHASM event
definitions and adjusting state transition semantics; regressions could
affect operation task emission, cancellation timing, and cleanup during
replay/reset.
> 
> **Overview**
> Implements CHASM-based Nexus operation event `Apply()` handlers:
scheduled/cancel-requested/started now create or update the in-memory
operation component (including spawning/scheduling a cancellation child
once an operation token exists), and terminal events
(completed/failed/canceled/timed-out) transition the operation then
remove it from the workflow.
> 
> Refactors workflow Nexus operation storage to be keyed by
`ScheduledEventId` (`int64`), simplifies command handlers to only emit
history events (letting event definitions create/update components), and
expands cancellation/operation state machines with concrete task
emission and retry/backoff metadata. Updates `chasm.Transition.Apply` to
run transition logic before mutating state (enabling source-state
inspection) and adds new CHASM-focused unit tests for the migrated event
definitions and updated transition behavior.
> 
> <sup>Written by [Cursor
Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit
c0f4e55. This will update automatically
on new commits. Configure
[here](https://cursor.com/dashboard?tab=bugbot).</sup>
<!-- /CURSOR_SUMMARY -->

gow added a commit that referenced this pull request


          [Nexus] Migrate event definition tests from HSM to CHASM (#9597)

7fc816e

## What changed?
Migrating all the event definition's `Apply()` method from HSM to CHASM.
Also migrated unit tests.

## Why?
HSM to CHASM migration

## How did you test it?
- [x] built
- [ ] run locally and tested manually
- [x] covered by existing tests
- [ ] added new unit test(s)
- [ ] added new functional test(s)


<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> **Medium Risk**
> Changes Nexus operation lifecycle handling by moving
scheduling/cancellation and terminal event application into CHASM event
definitions and adjusting state transition semantics; regressions could
affect operation task emission, cancellation timing, and cleanup during
replay/reset.
> 
> **Overview**
> Implements CHASM-based Nexus operation event `Apply()` handlers:
scheduled/cancel-requested/started now create or update the in-memory
operation component (including spawning/scheduling a cancellation child
once an operation token exists), and terminal events
(completed/failed/canceled/timed-out) transition the operation then
remove it from the workflow.
> 
> Refactors workflow Nexus operation storage to be keyed by
`ScheduledEventId` (`int64`), simplifies command handlers to only emit
history events (letting event definitions create/update components), and
expands cancellation/operation state machines with concrete task
emission and retry/backoff metadata. Updates `chasm.Transition.Apply` to
run transition logic before mutating state (enabling source-state
inspection) and adds new CHASM-focused unit tests for the migrated event
definitions and updated transition behavior.
> 
> <sup>Written by [Cursor
Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit
c0f4e55. This will update automatically
on new commits. Configure
[here](https://cursor.com/dashboard?tab=bugbot).</sup>
<!-- /CURSOR_SUMMARY -->

gow added a commit that referenced this pull request


          [Nexus] Migrate event definition tests from HSM to CHASM (#9597)

577ea95

## What changed?
Migrating all the event definition's `Apply()` method from HSM to CHASM.
Also migrated unit tests.

## Why?
HSM to CHASM migration

## How did you test it?
- [x] built
- [ ] run locally and tested manually
- [x] covered by existing tests
- [ ] added new unit test(s)
- [ ] added new functional test(s)


<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> **Medium Risk**
> Changes Nexus operation lifecycle handling by moving
scheduling/cancellation and terminal event application into CHASM event
definitions and adjusting state transition semantics; regressions could
affect operation task emission, cancellation timing, and cleanup during
replay/reset.
> 
> **Overview**
> Implements CHASM-based Nexus operation event `Apply()` handlers:
scheduled/cancel-requested/started now create or update the in-memory
operation component (including spawning/scheduling a cancellation child
once an operation token exists), and terminal events
(completed/failed/canceled/timed-out) transition the operation then
remove it from the workflow.
> 
> Refactors workflow Nexus operation storage to be keyed by
`ScheduledEventId` (`int64`), simplifies command handlers to only emit
history events (letting event definitions create/update components), and
expands cancellation/operation state machines with concrete task
emission and retry/backoff metadata. Updates `chasm.Transition.Apply` to
run transition logic before mutating state (enabling source-state
inspection) and adds new CHASM-focused unit tests for the migrated event
definitions and updated transition behavior.
> 
> <sup>Written by [Cursor
Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit
c0f4e55. This will update automatically
on new commits. Configure
[here](https://cursor.com/dashboard?tab=bugbot).</sup>
<!-- /CURSOR_SUMMARY -->

gow added a commit that referenced this pull request


          [Nexus] Migrate event definition tests from HSM to CHASM (#9597)

a28b82a

## What changed?
Migrating all the event definition's `Apply()` method from HSM to CHASM.
Also migrated unit tests.

## Why?
HSM to CHASM migration

## How did you test it?
- [x] built
- [ ] run locally and tested manually
- [x] covered by existing tests
- [ ] added new unit test(s)
- [ ] added new functional test(s)


<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> **Medium Risk**
> Changes Nexus operation lifecycle handling by moving
scheduling/cancellation and terminal event application into CHASM event
definitions and adjusting state transition semantics; regressions could
affect operation task emission, cancellation timing, and cleanup during
replay/reset.
> 
> **Overview**
> Implements CHASM-based Nexus operation event `Apply()` handlers:
scheduled/cancel-requested/started now create or update the in-memory
operation component (including spawning/scheduling a cancellation child
once an operation token exists), and terminal events
(completed/failed/canceled/timed-out) transition the operation then
remove it from the workflow.
> 
> Refactors workflow Nexus operation storage to be keyed by
`ScheduledEventId` (`int64`), simplifies command handlers to only emit
history events (letting event definitions create/update components), and
expands cancellation/operation state machines with concrete task
emission and retry/backoff metadata. Updates `chasm.Transition.Apply` to
run transition logic before mutating state (enabling source-state
inspection) and adds new CHASM-focused unit tests for the migrated event
definitions and updated transition behavior.
> 
> <sup>Written by [Cursor
Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit
c0f4e55. This will update automatically
on new commits. Configure
[here](https://cursor.com/dashboard?tab=bugbot).</sup>
<!-- /CURSOR_SUMMARY -->

gow added a commit that referenced this pull request


          [Nexus] Migrate event definition tests from HSM to CHASM (#9597)

23e3f42

## What changed?
Migrating all the event definition's `Apply()` method from HSM to CHASM.
Also migrated unit tests.

## Why?
HSM to CHASM migration

## How did you test it?
- [x] built
- [ ] run locally and tested manually
- [x] covered by existing tests
- [ ] added new unit test(s)
- [ ] added new functional test(s)


<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> **Medium Risk**
> Changes Nexus operation lifecycle handling by moving
scheduling/cancellation and terminal event application into CHASM event
definitions and adjusting state transition semantics; regressions could
affect operation task emission, cancellation timing, and cleanup during
replay/reset.
> 
> **Overview**
> Implements CHASM-based Nexus operation event `Apply()` handlers:
scheduled/cancel-requested/started now create or update the in-memory
operation component (including spawning/scheduling a cancellation child
once an operation token exists), and terminal events
(completed/failed/canceled/timed-out) transition the operation then
remove it from the workflow.
> 
> Refactors workflow Nexus operation storage to be keyed by
`ScheduledEventId` (`int64`), simplifies command handlers to only emit
history events (letting event definitions create/update components), and
expands cancellation/operation state machines with concrete task
emission and retry/backoff metadata. Updates `chasm.Transition.Apply` to
run transition logic before mutating state (enabling source-state
inspection) and adds new CHASM-focused unit tests for the migrated event
definitions and updated transition behavior.
> 
> <sup>Written by [Cursor
Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit
c0f4e55. This will update automatically
on new commits. Configure
[here](https://cursor.com/dashboard?tab=bugbot).</sup>
<!-- /CURSOR_SUMMARY -->

bergundy pushed a commit to bergundy/temporal that referenced this pull request


          [Nexus] Migrate event definition tests from HSM to CHASM (temporalio#…

…9597)

## What changed?
Migrating all the event definition's `Apply()` method from HSM to CHASM.
Also migrated unit tests.

## Why?
HSM to CHASM migration

## How did you test it?
- [x] built
- [ ] run locally and tested manually
- [x] covered by existing tests
- [ ] added new unit test(s)
- [ ] added new functional test(s)


<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> **Medium Risk**
> Changes Nexus operation lifecycle handling by moving
scheduling/cancellation and terminal event application into CHASM event
definitions and adjusting state transition semantics; regressions could
affect operation task emission, cancellation timing, and cleanup during
replay/reset.
> 
> **Overview**
> Implements CHASM-based Nexus operation event `Apply()` handlers:
scheduled/cancel-requested/started now create or update the in-memory
operation component (including spawning/scheduling a cancellation child
once an operation token exists), and terminal events
(completed/failed/canceled/timed-out) transition the operation then
remove it from the workflow.
> 
> Refactors workflow Nexus operation storage to be keyed by
`ScheduledEventId` (`int64`), simplifies command handlers to only emit
history events (letting event definitions create/update components), and
expands cancellation/operation state machines with concrete task
emission and retry/backoff metadata. Updates `chasm.Transition.Apply` to
run transition logic before mutating state (enabling source-state
inspection) and adds new CHASM-focused unit tests for the migrated event
definitions and updated transition behavior.
> 
> <sup>Written by [Cursor
Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit
c0f4e55. This will update automatically
on new commits. Configure
[here](https://cursor.com/dashboard?tab=bugbot).</sup>
<!-- /CURSOR_SUMMARY -->

bergundy pushed a commit to bergundy/temporal that referenced this pull request


          [Nexus] Migrate event definition tests from HSM to CHASM (temporalio#…

ec90232

…9597)

## What changed?
Migrating all the event definition's `Apply()` method from HSM to CHASM.
Also migrated unit tests.

## Why?
HSM to CHASM migration

## How did you test it?
- [x] built
- [ ] run locally and tested manually
- [x] covered by existing tests
- [ ] added new unit test(s)
- [ ] added new functional test(s)


<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> **Medium Risk**
> Changes Nexus operation lifecycle handling by moving
scheduling/cancellation and terminal event application into CHASM event
definitions and adjusting state transition semantics; regressions could
affect operation task emission, cancellation timing, and cleanup during
replay/reset.
> 
> **Overview**
> Implements CHASM-based Nexus operation event `Apply()` handlers:
scheduled/cancel-requested/started now create or update the in-memory
operation component (including spawning/scheduling a cancellation child
once an operation token exists), and terminal events
(completed/failed/canceled/timed-out) transition the operation then
remove it from the workflow.
> 
> Refactors workflow Nexus operation storage to be keyed by
`ScheduledEventId` (`int64`), simplifies command handlers to only emit
history events (letting event definitions create/update components), and
expands cancellation/operation state machines with concrete task
emission and retry/backoff metadata. Updates `chasm.Transition.Apply` to
run transition logic before mutating state (enabling source-state
inspection) and adds new CHASM-focused unit tests for the migrated event
definitions and updated transition behavior.
> 
> <sup>Written by [Cursor
Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit
c0f4e55. This will update automatically
on new commits. Configure
[here](https://cursor.com/dashboard?tab=bugbot).</sup>
<!-- /CURSOR_SUMMARY -->

bergundy pushed a commit that referenced this pull request


          [Nexus] Migrate event definition tests from HSM to CHASM (#9597)

398373e

## What changed?
Migrating all the event definition's `Apply()` method from HSM to CHASM.
Also migrated unit tests.

## Why?
HSM to CHASM migration

## How did you test it?
- [x] built
- [ ] run locally and tested manually
- [x] covered by existing tests
- [ ] added new unit test(s)
- [ ] added new functional test(s)


<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> **Medium Risk**
> Changes Nexus operation lifecycle handling by moving
scheduling/cancellation and terminal event application into CHASM event
definitions and adjusting state transition semantics; regressions could
affect operation task emission, cancellation timing, and cleanup during
replay/reset.
> 
> **Overview**
> Implements CHASM-based Nexus operation event `Apply()` handlers:
scheduled/cancel-requested/started now create or update the in-memory
operation component (including spawning/scheduling a cancellation child
once an operation token exists), and terminal events
(completed/failed/canceled/timed-out) transition the operation then
remove it from the workflow.
> 
> Refactors workflow Nexus operation storage to be keyed by
`ScheduledEventId` (`int64`), simplifies command handlers to only emit
history events (letting event definitions create/update components), and
expands cancellation/operation state machines with concrete task
emission and retry/backoff metadata. Updates `chasm.Transition.Apply` to
run transition logic before mutating state (enabling source-state
inspection) and adds new CHASM-focused unit tests for the migrated event
definitions and updated transition behavior.
> 
> <sup>Written by [Cursor
Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit
c0f4e55. This will update automatically
on new commits. Configure
[here](https://cursor.com/dashboard?tab=bugbot).</sup>
<!-- /CURSOR_SUMMARY -->

bergundy pushed a commit that referenced this pull request


          [Nexus] Migrate event definition tests from HSM to CHASM (#9597)

fc1d5ab

## What changed?
Migrating all the event definition's `Apply()` method from HSM to CHASM.
Also migrated unit tests.

## Why?
HSM to CHASM migration

## How did you test it?
- [x] built
- [ ] run locally and tested manually
- [x] covered by existing tests
- [ ] added new unit test(s)
- [ ] added new functional test(s)


<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> **Medium Risk**
> Changes Nexus operation lifecycle handling by moving
scheduling/cancellation and terminal event application into CHASM event
definitions and adjusting state transition semantics; regressions could
affect operation task emission, cancellation timing, and cleanup during
replay/reset.
> 
> **Overview**
> Implements CHASM-based Nexus operation event `Apply()` handlers:
scheduled/cancel-requested/started now create or update the in-memory
operation component (including spawning/scheduling a cancellation child
once an operation token exists), and terminal events
(completed/failed/canceled/timed-out) transition the operation then
remove it from the workflow.
> 
> Refactors workflow Nexus operation storage to be keyed by
`ScheduledEventId` (`int64`), simplifies command handlers to only emit
history events (letting event definitions create/update components), and
expands cancellation/operation state machines with concrete task
emission and retry/backoff metadata. Updates `chasm.Transition.Apply` to
run transition logic before mutating state (enabling source-state
inspection) and adds new CHASM-focused unit tests for the migrated event
definitions and updated transition behavior.
> 
> <sup>Written by [Cursor
Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit
c0f4e55. This will update automatically
on new commits. Configure
[here](https://cursor.com/dashboard?tab=bugbot).</sup>
<!-- /CURSOR_SUMMARY -->

bergundy pushed a commit that referenced this pull request


          [Nexus] Migrate event definition tests from HSM to CHASM (#9597)

0f1844d

## What changed?
Migrating all the event definition's `Apply()` method from HSM to CHASM.
Also migrated unit tests.

## Why?
HSM to CHASM migration

## How did you test it?
- [x] built
- [ ] run locally and tested manually
- [x] covered by existing tests
- [ ] added new unit test(s)
- [ ] added new functional test(s)


<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> **Medium Risk**
> Changes Nexus operation lifecycle handling by moving
scheduling/cancellation and terminal event application into CHASM event
definitions and adjusting state transition semantics; regressions could
affect operation task emission, cancellation timing, and cleanup during
replay/reset.
> 
> **Overview**
> Implements CHASM-based Nexus operation event `Apply()` handlers:
scheduled/cancel-requested/started now create or update the in-memory
operation component (including spawning/scheduling a cancellation child
once an operation token exists), and terminal events
(completed/failed/canceled/timed-out) transition the operation then
remove it from the workflow.
> 
> Refactors workflow Nexus operation storage to be keyed by
`ScheduledEventId` (`int64`), simplifies command handlers to only emit
history events (letting event definitions create/update components), and
expands cancellation/operation state machines with concrete task
emission and retry/backoff metadata. Updates `chasm.Transition.Apply` to
run transition logic before mutating state (enabling source-state
inspection) and adds new CHASM-focused unit tests for the migrated event
definitions and updated transition behavior.
> 
> <sup>Written by [Cursor
Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit
c0f4e55. This will update automatically
on new commits. Configure
[here](https://cursor.com/dashboard?tab=bugbot).</sup>
<!-- /CURSOR_SUMMARY -->

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet