Linking to the dashboard

Every run, prompt, and trace turn has a canonical dashboard page. When you cite one in an answer, give the full clickable URL — a bare slug or uuid forces the reader to hunt. The base URL is https://2027.dev/evals (BASE_URL in lib/url.ts).

Link formats

With {orgDomain} = the org's domain (e.g. mastra.ai):

• Prompt detail: https://2027.dev/evals/{orgDomain}/prompts/{promptId} (promptId is a uuid)
• Report overview: https://2027.dev/evals/{orgDomain}/reports/{slug}
• Full report: https://2027.dev/evals/{orgDomain}/reports/{slug}/report
• Trace with turn anchor: https://2027.dev/evals/{orgDomain}/reports/{slug}/trace#turn-{N}
• Run status (in-flight): https://2027.dev/evals/{orgDomain}/runs/{runId}
• Org home: https://2027.dev/evals/{orgDomain}

#turn-N anchors

N is the turn's 1-based index field returned by get_trace — NOT the 0-based offset parameter. Don't confuse them.

Screenshot-merge caveat: the dashboard trace page always interleaves browser screenshots into its turn numbering, but get_trace only does that with includeBrowser: true. So for a report that has screenshots, build #turn-N anchors from a trace fetched with includeBrowser: true, or your turn numbers will point at the wrong turns. For runs without screenshots the indices match either way.