v4.0.3

What's Changed

• feat(task): real rollbackTask + complete CUSTOM storage persistence (4.0.3) by @vavi in #6
• fix(task): persist enter-built delta on rollback; mutable request context by @vavi in #7

Full Changelog: v4.0.2...v4.0.3

v4.0.2

Sequential multi-instance countersign now advances through all candidates.

Release alignment update:

• Decouples the internal sequential multi-instance candidate cache from the business variable persistence enable flag, so DB mode works with the default DefaultVariablePersister=false configuration.
• Adds regression coverage for request-scoped sequential candidates across 1 -> 3 -> 5 assignees.
• Adds service-level coverage for explicit operatorUserId records on rollback/add-sign/remove-sign for unclaimed tasks.

Maven Central 4.0.2 has been published from this content.
Central deploymentId: 3b1451ea-622b-4c96-90f4-89f4c14fc532
PR: #5

v4.0.1

SmartEngine 4.0.1

Fix: operator_user_id on rollback / add-sign / remove-sign (G-B5)

rollbackTask / addTaskAssigneeCandidateWithReason / removeTaskAssigneeCandidateWithReason previously recorded operator_user_id from taskInstance.getClaimUserId(). For an assigned-but-unclaimed task claimUserId is null, so inserts into se_process_rollback_record / se_assignee_operation_record (operator_user_id NOT NULL) failed with a constraint violation — these three operations were 100% broken at runtime.

4.0.1 adds backward-compatible overloads taking an explicit operatorUserId; old signatures delegate with claimUserId fallback (unchanged). Callers should pass the acting user.

Verified downstream: AuraBoot BpmTaskOperationTest 18/18 (0 skipped) against a real Postgres + this engine.

Co-Authored-By: Claude Opus 4.8 (1M context)