Simulation Result Diff Comparator

[Kingsman-99]

Description

src/simulationDiff.ts exists but does not provide a structured comparison between two separate simulation runs (e.g. a baseline vs a modified transaction). During development and debugging, engineers need to understand exactly how a change to a transaction affects resource consumption, auth entries, and footprint size. A diff comparator should accept two simulation results and return a typed, human-readable difference object.

Technical Context

Extend src/simulationDiff.ts. Accepts two SorobanRpc.SimulateTransactionResponse objects. Compares fields: cost.cpuInsns, cost.memBytes, minResourceFee, footprint.readOnly, footprint.readWrite, and auth entries. Adds SimulationDiff and ResourceDelta to src/types.ts. Integrates with src/profiler.ts to emit diffs on each profiling run.

Acceptance Criteria

• compareSimulations(baseline, revised): SimulationDiff returns a typed object with cpuDelta, memDelta, feeDelta, footprintAdded[], footprintRemoved[], and authChanged: boolean
• Positive deltas indicate the revised simulation uses more resources; negative indicates fewer
• footprintAdded and footprintRemoved list the LedgerKey XDR base64 strings that differ between the two runs
• formatDiffSummary(diff: SimulationDiff): string produces a human-readable multi-line summary for logging
• Unit tests assert correct deltas for: identical simulations (all zeros), revised simulation with 2× CPU usage, revised simulation with additional auth entry
• All CI checks (npm test, npm run build, ESLint/TypeScript) pass and the branch has no merge conflicts

---

[Calebstack]

@Calebstack has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Hello maintainer, i’ve got this covered! Ready to drop a high-impact, clean PR that gets this merged seamlessly

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

[ololadedavidvictor-bit]

@ololadedavidvictor-bit has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

hello can i work on this issue

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

[CHEF-SAVY]

@CHEF-SAVY has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

I can work on this.
Please assign

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

[drips-wave]

Congratulations, @CHEF-SAVY! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on July 30, 2026.

🧑‍💻 @CHEF-SAVY: 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 🌊

[drips-wave]

This issue has been completed by @CHEF-SAVY as part of the Stellar Wave Program's 7th Wave 🥳

😎 @CHEF-SAVY: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.