Add boost-scores.js dry-run mode

[ritik4ever]

boost-scores.js immediately starts submitting on-chain transactions without any dry-run or confirmation prompt, making it easy to accidentally submit hundreds of transactions if run against the wrong contract.
Category: backend

Project area: backend/scripts/boost-scores.js
Implementation:

Review the current flow in backend/scripts/boost-scores.js.
Add a --dry-run flag that logs what transactions would be submitted (agent name, current score, needed payments) without actually calling recordPaymentOnChain.
Update route/service tests, logging, and docs where the new behavior changes API or operations.

Acceptance Criteria:

The API or service behavior is reachable through the intended code path.
Failure cases return actionable responses or logs.
Automated coverage is added or updated for the touched backend path.

[levoski1]

Kinly assign me this issue, i have strong knowledge on this task

[leocagli]

#156 done

[clintjeff2]

Hello, I have 6 years of experience working on tasks like this and handling similar challenges across backend, frontend, and smart-contract development. I have carefully read and fully understood the task requirements, and I am confident I can deliver a clean, efficient, and well-tested solution promptly. I always ensure high-quality implementation, maintainability, and adherence to best practices.

ETA 10 hours

[naninu123]

boost-scores.js currently fires off on-chain transactions the moment you run it — no dry-run, no confirmation, no safety net. Running it against the wrong contract or with bad scoring data means hundreds of irreversible transactions, which is a real operational risk for anyone managing agent rewards. I already have experience with this codebase (PR #239 approved) and the backend/scripts/ structure. I'll add a --dry-run flag that walks through the exact same scoring logic, logs every transaction that would be submitted (agent address, current score, needed payments, contract target), and then exits without calling recordPaymentOnChain. The flag defaults to off so production behavior is unchanged, but operators get a safety preview before committing. I'll also add a confirmation prompt when running without --dry-run and write tests that verify dry-run mode outputs the correct transaction list without any on-chain side effects.

[grantfox-oss]

🦊 GrantFox — @naninu123 has been assigned to this issue as part of the Official Campaign campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #76)
2. Your PR will be reviewed by the Stellar-Ecosystem maintainers

Good luck! Track your progress on GrantFox.

[naninu123]

PR submitted: #240

What was done:

• Added --dry-run flag to backend/scripts/boost-scores.js — logs planned transactions (agent name, current score, target, needed payments, total amount) without calling recordPaymentOnChain
• Exported boost() function with options object for testability
• Guarded top-level execution behind import.meta.url check to avoid side effects on import
• Added 3 vitest tests in boost-scores.test.js covering dry-run logging, skip-at-target, and live mode

Usage: node scripts/boost-scores.js --dry-run to preview, no flag = live mode (unchanged behavior).

Tests: 3/3 passing, no existing tests broken.

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox as part of the Official Campaign campaign!

@naninu123's PR #240 was approved and merged by @ritik4ever.

🏆 @naninu123: You earned 40 FoxPoints for this contribution! Your current tier: Builder (1,831 total points). Track your full progress on GrantFox.

👏 Great work, @naninu123! Keep contributing to Stellar-Ecosystem.