Implement Integration Test for Loss at Multiple Streak Levels

[popsman01]

Description
Verify losses at streak levels 1 through 4 plus apply forfeiture and cleanup consistently.

Motivation
Tests are the primary safety net for the Tossd contract. Without coverage for this area, regressions can go undetected and break game fairness or fund safety guarantees.

Requirements and context

• Must be secure, tested, and documented
• Should be efficient and easy to review
• Primary files: Tossd-contract/src/lib.rs

Proposed Solution
Complete the following in a focused PR off feature/integration-loss-levels:

• Write loss integration scenarios across streak levels
• Verify cleanup and accounting after each loss
• Document expected forfeiture behavior

Technical Implementation

Files to modify:

• coinflip-contract/src/lib.rs

Implementation steps:

• Write loss integration scenarios across streak levels
• Verify cleanup and accounting after each loss
• Document expected forfeiture behavior

Branch: feature/integration-loss-levels

Example commit message

test: add integration coverage for losses across streak levels

Acceptance Criteria

• Run tests
• Cover edge cases
• Include test output and flow notes

Guidelines

• Assignment required before starting
• PR description must include: Closes #153

[drips-wave]

This issue has been added to the Stellar Wave Program and is worth 200 Points.

🧑‍💻 Interested in contributing? Apply to work on this issue on Drips Wave, earn points, and receive rewards.

Warning

Only applications submitted via the apply link above will be considered. Please do not apply by commenting on the issue or opening a PR directly.

🤠 Repo maintainers: You can manage this issue's Points and Complexity on your Maintainer Dashboard here. Please keep an eye on applications and respond quickly 💙

ℹ️ Learn more about Drips Wave

[Kenlachy]

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

I would like to work on this issue because validating loss behavior across multiple streak levels is important to ensure correctness of state transitions, reward or penalty calculations, and streak resets. Without integration tests, subtle bugs in streak handling could accumulate and produce incorrect outcomes over time.

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