Issue 119: Add property test for customization history preservation

[temma02]

Description
Implement a property test proving deployment update history preserves prior customization states.

Requirements and context

• Must be secure, tested, and documented where applicable
• Should stay reviewable and fit the current monorepo structure

Suggested execution

• Create branch: issue-119-add-property-test-for-customization-history-pres
• Keep changes scoped to the issue and reference the task IDs in the PR

Implement changes

• Generate sequences of valid customization edits
• Run at least 100 iterations and annotate Property 37
• Assert each historical revision remains recoverable and ordered

Test and commit

• Run the most relevant tests for the touched service or UI surface
• Include screenshots or request/response examples when the change is user-facing
• Call out edge cases, assumptions, and any follow-up work

Example commit message
test: add customization history property

Guidelines

• Prefer small, reviewable PRs
• Keep naming and data contracts consistent with the spec docs
• Preserve responsive and accessible behavior for frontend work

[EmmyKay0026]

@EmmyKay0026 has applied to work on this issue as part of the Stellar Wave Program's 3rd wave.

Hi! I’m interested in taking on this issue to add the property test for customization history. Implementing it will help ensure deployment updates reliably preserve prior customization states. Could you let me know if I can proceed or if there are any specific guidelines I should follow?

ℹ️ Repo Maintainers: To accept this application, review their application or assign @EmmyKay0026 to this issue.

[jahrulezfrancis]

@jahrulezfrancis has applied to work on this issue as part of the Stellar Wave Program's 3rd wave.

Hi, I’d love to work on adding the property test for customization history preservation.

I’ll keep the implementation scoped and reviewable, and build a property-based test that generates valid sequences of customization edits to verify that prior states are preserved correctly over time. The main focus will be proving that each historical revision remains recoverable, correctly ordered, and unaffected by later updates.

I’ll run the required iterations, align the test with the current monorepo structure, and make sure the assertions are strong enough to catch subtle regressions in history handling rather than just obvious failures. I’ll also note any edge cases or assumptions clearly in the PR.

ETA: 4–6 hours.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @jahrulezfrancis to this issue.

[GoSTEAN]

@GoSTEAN has applied to work on this issue as part of the Stellar Wave Program's 3rd wave.

Can i work on this?

ℹ️ Repo Maintainers: To accept this application, review their application or assign @GoSTEAN to this issue.

[popsman01]

@popsman01 has applied to work on this issue as part of the Stellar Wave Program's 3rd wave.

hello dev , assign me to this issue.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @popsman01 to this issue.

[drips-wave]

Congratulations, @popsman01! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on March 30, 2026.

🧑‍💻 @popsman01: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊