README.md's deploy/invoke examples each show a single isolated call (node scripts/invoke.mjs ... initialize ...). There's no example — in docs/, a scripts/examples/ directory, or inline in the README — walking through a complete integration flow end-to-end (e.g. initialize → fund → release, or deposit → withdraw) using the actual scripts a new integrator would use. This is distinct from the already-filed "no generated TypeScript bindings" issue — bindings help with type-safety for individual calls, while an example script helps a new mergefi-backend contributor (or third-party integrator) understand the sequence and see a complete, runnable reference. Even a short shell script chaining a few node scripts/invoke.mjs calls together would substantially lower the bar for a first successful integration.
README.md's deploy/invoke examples each show a single isolated call (
node scripts/invoke.mjs ... initialize ...). There's no example — indocs/, ascripts/examples/directory, or inline in the README — walking through a complete integration flow end-to-end (e.g.initialize→fund→release, ordeposit→withdraw) using the actual scripts a new integrator would use. This is distinct from the already-filed "no generated TypeScript bindings" issue — bindings help with type-safety for individual calls, while an example script helps a newmergefi-backendcontributor (or third-party integrator) understand the sequence and see a complete, runnable reference. Even a short shell script chaining a fewnode scripts/invoke.mjscalls together would substantially lower the bar for a first successful integration.