2Above the file content, click Blame.accurate
VerdictThe literal pass failed once, but the route Kane found is the doc's own route. Treated as a flaky run, not drift.
What Kane did
Literal failedaction · 9.2 cr · 117s
  1. navigate: Navigate to https://github.com/expressjs/express/blob/master/Readme.md
  2. wait: PRIMARY: wait for the element whose visible label is exactly 'Blame' to become v
  3. wait: Waiting after checking for the element whose visible label is exactly 'Blame'
The run stopped because its page-state check said it was on an Activity page without Blame, even though the captured page shows the Readme file with a Blame control.
Follow these steps literally, one at a time, from the current page. Click only what each step names. Never type a URL, search, or take another route. 1. Click the element whose visible label is exactly 'Blame'. Then store the main heading of the page you end on as 'landed_on'.
Goal passedtesting · 18.5 cr · 74s
  1. navigate: Navigate to https://github.com/expressjs/express/blob/master/Readme.md
  2. click: Clicking the Blame button to open the line-by-line blame view
  3. wait: PRIMARY: wait for the blame page heading "Readme.md" to load
  4. analyze: ANALYZE(textual_visual, 'Get the main heading of the page you end on and save as
  5. assert: a line-by-line blame view, with code grouped by commit, is visible.
opened the Readme.md blame view on GitHub
Clicked, per the evidence pack: Blame
Goal: a line-by-line blame view, with code grouped by commit, is visible. Reach it from the current page by clicking through the visible UI, by any route. Never type a URL or use the address bar. Hint: an old tutorial said "Above the file content, click Blame.", but those labels may have moved or been renamed. When the goal is met, store the main heading of the page you end on as 'landed_on', then verify the goal on screen.
3To return to the raw code view, above the file content, click Code.accurate
VerdictKane followed the doc's exact words and reached the goal.
What Kane did
Literal passedaction · 20.1 cr · 81s
  1. navigate: Navigate to https://github.com/expressjs/express/blame/master/Readme.md
  2. click: Clicking Code link in repository navigation
  3. wait: PRIMARY: wait for the repository page heading to load
  4. analyze: ANALYZE(textual_visual, 'The main heading of the page you end on is saved as {{l
  5. wait: Waiting after completion
opened Code on github.com
Clicked, per the evidence pack: Code
Follow these steps literally, one at a time, from the current page. Click only what each step names. Never type a URL, search, or take another route. 1. Click the element whose visible label is exactly 'Code'. Then store the main heading of the page you end on as 'landed_on'.
4If you are viewing a Markdown file, above the file content, you can also click Preview to return to the view with Markdown formatting applied.false alarm
Errata saiddrifted, with a rewrite: “Click Readme.md.”
ReviewFalse alarm. Errata bug, not a docs error: step 3 says to click Code above the file content, but given only the label, Kane clicked the repository Code tab (a second Code on the page), so step 4 started on the wrong page. Kane now also gets the doc sentence as context. Re-run with the fix (runs/2026-11-16/rerun): all 3 steps accurate.
Approved byDarkfallx
What Kane did
Literal failedaction · 20.5 cr · 79s
  1. navigate: Navigate to https://github.com/expressjs/express
  2. scroll: Scrolling to Preview section
  3. scroll: Scrolling to Preview
  4. scroll: Scrolling to the Preview section
  5. wait: Waiting after checking for the element whose visible label is exactly 'Preview'
The run expected a visible “Preview” control on the Express repository page, but that page does not provide one.
Kane's screenshot at the end of the literal run
Kane's screenshot at the end of this run, from its sealed evidence pack
Follow these steps literally, one at a time, from the current page. Click only what each step names. Never type a URL, search, or take another route. 1. Click the element whose visible label is exactly 'Preview'. Then store the main heading of the page you end on as 'landed_on'.
Goal passedtesting · 22.7 cr · 108s
  1. navigate: Navigate to https://github.com/expressjs/express
  2. click: Clicking Readme.md in the folders and files list
  3. wait: PRIMARY: wait for the Markdown file with formatting applied to finish loading
  4. analyze: ANALYZE(textual_visual, 'The main heading of the page you end on is saved as {{l
  5. assert: The Markdown file is shown with formatting applied.
opened the formatted Readme.md file on GitHub
Clicked, per the evidence pack: Readme.md
Kane's screenshot at the end of the goal run
Kane's screenshot at the end of this run, from its sealed evidence pack
Goal: the Markdown file is shown with formatting applied. Reach it from the current page by clicking through the visible UI, by any route. Never type a URL or use the address bar. Hint: an old tutorial said "If you are viewing a Markdown file, above the file content, you can also click Preview to return to the view with Markdown formatting applied.", but those labels may have moved or been renamed. When the goal is met, store the main heading of the page you end on as 'landed_on', then verify the goal on screen.
Proof · loop 1 passedaction · 19.5 cr · 102s
  1. navigate: Navigate to https://github.com/expressjs/express
  2. click: Clicking Readme.md
  3. wait: PRIMARY: wait for the heading "Readme.md" to be visible
  4. analyze: ANALYZE(textual_visual, 'The main heading of the page you end on is stored as {{
  5. wait: Waiting after confirming the Readme.md page heading
opened Readme.md on GitHub
Clicked, per the evidence pack: Readme.md
Kane's screenshot at the end of the proof · loop 1 run
Kane's screenshot at the end of this run, from its sealed evidence pack
Follow these steps literally, one at a time, from the current page. Click only what each step names. Never type a URL, search, or take another route. 1. Click the element whose visible label is exactly 'Readme.md'. Then store the main heading of the page you end on as 'landed_on'.