feat: AI project evaluation for price suggestion (#3)

[sureshchouksey8]

Related to #3 by implementing backend AI price suggestion heuristics and integrating them into Step 3 of the project creation wizard with complexity levels and constraints.

[github-actions]

PR readiness check.

• Evidence: provided.
• Repository star: verified for @sureshchouksey8.
• Bounty type: feature bounty.

All bounty readiness checks currently pass.

[sureshchouksey8]

Evidence update for the readiness check.

Validation performed locally:

• Frontend production build passed with bundled Node v24.14.0: npm run build completed both client and SSR server builds.
• Verified the implementation path adds POST /api/projects/evaluate and connects Step 3 of project setup to an AI price suggestion card.
• The UI includes complexity/constraints inputs, loading and error states, a suggested budget range, task breakdown, assumptions, risks, rationale, and an Apply Suggested Budget action.
• Repository star was already submitted for @sureshchouksey8 via the authenticated GitHub API.

Note: backend go test ./... could not be run in this local environment because the go binary is not installed here.

[TUPM96]

@sureshchouksey8
Conflict! Pls check!

[sureshchouksey8]

I pushed commit 33defe6 to address the conflict areas in PR #5 and re-ran the frontend production build successfully (client + SSR). The pushed commit keeps the AI project evaluation endpoint/UI and incorporates the current price-estimator side where the conflicts overlapped.\n\nOne remaining access caveat: GitHub still reports the PR as dirty because the repository's current master includes workflow-file changes, and my available OAuth token cannot push a true master merge/rebase that updates .github/workflows without workflow scope. I can finish the branch update immediately once a workflow-scoped push/update-branch path is available.

[TUPM96]

@sureshchouksey8 Please rebase your branch onto master.

[sureshchouksey8]

Rebased PR #5 onto current master via GitHub conflict resolution.\n\nCurrent head: 673e0e3\nValidation: readiness check completed successfully, and GitHub now reports the PR as mergeable/clean. I also kept the earlier local frontend production build validation (client + SSR passed) for the resolved files.

[TUPM96]

MergeOS approved and merged this PR.

• Merge URL: 11ce6d5
• MRG credit URL: https://scan.mergeos.shop/address/github:sureshchouksey8
• Credited worker: github:sureshchouksey8
• Bounty type: Future bounty - medium
• MRG credited: 50 MRG
• Proof hash: ab782bf7d7e7072a3a13180988907d14e3561275b64d300c2b673f08b1461d9d

[sureshchouksey8]

Thanks for the merge and 50 MRG credit. One practical follow-up so I can track the bounty correctly: where should contributors see the payout ledger entry and the current MRG redemption/liquidity path, if any? The PR credit scan is visible here, but I do not want to count it as cash until the redeemable/payment route is clear.

[sureshchouksey8]

Thanks for approving and merging this, and for crediting github:sureshchouksey8 with 50 MRG.

Could you please share the redemption / payout path for the credited MRG?

Specifically:

• Is there a dashboard, wallet, or claim page we should use for github:sureshchouksey8?
• Can MRG be redeemed or converted to cash/stablecoin, or is it only an internal project credit?
• Are any additional account, wallet, or payment details required from my side?

Scan URL currently shown: https://scan.mergeos.shop/address/github:sureshchouksey8