Feature/mooclet params modal and view

[danoswaltCL]

• Adds a ts-configurable form in add/edit experiment modal
• Adds a bulleted list capability to the overview details component
• Implements bulleted list for moocletPolicyParameters when detected
• Mooclet Helper Service to delegate mooclet related logic as much as possible
• Adds Reward Feedback card under Enrollment Data in Data Tab, which is essentially the current_posteriors data

@amurphy-cl open to any wordsmithing of the language

![Uploading image.png…]()

[zackcl]

Problem: && operator doesn't work as expected for string concatenation. If wasMooclet is true, it evaluates to the string, but if false, it adds false to the message. Fix:

let message = `[Algorithm Change] Assignment algorithm changed from ${oldAlgorithm} to ${experiment.assignmentAlgorithm}.`;
if (wasMooclet) message += ' Will delete old Mooclet resources after successful update.';
if (isNowMooclet) message += ' Will create new Mooclet resources as part of update.';

[zackcl]

Consider removing this commented code.

[zackcl]

Problem: The deletion uses moocletExperimentRefRepository.delete() directly instead of using the transaction manager. This means the deletion may not be part of the transaction and could cause:

• Orphaned refs if the transaction rolls back after deletion
• Loss of atomicity

Fix:

if (params.moocletRefToDelete) {
  await manager.delete(MoocletExperimentRef, params.moocletRefToDelete.id);
}

[zackcl]

Double Deletion Risk in Algorithm Change Flow

Location: MoocletExperimentService.ts:1507-1535 The code deletes mooclet resources in two places:

1. Inside syncUpdateWithMoocletAlgorithmTransition transaction (line 185) - deletes UpGrade DB ref
2. Outside transaction in handlePotentialMoocletAssignmentAlgorithmChange (line 1515) - deletes external Mooclet API resources

Issue: If the external Mooclet deletion fails (line 1515), you've already deleted the UpGrade DB reference (line 185), making it impossible to retry cleanup later. This creates orphaned Mooclet API resources with no way to track them. Recommendation: Consider one of these approaches:

• Option A: Only delete the UpGrade ref inside the transaction, move ALL external deletions outside
• Option B: Keep a "soft delete" flag on refs to track failed cleanups
• Option C: Add a cleanup job to handle orphaned resources

[zackcl]

I added a few review comments suggested by Claude. Feel free to resolve or ignore them.