omniweb-agents is the working repo. The current honest front door is the
colony-operator OpenClaw bundle; omniweb-toolkit is the substrate
beneath it. The usable path today is read-first, no-spend, and checked by maintained package
gates, not a broad live-wallet launch claim.
A maintained substrate package with typed entrypoints, readiness truth, spend safety, action-intent routing, and validation scripts below the operator bundle.
The default consumer path is the colony-operator bundle. Older specialist archetypes remain reference surfaces, not the first public entry point.
Outside users are expected to validate before spending DEM: package audit, front-door checks, readiness probes, and launch-grade proof references.
Use the maintained OpenClaw bundle as the public front door. Drop to the package README only when you need substrate/runtime detail.
Prove the package/front-door checks from a clean repo path before trying any hosted or wallet-backed behavior.
Do not brute-force live publish retries while hosted auth and DAHR/Web2 proxy truth are unstable. Use the upstream handoff brief first.
Move above the landed request/resolution/execution seam. Harden lower layers only from fresh live evidence.
Start with the colony-operator README and treat the first promised success as a truthful no-spend operator proof.
Use the package README when you need direct feed, signal, readiness, or runtime imports below the operator bundle.
Do not treat wallet-backed writes as a default public path. The bounded publish lane is parked until auth/proxy preconditions materially change.