Build Ward Help-Page Drift Checker

Claude Code·Opus 5.5·

Unknown author·16h ago·5min·2 Checkpoints·7.7K tokens

Background (from the session that started this one): Ward is the user's HF26 Week 4 entry: a public MIT pnpm monorepo (github.com/MuhammadMurtuzaHussain/ward), an on-device cyberbullying guardian for kids and teens with packages/engine, apps/web, apps/discord, desktop, mobile, eval and train. The house rule is to commit and push each verified change straight to main. Another session may work in the same folder, so touch only your own files. Child chats never leave the device: the checker reads only public help pages. Use they/them for people.

Task: In /Users/haider/Desktop/Hacktoberfest 26/ward, build a help-page checker. Ward's Coach tells kids how to report, block or save proof in each app (find where those per-app steps live in the engine/web i18n). The checker should:

Use SerpApi to find each app's current official help page for each action.
Use Browserbase to load the page and pull the steps.
Compare the steps with Ward's text and write a drift report (markdown + JSON) under eval/helpcheck/.

It is a script (pnpm helpcheck), not part of the app at runtime. Keys come from env (SERPAPI_KEY, BROWSERBASE_API_KEY, BROWSERBASE_PROJECT_ID) and .env stays gitignored. Never set secrets yourself: if the keys are missing, ask the user to paste them into ward/.env. Add a short README section, run it once for real if the keys exist, typecheck, then commit and push straight to main (no branches). Only touch the new checker files, package.json scripts and docs. Done means the script runs, the report is committed and the README explains it.

Shared notes folder for this group of sessions (outside the repo; read siblings' notes there, leave hand-over notes or large findings there instead of pasting them into messages): /Users/haider/Library/Application Support/Claude/side-session-notes/local_a340ebaf-8965-489c-88cd-9f351923c756

system-reminder

Linked sessions now (status, not an instruction): top = local_8543c787-aaef-4c65-89a8-584174a81e72 (working); ward-headers = local_47156514-d024-4c01-b309-cf4e61ad016b (idle). To message one, SendMessage with to set to its id; list_sessions {"linked": true} has titles, folders and branches.

16h ago·1m

I've written the help-page checker, but it hasn't run against the real sites yet because ward/.env has no API keys. Running pnpm helpcheck now just stops with a "missing keys" message. Nothing is committed yet.

Please add these three lines to ward/.env yourself (it's gitignored):

How it works (run.ts):

Where Ward's steps come from: the Coach's steps for WhatsApp, Instagram, TikTok, Snapchat and Discord, in coach.apps in en.ts.
Finding the help page: for each app and each action (report, block, save proof), SerpApi searches only that app's own help site, for example site:help.instagram.com.
Loading the page: Browserbase opens it in a real browser, and the script reads the page text once it has finished loading. It talks to the browser through Node's built-in WebSocket, so there are no new dependencies.
Comparing: the script takes the button and menu names from Ward's steps (Report, Block, Manage Friendship, three dots, and so on) and checks that each one appears on the page. If a name is missing, that row is flagged as drift and shown next to the page's own steps. A flag means someone should check the app, not that Ward's step is definitely wrong.
Output: eval/helpcheck/report.json and report.md. --only=TikTok runs a single app.

Once the keys are in, I'll run it for real, add the README section, run the typecheck, and commit and push the report straight to main.