Lane 8 journeys: J5 through the new Suggested wiki updates, J6 reads the wiki as a player (#734) #928
Loading…
Reference in a new issue
No description provided.
Delete branch "build/lane8-journeys"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Lane 8's journeys PR (#734; survey §5). The journeys now walk lane 8's pages, and doing so found two bugs, fixed here.
J5, "after the session"
J5 used to stop at the old suggestions page because it failed the contrast scan. Now it:
The fake AI extracts a second entry, an update to Sister Quill (a page the seed has), matched to her page by title, and answers the merge draft with the page followed by what the session added.
Three projects, one database. All three evenings are the same recording, so after the first project adds and merges, a later evening's run correctly finds nothing new: the server skips what a page already says, and the row reads "None left to review". That project asserts this and scans Suggested wiki updates on its own layout, and its add and merge steps skip with the reason given.
J6, "a player finds out what happened", act 5
As Priya, on lane 8's pages, with axe on each:
:::for Ossian Valeblock are there, the GM's block is not; only public timeline events; Mentioned in lists the linking page.The seed
identities.jsonalways said she plays him; the seed never made him.canon.wiki_scenery: a linking page, a GM-only page, a quest with a hidden objective, a line Ossian carries, and two handouts.Bugs the journeys found (fixed)
Tilereadattachments[0].kind), so none of her handouts appeared. Fixed, with a unit test.link-in-text-block: character links 2.23:1 against the text around them, no underline). They're underlined now.Checked
Full journey suite locally, all three projects: 118 passed, 11 skipped (the designed skips, above). Frontend wiki tests pass (172), lint clean.
Part of #734.
🤖 Generated with Claude Code
J5 used to stop at the suggestions page because the old one failed the contrast scan. Lane 8's page is scanned now, and the journey: - follows the checklist's row to Suggested wiki updates (IS-002's list), - adds the new page the session found, - opens the update's merge draft (WIKI-9), waits for the worker, reads the merged text, approves it, and reads it on the page. The fake AI finds a second entry, an update to Sister Quill (a page the seed has), matched to her page by title, and answers the merge draft with the page followed by what the session added. The three projects share one database and the same recording: after the first adds and merges, a later evening's run finds nothing new (the server skips what a page already says), which its row says ("None left to review"). That evening scans the page on its own layout, and its add and merge steps skip with the reason. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>