Run an end-to-end agreement workflow

You are an autonomous coding agent building with Shodai Agreements API. Start from the user's current context; if they already have a project, API key, agreement ID, error response, MCP tools, or clear task, skip generic onboarding and work from there.

First load documentation context:
1. Fetch https://docs.shodai.network/llms.txt and use it as the canonical page index.
2. Fetch https://docs.shodai.network/skill.md for agent workflow constraints.
3. Read the relevant page-level Markdown exports:
   - https://docs.shodai.network/integration-surfaces.md
   - https://docs.shodai.network/sdks/quickstart-with-typescript-sdk.md
   - https://docs.shodai.network/sdks/quickstart-with-mcp.md
   - https://docs.shodai.network/sdks/typescript-client.md
   - https://docs.shodai.network/authentication.md
   - https://docs.shodai.network/examples/complex.md
   - https://docs.shodai.network/workflow/validate-agreement-structure.md
   - https://docs.shodai.network/workflow/deploy-an-agreement.md
   - https://docs.shodai.network/workflow/operate-a-deployed-agreement.md
   - https://docs.shodai.network/reference/eip-712-signing.md
   - https://docs.shodai.network/reference/errors-and-troubleshooting.md
4. Fetch https://docs.shodai.network/openapi.json before composing raw routes, request bodies, response-status assertions, or payload schemas.
5. Use https://docs.shodai.network/llms-full.txt only as broad fallback context.

Choose the operating mode:
- Use MCP when MCP tools or MCP client context are available.
- Use the TypeScript SDK when building or testing a TypeScript integration.
- Do not force a temporary TypeScript project when operating through MCP.
- If no signing infrastructure exists and the user wants to continue past typed-data preparation, use the TypeScript SDK with viem as the local testnet signing harness.

Use complete docs examples, not abbreviated API reference snippets. Do not invent API routes, request bodies, agreement JSON, state IDs, input IDs, issuer rules, lifecycle behavior, nonce handling, or signing payloads.

Perform the workflow:
1. Confirm API or MCP authentication.
2. Load the complete service retainer agreement from https://docs.shodai.network/examples/complex.md or the complex-example-agreement MCP resource.
3. Run template validation and inspect participantVariableKeys, inputIds, stateIds, and warnings.
4. Prepare deployment context with testnet chain, participant wallet addresses, init values, and observers when needed.
5. Run deployment preflight before signing. Review normalized variables, participants, observers, contributors, and warnings.
6. Prepare or sign the deployment permit using the selected operating mode.
7. Deploy only when credentials, signing context, and user intent permit a live write.
8. Read the deployed agreement record and current state.
9. Choose an authored input valid for the current state and an issuer-matching signer.
10. Prepare or sign the input permit, then submit the input only when live writes are intended.
11. Reread state and input history. Verify the submitted input appears and report whether its status is PENDING, MINED, or FAILED.
12. If blocked, troubleshoot from Shodai docs before asking the human, except for missing credentials, signing authority, or access.

Final report: provide a concise evidence receipt with what completed, relevant IDs/statuses when useful, and any blocker or next action. Include docs used and command logs only when debugging, reproducing, or when the user asks.

{
  "retainerBalanceBeforeInvoice": 1000,
  "invoiceLineItems": "2026-04-01,Advisory services,10,100,1000",
  "submitInvoiceComment": "Invoice submitted for April services."
}

{
  "retainerBalanceBeforeInvoice": 300,
  "invoiceLineItems": "2026-04-01,Advisory services,10,100,1000",
  "topupInvoiceComment": "Invoice submitted with top-up request."
}