test(runtime): prove Discord no-op observation path

[egdev6]

Pre-flight checks

• I searched existing issues and this is not a duplicate
• I understand this verification must be approved before execution if it can mutate private runtime state
• I will not post real Discord IDs, tokens, credentials, screenshots, raw logs, transcripts, or private payloads

Verification goal

Prove a read-only no-op observation path for #211 before any write-like private Discord traffic. The path must observe a synthetic or separately approved redacted Discord event, classify route/approval metadata, and stop before prompt execution, workspace writes, Engram writes, filesystem writes, publishing, scheduling, or external network side effects.

Environment

Local Docker runtime

Verification checklist

• Use examples/private-discord-engram-noop-observation.fake.yaml as the expected design contract.
• Exercise only a read-only no-op/status/preview path.
• Matched-route preview returns approval-requested with no writes.
• Unmapped-route preview returns needs-route with no durable reads or writes.
• Output includes placeholder runtime namespace and sanitized target refs only.
• No prompt execution, workspace writes, Engram writes, filesystem writes, publishing, scheduling, GitHub mutations, or external side effects occur.
• test(runtime): execute private Discord-to-Engram vertical slice #211 readiness can move no-op-observation-path from design-only-not-proven only after sanitized runtime evidence proves the path.

Safety and rollback notes

This verification must not use production credentials or public Discord channels. Do not commit real guild/channel/user/message IDs, credentials, screenshots, raw logs, transcripts, private payloads, raw Engram exports, or SQL dumps. If the runtime requires prompt execution or workspace writes to observe the event, stop and mark the check blocked.

Result summary

Not executed yet. PR #226 recorded a sanitized preflight showing the runtime/plugin were ready enough for preflight, but live message execution remained blocked by the readiness gate.

[egdev6]

PR #230 merged the repo-safe synthetic no-op observation CLI into develop.

Merged scope:

• packaged discord-project-manager-noop-observation into the OpenClaw image;
• synthetic matched-route write-like preview stops at approval-requested;
• synthetic unmapped-channel preview stops at needs-route;
• prompt execution, network calls, filesystem/workspace writes, Engram writes, publishing, scheduling, and GitHub mutations remain blocked;
• validator rejects control/YAML injection, private identifier-like values, and common token-like inputs;
• malformed approval-guard output fails closed.

Remaining #228 work before this issue can close:

• prove the real private/redacted Discord observation path, or explicitly decide that repo-safe synthetic proof is sufficient for this milestone slice.

#211 remains blocked. This PR improves the no-op evidence surface but does not prove live Discord gateway delivery, private redacted event ingestion, or readiness available-and-proven.