diff --git a/docs-site/content/docs/cli-reference/ktx-ingest.mdx b/docs-site/content/docs/cli-reference/ktx-ingest.mdx
index 495ca356..9d94cd88 100644
--- a/docs-site/content/docs/cli-reference/ktx-ingest.mdx
+++ b/docs-site/content/docs/cli-reference/ktx-ingest.mdx
@@ -113,11 +113,15 @@ results.
 
 ## Inspect source ingest traces
 
-Source ingest writes persistent JSONL traces for postmortem debugging. Stored
-ingest status prints the trace path near the run identifiers:
+Source ingest writes persistent JSONL traces for postmortem debugging. Plain
+ingest output prints the trace path near the report, run, and job identifiers
+when a trace is available:
 
-```bash
-ktx ingest status <runId>
+```text
+Report: report-abc123
+Run: run-abc123
+Job: job-abc123
+Trace: .ktx/ingest-traces/job-abc123/trace.jsonl
 ```
 
 The trace file lives under the project directory at
@@ -125,8 +129,7 @@ The trace file lives under the project directory at
 job id, run id, sync id, connection id, source key, phase, event name, timing,
 state snapshot, decision context, and error details. Failed runs also write a
 stored ingest report with `status: "failed"`, `failure.phase`,
-`failure.message`, and the same trace path, so `ktx ingest status <runId>` can
-point you to the postmortem trace.
+`failure.message`, and the same trace path.
 
 Use `jq` or line-oriented tools to inspect a trace: