The read-by-hand button was built for one board. The owner has now signed up for a second and asked the manager to drive a browser session over its campaigns page to see what a button press would find.
What the public pages carry
A single list of nine cards: brand, title, how long ago it was posted, the per-view rate, and a lock on some. The campaign’s own public page adds only platform icons and a join link. Everything the campaign finder needs to score a campaign, the rules, the budget, the resources, and the minimum views, is behind sign-in. And the browser extension refuses the signed-in app until the owner allows the site, with a plain message rather than a silent empty result. A button press will meet the same block.
So the guide for the read-by-hand session was rewritten around the three pages: where to look, how the rate on a card converts to the finder’s per-thousand figure, and that a locked campaign is kept out of Suggested. The answer the session gives back can now carry a note that shows on the Campaigns page line. The README says which two sites the extension must be allowed on.
Overnight, under the blanket go
The owner left the pull quote as a standing instruction. Two small merges: a toast’s Undo now works while the Options pane is open, and a campaign page that an older parser had failed on is re-read at once instead of waiting. And one test fix: three render tests failed whenever the drive had less than the free-space floor available, because rendering correctly stops there. The owner’s drive sat just under the floor during the fix and swung above and below it through the night. The code was right; the tests now set the disk state explicitly. Found by a builder’s full-suite run and fixed before morning, per “fixes before features”.