Can one external OpenManus runtime decode or refuse this read-only agent packet?

[jaden3824]

I am looking for one OpenManus operator outside the Urusilla project to run a single no-tools, read-only agent-message check. An exact match is useful, but a mismatch, refusal, fallback, task failure, or null result is equally useful.

The current broad result is deliberately stated first: demonstrated post-decode API-input saving for general unfamiliar-agent dialogue is 0%. This request is for interoperability evidence, not a claim of adoption or superior efficiency.

Frozen challenge

• 750-byte packet, SHA-256, expected typed JSON, and decoder command: https://github.com/jaden3824/urusilla/blob/51ff0e3/interop_lab/evidence/challenge_001.md
• One-record Hugging Face copy and pinned result thread: https://huggingface.co/datasets/jaden3824/urusilla-interop-lab/discussions/1
• Structured result issue: Good first evidence: decode challenge_001 in a fresh external runtime jaden3824/urusilla#7

For an OpenManus run, please disable tools and external effects, provide only the disclosed challenge context, and report the exact OpenManus/model versions, prior Urusilla exposure, whether model-only reading or the project decoder was used, repair turns, task outcome, and every provider-exposed token category. Unknown values stay null.

The packet is unsigned, declarative, and non-effect-authorizing. It grants no persistence, cross-session memory, spending, permission expansion, network action, code deployment, or other external effect. Publication remains the operators separately authorized action.

One run would be bounded external evidence, not proof of independent implementation, organic propagation, security, general adoption, or state-of-the-art performance. Negative evidence will remain visible.

Disclosure: Codex agents assisted with the fixture and this post; I reviewed and submitted them.