feat(dx): implement contract ABI codegen pipeline

[Marvy247]

Implements a contract ABI codegen pipeline that auto-generates TypeScript types, SDK client methods, and event parsers from compiled Soroban contract WASM.

Changes

Phase 1 — Codegen pipeline (packages/codegen/)

• packages/codegen/generate.ts — extracts ABI via stellar contract inspect --output xdr-base64-array, parses it with @stellar/stellar-sdk v15, and generates three output files
• packages/sdk/src/generated/types.ts — TypeScript interfaces for every contract type with Soroban-to-TS type mappings
• packages/sdk/src/generated/client.ts — typed GeneratedLinkoraClient class with one method per contract function
• packages/sdk/src/generated/events.ts — typed event interfaces and parseContractEvent parser
• pnpm codegen script that builds WASM and runs the generator
• pnpm codegen:check CI step that fails if generated files are out of sync

Phase 2 — Migration of existing SDK

• packages/sdk/src/types.ts — re-exports generated types instead of manual definitions
• packages/sdk/src/client.ts — LinkoraClient extends GeneratedLinkoraClient, adding error handling and number↔bigint conversions
• packages/sdk/src/index.ts — exports from generated modules

Phase 3 — Shared types package

• packages/types/ — zero-dependency package re-exporting from packages/sdk/src/generated/types.ts
• Ready for consumption by apps/web and apps/mobile

Closes #577

[devJaja]

Thanks for this @Marvy247 — the core pipeline is solid and addresses the root cause of the manual sync problem.
The generate.sh script should be cleaned up regardless, resolve the conflict, make sure all CI checks pass. Then its ready to be merge

[devJaja]

Review: Request Changes ⚠️

Good architecture overall @Marvy247 — the XDR-based ABI extraction approach is correct and the CI check is well-wired. But there are two blocking bugs in the generated output that need to be fixed before this can merge.

Blocking
1. getFollowers and getFollowing are generated without offset and limit parameters.  The contract requires (user, offset: u32, limit: u32) for both functions. The generated client omits the pagination args entirely:

// Generated — WRONG
async getFollowers(user: string): Promise<string[]> {
const retval = await this.simulateCall("get_followers", scvAddress(user));

Calling these will fail at the Soroban level with an argument count mismatch. This is the exact desync this PR was built to prevent. The codegen needs to correctly emit all parameters for these functions.

2. createPost is classified as a read method (simulate-only) when it's a mutating function.
   Because create_post returns a u64 (the new post ID), the codegen places it in readMethods and generates it as a simulateCall. Simulation never writes state — callers will get back a post ID but no post will actually be created on-chain. The codegen needs a way to classify functions that return values but are state-mutating. create_post must be in writeMethods, returning the signed XDR envelope.

3. Governance UDTs are missing from generated/types.ts.
   GovParameter, GovConfig, GovProposal, and GovStatus are #[contracttype] structs/enums that appear in public function signatures but are absent from the generated types file. Any caller using governance functions would get any.

Non-blocking (fix in follow-up)

• apps/web and apps/mobile still import types directly — neither was updated to consume @linkora/types. Please either update them in this PR or open a follow-up issue immediately.
• packages/sdk/generate.sh is still present alongside the packages/codegen/ pipeline. Remove it or document what it's for.
• scvAddressVec only handles string[]. Any Vec where T is not an address falls through to a bare nativeToScVal, which may produce incorrect ScVal encoding for future contract functions. Document the limitation.

[vercel]

@Marvy247 is attempting to deploy a commit to the Jaja's projects Team on Vercel.

A member of the Team first needs to authorize it.

[devJaja]

Nice Implementation @Marvy247 , I can see the changes are now fully implemented.
but quick one , all CI checks are failing, fix it then the PR is ready to be merge

[devJaja]

@Marvy247 The CI checks are still failing