live smoke: three tests assert on instance data that has drifted #8

Three UI tests fail on main, independent of any current branch (verified by running them on main):

1. testCreationAndEditingFlows:84 — waits for an issue row containing README.org. That is issue #4, which is now closed, so it is not in the default open list. The test needs its own fixture issue, or to switch the filter to All.

2. testDiscoveryFlows:417 — asserts app.staticTexts["Repositories"] on a profile. The section header is Repositories \(profile.repos.count), so the label is "Repositories 12" and the exact match fails. Should match by prefix.

3. testScreenshotCheckpoint:606 — after tapping the first MR row, waits for the "Diff" static text and does not find it. Root cause not established; MRView renders that row unconditionally, so it may be a timing or mis-tap problem rather than data.

The pattern across all three is tests pinned to live instance state that changes as the project moves. Worth deciding whether the live suite should create its own fixtures (as testRepoManagementFlows does with cmc/ui-smoke) rather than assert on whatever happens to be there.

Fixed by !24. It did not close itself on merge despite "Closes #8" in the body — a bare #8 in the commit message claimed the shared dedup key first. That is krz/gitbay!108.