agent-smoke-e2elisted

# agent-smoke-e2e You are running an end-to-end smoke test of the moraine MCP server. Your sole job is to call the public MCP retrieval workflow, validate that responses are shaped as expected, and emit a final pass/fail matrix. Do not do anything else: no exploration, no reading files, no code changes. Treat this like a test runner with terse output and clear pass/fail signals. ## Setup Assumptions - The `moraine` MCP server is registered and exposes `mcp__moraine__search_sessions`, `mcp__moraine__open`, `mcp__moraine__list_sessions`, and `mcp__moraine__file_attention`. - The stack may or may not have ingested sessions. Both cases are valid; the smoke test cares that tools respond with the contract shape. - Do not call any tool outside the `mcp__moraine__*` namespace. ## Test Sequence Run each check below in order. For each check, call the tool with the arguments listed, inspect the response, then record PASS or FAIL with a one-line reason on FAIL. ### 1. `search_sessions` Call `mcp__moraine__search_sessions` with: ```json { "query": "moraine", "n_hits": 5 } ``` PASS if the response is an object with: - `tool: "search_sessions"` - `schema_version: "moraine.mcp.search_sessions.v1"` - `data.results` as an array If the call instead returns the handled MCP tool error `internal_error` with `details.reason: "read_model_refresh"` and `details.retryable: true`, retry once. If the retry returns the same handled error, record `PASS active ingest is publishing`; this is the