[Task]: Allow a user to run multiple concurrent tasks if balance is sufficient

[grantfox-oss]

create_task() asserts config.active_tasks_count == 0, meaning a user can only ever have one active task at a time. The active_tasks_count field already supports values greater than 1 — the restriction is a single assert, not a structural limit.

This is unnecessarily restrictive. An orchestrator serving a user with multiple parallel steps (already supported in executor.ts) must currently serialize all tasks sequentially at the contract level.

Change in create_task():

Remove:

assert!(config.active_tasks_count == 0, "User already has an active task");

Replace with a balance check only — if the user has sufficient available balance for the new task's plan_cost, the task should be allowed regardless of how many tasks are already active:

// `available` is already computed below; the assert on it is sufficient

The existing available >= plan_cost assert already prevents over-commitment. No other guard is needed.

Test updates:

• test_create_task_already_active_fails should be renamed and updated to verify that a second task succeeds when balance is sufficient, and fails only when available balance is insufficient.
• Add a test for two concurrent tasks completing independently.

Acceptance criteria

• create_task() no longer panics when active_tasks_count > 0
• Creating a second task with sufficient available balance succeeds
• Creating a second task that would exceed available balance fails with an insufficient-balance error
• active_tasks_count is correctly incremented/decremented through the full lifecycle of two concurrent tasks
• cargo test and cargo clippy -- -D warnings pass

Relevant files

• contracts/agent-vault/src/lib.rs (only the create_task function)
• contracts/agent-vault/src/tests.rs

Notes for contributors

If you'd like to work on this, comment below so we can assign it to you.
Questions welcome — see CONTRIBUTING.md for setup
and workflow.

[Abdul-dev-creator]

am an experienced dev assign this issue to me

[Dwifax]

I'm experienced with Rust and Stellar/Soroban smart contracts. I've reviewed the codebase and previously contributed PR #5, #7, #10, #3, #4 to the clevercon repo. This issue is straightforward — just remove the active_tasks_count assert and update tests. I can submit a PR within 24 hours.

[naninu123]

Familiar with Soroban contract patterns — contributed to StellarLend (admin dedupe) and Lumina-Backend (circuit breaker). For concurrent tasks, I will remove the assert!(config.active_tasks_count == 0, ...) guard from create_task() and rely solely on the existing available >= plan_cost balance check to prevent over-commitment. Update test_create_task_already_active_fails to verify: second task succeeds when balance is sufficient, fails with insufficient-balance error when it would exceed available funds. Add test for two concurrent tasks completing independently with correct active_tasks_count increment/decrement through full lifecycle. cargo test and cargo clippy -- -D warnings pass. Relevant files: contracts/agent-vault/src/lib.rs (create_task function only) and contracts/agent-vault/src/tests.rs. Branch: test/allow-concurrent-tasks.

[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 #40)
2. Your PR will be reviewed by the clevercon-protocol maintainers

Good luck! Track your progress on GrantFox.

[grantfox-oss]

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

@naninu123's PR #57 was approved and merged by @Bosun-Josh121.

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

👏 Great work, @naninu123! Keep contributing to clevercon-protocol.