# Reflection: Verify Runtime Target and Entrypoint Before E2E

## Trigger

Debugging initially followed the obsolete local MCP/ngrok path even after the user had moved services to a server environment. A subsequent SuperAgent export was also a manual chat-upload processor test rather than the accepted ARR Web upload flow.

## Expected Behavior

Before changing credentials or diagnosing transport, identify the exact MCP URL currently saved in SuperAgent and verify that the probe targets that runtime. Before calling a run “end to end,” require an ARR-created `job_id`, attempt identity, OSS provenance, submission grant, MCP receipt, and database evidence.

## Actual Behavior

The local temporary gateway was authenticated successfully but was irrelevant to the server deployment. The manual Agent run processed XML and presented files without `fetch_oss_file` or `arr_submit_processing_result`, so it could never prove the database path.

## Root Cause

- Stale runtime assumption
- Test-mode confusion
- Acceptance gate applied too late

## Evidence

- User correction that the active MCP is server-side rather than the temporary local tunnel
- `.project-docs/50-evidence/topics/2026-07-29-superagent-manual-xml-run-bypassed-mcp.md`
- `deploy/README.md`

## Lesson

Use a two-part preflight for every external E2E:

1. Record the exact configured endpoint and confirm the probe reaches that endpoint.
2. Classify the test entry as manual processor validation or ARR program-triggered ingestion before interpreting any Agent status.

Never synchronize credentials or restart a runtime until both checks identify it as the active target.

## Action

- Preserve the exported-run evidence and current blocker.
- Require server Web upload plus authoritative MCP/database signals for the next acceptance attempt.

## Promotion

Promoted to current-state risks and the evidence index. No architecture decision changes.