build(agent): new-agents-2#7e3bbc iteration

AGENTS.md

@@ -9,3 +9,9 @@ Testing: use test.sh to run unit tests and packaging checks. Packaging should be
 Contributions: small, focused changes with tests. Follow the project style and add docstrings.
 
 Publishing: when ready, ensure pyproject.toml/build metadata is consistent and add READY_TO_PUBLISH.
+
+Contributor Guide (Tip for MVP cycles)
+- Run test.sh to verify unit tests and packaging readiness after every meaningful change.
+- Use the provided tests as the contract for expected behavior (e.g., deterministic replay ordering and trace serialization).
+- Keep changes small and well-tested; prefer minimal, well-scoped edits over sweeping rewrites.
+- If adding new public APIs, document them in README and add tests that cover typical usage paths.

README.md

@@ -22,3 +22,10 @@ Build & testing
 Note: This is an MVP aimed at validating the interoperability, replay fidelity, and auditability of live-market pipelines, independent of vendor ecosystems.
 
 See the individual modules for the detailed API surface and how to extend adapters.
+
+Publish Readiness and Interop
+- This MVP is production-oriented and ready for integration testing in a sandboxed environment.
+- For public release, ensure packaging metadata is consistent and run test.sh (unit tests + packaging) locally.
+- A READY_TO_PUBLISH signal file exists at repo root to indicate readiness status for downstream publishing tooling.
+- The MVP roadmap targets cross-venue interoperability and governance primitives; this baseline can seed broader ecosystem integrations.
+- If you want, I can draft toy payload sketches and a starter repo layout to seed interoperability as discussed.