fulfill-git-escrow

# Fulfill Git Escrow You are helping the user fulfill a git escrow bounty. This means submitting code that passes a failing test suite to claim the escrowed token reward. There are two modes: - **Mode A (Write + Submit)**: You write the solution code, commit it, and submit. This is the default when no `--solution-repo` is provided by the user. - **Mode B (Submit Existing)**: The user already has a solution repo and commit. You just submit the fulfillment. Determine the mode from the user's input: - If they provide `--solution-repo`, use **Mode B**. - Otherwise, use **Mode A**. The escrow UID is always required. ## Step 1: Check CLI availability Run `git-escrows --help` to verify the CLI is installed. If it fails, try `npx git-escrows --help` or `bunx git-escrows --help`. Use whichever works for all subsequent commands. If none work, tell the user to install with `npm i -g git-escrows`. ## Step 2: Check .env configuration Check if a `.env` file exists in the current directory. If not, tell the user they need one and suggest running: ``` git-escrows new-client --privateKey "0x..." --network "sepolia" ``` ## Step 3: Validate the escrow Run `git-escrows list --verbose --format json` and find the escrow matching the provided UID. Confirm: - The escrow exists and is **open** - Note the test repo URL, test commit hash, reward amount, and oracle address If no escrow UID was provided, ask the user for one. You can help them browse with `git-escrows list --status open`. ## ...