ecorp-operationslisted

# Inspect ECorp operations Use the configured `ecorp` MCP server and its `crony_snapshot` tool. For a selected Factory work item, use `crony_factory_recovery_context` with its exact `work_item_id` UUID. The repository configuration starts the native gateway with `--read-only`: it exposes these inspection tools and rejects write tools before making a server request. If the installed gateway lacks this mode, build the current gateway; do not silently remove the flag. The operator must select the server, Corp and actor through trusted host configuration. Do not substitute demo identities, another Corp, a localhost default or another signed-in account when the requested identity is unavailable. The server remains responsible for membership and role authorization. A native tool permission is not tenant authorization. For setup and the non-mutating stdio probe, read [the MCP operations guide](../../../docs/MCP_OPERATIONS.md). The probe emits connection metadata and counts; the snapshot itself can contain private operational content and should stay within the requesting user's authorized context. Do not copy full snapshots into public issues or logs. ## Trace an outcome Find the exact mission/run requested by the user and correlate its task status, runner presence, verification result, outstanding approval and budget state. Prefer persisted IDs and source or artifact digests over display names. A missing object may be outside the actor's scope; it is not proof that no such obje