docs: add end-to-end integration walkthrough for embedding the SDK

[latiblack]

Expands docs/INTEGRATION.md with a complete, copy-paste walkthrough covering install -> create round -> commit sealed bid -> open reveal -> settle -> export receipt.

Changes:

• Full numbered walkthrough with runnable snippets (install, configure, deploy, create round, seal+commit, keeper reveal, clear+settle, export+verify receipt)
• Notes on required env/keys and testnet vs mainnet
• Keeper service usage guide
• Cross-linked from README.md Integration model section
• All local links verified via scripts/check-links.js

Closes #156

[karagozemin]

Changes requested: the walkthrough is link-clean but the core copy-paste path is not runnable as written.\n\n- configures testnet RPC/passphrase with , which the repository documents as the mainnet deployment. A reader following the example will query a contract that does not exist on testnet.\n- passes the classic USDC issuer account () as the constructor value and labels it a SAC. The round contract needs the deployed SEP-41 asset contract ID (), otherwise escrow token calls cannot work.\n- tells users to install and invoke through , but is private and defines no entry. That command cannot run.\n\nPlease base the deployment/lifecycle snippets on the existing live scripts and either provide real per-network values or explicit placeholders plus the exact commands that derive them. External links: 5 (pass --external to list)
OK 38 local link(s) checked, 0 allowlisted passes (42 local links), but it cannot catch these executable-example errors.

Replaced because Markdown was corrupted during submission.

[karagozemin]

Changes requested: the walkthrough is link-clean but the core copy-paste path is not runnable as written.

• docs/INTEGRATION.md:64 configures testnet RPC/passphrase with CA7KS..., which the repository documents as the mainnet deployment. A reader following the example will query a contract that does not exist on testnet.
• docs/INTEGRATION.md:109 passes the classic USDC issuer account (G...) as the constructor usdc value and labels it a SAC. The round contract needs the deployed SEP-41 asset contract ID (C...), otherwise escrow token calls cannot work.
• docs/INTEGRATION.md:383-390 tells users to install and invoke @sub-rosa/keeper through npx sub-rosa-keeper, but services/keeper/package.json is private and defines no bin entry. That command cannot run.

Please base the deployment/lifecycle snippets on the existing live scripts and either provide real per-network values or explicit placeholders plus the exact commands that derive them. node scripts/check-links.js passes (42 local links), but it cannot catch these executable-example errors.

[karagozemin]

Rechecked the current head (913a0250). There have been no commits since the requested-changes review. The walkthrough still mixes the mainnet contract with testnet configuration, uses a classic G... issuer where the constructor requires a SEP-41 C... contract, and documents a keeper npx command that the private package does not expose. The copy-paste path is therefore still not runnable.

[latiblack]

Hey @karagozemin, thanks for the review. All three issues have been addressed:

• §2 contractId: Changed from the mainnet CA7KS... to <DEPLOYED_CONTRACT_ID> with an inline note directing testnet readers to §3 and confirming CA7KS... is the mainnet value.

• §3 USDC SAC: Replaced GBBD47... (classic G-prefix issuer) with CAPTODB... (testnet SAC contract ID). Also fixed the USDC addresses reference table at the bottom.

• §9 keeper CLI: Replaced npm install @sub-rosa/keeper + npx sub-rosa-keeper watch with pnpm keeper:watch from the monorepo root, since the keeper package is private and has no bin entry.

Should be runnable as written now.