Publish standalone flow with consumer examples and release verification

[MasterOfBinary]

Outcome

Publish the standalone flow package and prove ordinary callers can consume its documented API. This release must not wait for RequestBatcher.

Acceptance

• Complete Implement validated flow graphs with bounded runs and node execution #98 and verify finite graph, admission, node/readiness bounds and adverse lifecycle cases.
• Run the ShitQuant-shaped fixture and a nontrading example using ordinary functions/adapters without request batching.
• Record API documentation, ownership/cancellation limits, migration/release notes and supported Go policy (Establish a tested Go support floor and reliable release CI #85).
• Pass normal library gates and applicable fixture/harness checks. Publish a version/tag selected at release readiness.
• Verify a separate consumer with GOWORK=off and no local replace; record resolved module/version.
• Link ShitQuant SQ-22 adoption/parity issue when created. Application adoption compares the released graph's evidence/proposal results and offline replay against the established direct-call baseline.
• May include an already-verified combined scenario from Verify shared request batching across concurrent flow runs #100. Neither Add bounded typed RequestBatcher with one outcome per accepted request #71 availability nor unfinished combined verification blocks this release; the combined work stays an independent follow-on.

Dependencies and boundaries

Blocked by #98 and the supported-Go decision #85. Parent #97. No paid APIs, app implementation, OnyxCore dependency or mainnet transaction required. Publishing is performed only when this scoped issue is executed with its release authorization.