agentic-veupath-dev

Harness that makes a VEuPathDB webapp drivable end-to-end by an agent. It checks out the site's repos (tsrc), syncs your working tree to the webserver where it builds and runs (mutagen), and keeps per-site build/app notes in profiles. From there the same Claude Code session can develop against the site, verify its own changes on the running instance, and dig through logs to debug. You describe the outcome; you don't run the steps by hand.

What you can do with it

The repo is the control plane for a full agentic development loop. Four modes, which chain together:

1. Stand up sync (local → remote). Initialize the repos on both machines and start the mutagen one-way-safe sync so working-tree edits flow to the webserver. This is the foundation the other three build on.
2. Develop features and fix bugs. The agent edits code on a feature branch; mutagen carries those edits to the remote; the agent triggers the site's build commands (bin/veup-build.sh) to compile/deploy on the webserver. Commits and branch switches stay local — only the working tree syncs.
3. QA the result. The agent checks its own work against the running site, not just the diff: hitting webservice/record-page queries and driving live pages with Claude in Chrome to confirm a fix actually landed and behaves.
4. Debug. When something's off, the agent inspects logs from both sides — the webserver (bin/veup-logs.sh <name> mark|since reads the remote app/access logs by page-load delta) and the browser (Chrome console and network) — to locate the failure instead of guessing.

Modes 2–4 are the inner loop: edit → build → verify → (if broken) read logs → edit again. Mode 1 is the one-time setup that makes that loop possible.

How to use it

1. Clone this repo into ~/workspaces/.
2. Start a Claude Code session in it.
3. Tell Claude what you want, e.g.:
   • Setup: "Set up the plasmodb instance and start syncing." / "Add a profile for toxodb and stand it up." / "Start / check / stop the sync for plasmodb."
   • Develop: "On a feature branch, fix the gene record page header, then rebuild the webapp on the remote."
   • QA: "Verify the fix on the plasmodb site — check the record page and run the search that was failing."
   • Debug: "The build failed — pull the webserver logs and tell me why." / "The page is blank; check the Chrome console."

Claude installs mutagen, runs the tsrc checkouts (local + remote), renders the config, and starts the sync. It will ask you for anything it can't figure out (which site, the remote docroot and URL) and will confirm before doing anything destructive.

You provide: SSH access to the webserver and to GitHub. Claude handles the rest.

Design and implementation details live in docs/superpowers/.