Create `lib/api/agreements.ts`and migrate agreements off Supabase

[ManuelJG1999]

Depends on: Issue Thalos-Infrastructure/ThalosBackend#8

Task Description

lib/actions/agreements.ts still queries Supabase directly and is the dependency for disputes logic. Create a backend client and migrate consumers.

Deliverable

• New lib/api/agreements.ts mapping to backend endpoints.
• Consumers updated to use it; Supabase queries removed.

Requirements

• Map functions to: POST /agreements, GET /agreements, GET /agreements/:id, PATCH /agreements/:id/status, PATCH /agreements/:id/milestones, GET /agreements/:id/activity, GET /agreements/by-contract/:contractId.
• Preserve updateAgreementStatus and logAgreementActivity signatures (used by lib/actions/disputes.ts).

Validation System

• Create/read/update agreements works end-to-end via backend.
• Grep shows no supabase.from("agreements") / agreement_activity in the FE.

Technical Requirements

• Reuse shared client (Issue Implement notification, dispute, and profile backend modules ThalosBackend#1).
• Send the correct wallet_address based on the user's active wallet.

Additional Notes

Do this before Issue Thalos-Infrastructure/ThalosBackend#5 — disputes call updateAgreementStatus and logAgreementActivity.

[ayomideadeniran]

I'm a full-stack developer and I'd like to take this issue.
I understand the requirements and will follow the existing project structure, keep the implementation clean, and include proper tests where applicable.

ETA: 1–3 days (depending on scope)
Portfolio: https://knightsdev-portfolio.vercel.app/

[ChukwuemekaP1]

I'd like to work on this issue.

My approach is to migrate all agreement-related frontend data access from direct Supabase queries to the backend API layer while preserving the existing public function signatures used across the application, especially "updateAgreementStatus" and "logAgreementActivity", since they are dependencies for the disputes module.

Implementation plan:

• Create "lib/api/agreements.ts" using the shared backend client from Issue Implement notification, dispute, and profile backend modules ThalosBackend#1.
• Map all agreement operations to the provided backend endpoints ("POST", "GET", and "PATCH" routes).
• Update all consumers to use the new API layer and remove direct "supabase.from("agreements")" and "agreement_activity" queries from the frontend.
• Ensure the active user's "wallet_address" is correctly passed with requests where required.
• Verify end-to-end agreement creation, retrieval, status updates, milestone updates, and activity logging.

I have experience building full-stack applications with API integrations, backend services, and frontend state management. I pay close attention to backward compatibility during refactoring, so existing consumers continue to work without breaking changes.

I can deliver a clean migration with proper testing and keep the implementation aligned with the project's architecture and conventions.

[grantfox-oss]

🦊 GrantFox — @ChukwuemekaP1 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 Thalos-Infrastructure/ThalosFrontend#102)
2. Your PR will be reviewed by the Thalos-Infrastructure maintainers

Good luck! Track your progress on GrantFox.

[ManuelJG1999]

🎉 Congratulations @ChukwuemekaP1 ! This issue has been assigned to you.

Before you start, make sure you understand the requirements. If you have any questions, ask us in our community chat:
https://t.me/ThalosOSSCommunity

Please keep us updated on your progress. If there's no activity or communication within 48 hours, the issue may be reassigned to another contributor.

Happy coding, and thanks for contributing to Thalos! 🐉

[ChukwuemekaP1]

Got it, thanks for the assignment. @ManuelJG1999

I’ve reviewed the issue and will start working on it right away. If anything comes up that needs clarification, I’ll reach out in the community chat. I’ll also keep regular updates so progress is easy to track.

Looking forward to contributing to Thalos.

[ChukwuemekaP1]

GM @ManuelJG1999,

I'm currently reviewing the repository to start Issue #102, but I ran into something I wanted to clarify before proceeding.

The issue description mentions migrating lib/actions/agreements.ts and creating lib/api/agreements.ts. However, after reviewing the current codebase, I haven't been able to find the lib directory at all, including lib/actions or any existing agreements module matching the paths referenced in the issue.

I also couldn't find the direct Supabase agreements queries (supabase.from("agreements")) or the agreement_activity references mentioned in the task description.

Could you please confirm whether:

• The issue is based on a different branch of the repository, or
• The project structure has changed and there is an updated location for these files?

I want to make sure the implementation follows the latest architecture and avoid working against an outdated structure.

Thanks in advance for the clarification.

[ManuelJG1999]

@ChukwuemekaP1
Hi mate,
Sorry we've not reached out back to you.

Thanks for flagging this before starting, let me clarify.

This issue targets the frontend repository (Thalos-Infrastructure/ThalosFrontend), not the backend (ThalosBackend). The backend is a NestJS project and has no lib/ directory, which is likely why the paths weren't found. If you cloned ThalosBackend, please switch to ThalosFrontend on the main branch.

I just verified against ThalosFrontend@main and everything referenced in the issue is present:

lib/actions/agreements.ts exists and exports these functions, all using Supabase directly:

• createAgreementInDb
• linkContractToAgreement
• updateAgreementStatus
• updateMilestoneStatus
• getAgreementsByWallet
• getAgreementById
• getAgreementByContractId
• logAgreementActivity
• getAgreementActivity

The direct Supabase queries are there too, for example:

• import { createClient } from "@/lib/supabase/server" (line 3)
• .from("agreements") (lines 74, 135, 178, 209, 226, 275, 301, 340)
• .from("agreement_participants") (lines 103, 260, 311)
• agreement_activity is referenced via the logAgreementActivity / getAgreementActivity functions

lib/api/ already exists with sibling clients you can mirror for style/consistency: disputes.ts, escrow.ts, wallets.ts, notifications.ts, and index.ts. Your new lib/api/agreements.ts should follow the same pattern as those (they share an apiRequest-style helper and the ApiResponse<T> shape).

So nothing has moved and it's not a different branch — please confirm you're in ThalosFrontend@main and you should see lib/actions/agreements.ts and lib/api/. Let me know if you still can't see them after switching repos.

I hope this helps,

Thalos team,