PROMPT — paste into Claude Code (or Claude Desktop with shell access) on
your LAPTOP. Folder will be created at ~/360lm-walkthroughs/.

------------------------------------------------------------------------

I want you to install the "360LM Walkthroughs" framework on this laptop.

WHAT IT IS
A Playwright-based human-in-loop runner that replaces CiC chat walkthroughs.
The framework opens a real visible Chromium window, drives it through repetitive
clicks (form fills, navigation, verification), and pauses with an on-page HUD
when only a human can act (sign-in, OTP, CAPTCHA, sensitive review). Scripts
double as Playwright regression tests when run with WALKTHROUGH_TEST=1.

INSTALL DIRECTORY
${HOME}/360lm-walkthroughs

SOURCE
The framework is served from my VPS at
  https://srv1111289.hstgr.cloud/walkthroughs/

There is a one-line installer at
  https://srv1111289.hstgr.cloud/walkthroughs/install.sh
which does almost everything. You can either run the installer end-to-end, or
walk through the steps it does (recommended so I see each step).

GROUND RULES
- Do NOT run the installer with sudo. It only writes inside my home directory.
- If Node 20+ is not installed, PAUSE and ask me to install it (Homebrew /
  nodejs.org installer / apt / choco — whichever fits this OS). Do not try
  to install Node via system package manager yourself — I want to choose.
- If ssh to root@srv1111289.hstgr.cloud is not passwordless, PAUSE and tell
  me to run  ssh-copy-id root@srv1111289.hstgr.cloud  myself. Don't try to
  edit ssh config or copy keys around without my OK.
- Do not edit my ~/.zshrc or ~/.bashrc beyond appending the single PATH line
  the installer adds. Show me the diff first.
- The installer downloads ~150MB of Chromium for Playwright. Confirm with me
  before kicking that off if I'm on a metered connection.
- Do not commit anything to git from this laptop.

PRE-CHECK
Tell me which OS this is (uname / sw_vers / systeminfo), confirm node -v
prints v20 or higher, confirm npm and ssh and curl are on PATH, and confirm
which shell I'm using ($SHELL).

INSTALL — preferred path
Run:
  curl -fsSL https://srv1111289.hstgr.cloud/walkthroughs/install.sh | bash
The script will:
  1) verify Node >= 20, npm, ssh, curl, tar
  2) make ~/360lm-walkthroughs and download dist/walkthroughs.tar.gz
  3) extract; run npm install
  4) run npx playwright install chromium  (the heavy step)
  5) test passwordless SSH to root@srv1111289.hstgr.cloud
  6) append a PATH export to my shell rc file (only if not already present)

After it finishes, in this same terminal run:
  source ~/.zshrc   (or ~/.bashrc — whichever the installer used)
  walkthrough doctor
  walkthrough list
  walkthrough run hello

The "hello" walkthrough is a self-test — it opens example.com and google.com,
shows the HUD overlay in the bottom right corner, and waits for me to click
"Continue". Confirm with me that I see the HUD and can click through.

INSTALL — manual path (use this if the installer fails halfway)
  mkdir -p ~/360lm-walkthroughs && cd ~/360lm-walkthroughs
  curl -fsSL https://srv1111289.hstgr.cloud/walkthroughs/dist/walkthroughs.tar.gz | tar xz
  npm install
  npx playwright install chromium
  ssh -o BatchMode=yes root@srv1111289.hstgr.cloud "echo ok"
  ./bin/walkthrough doctor

If any step fails, PAUSE, show me the exact error, and don't continue.

VERIFY
Run  ./bin/walkthrough doctor  and read me the output. All five lines should
be green checks. If "SSH→VPS" fails because the key isn't on the VPS, tell me
to run  ssh-copy-id root@srv1111289.hstgr.cloud  and re-run doctor.

REPORT BACK
- The Node and npm versions you saw
- Where the install lives (full path)
- Which shell rc file got the PATH line
- Whether SSH→VPS passes
- Whether `walkthrough run hello` showed the on-page HUD card in the bottom-
  right corner of the Chromium window, and whether the "▶ Continue" button
  advanced the steps

DON'T DO
- Don't install any walkthrough scripts beyond what the tarball contains —
  the "hello" sample is enough. Real walkthroughs (Brevo, OpenRouter, etc.)
  will be added by me later via `walkthrough update`.
- Don't run any walkthrough that touches my actual Hostinger / Brevo /
  GitHub accounts during the install verification. "hello" is harmless;
  anything else should wait until I explicitly ask.

------------------------------------------------------------------------
END PROMPT