eric/project-work
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

ren worker folder adding orig, mv new one into root

Browse Source
This commit is contained in:
Eric Bell
2026-09-25 10:34:29 -04:00
parent 10f0668e32
commit 5b010039d7
1308 changed files with 44597 additions and 1511 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
worker-toolkit-potion-polyglot/README.md
View File

@@ -76,9 +76,12 @@ The repo has full git history, so you can check out any commit. Use `git log --o
Some repos let you run the real app so you can click through the actual workflows while you explore. Inside the Explore container, one command does it:
```bash
[devcontainer:explore] $ run-app
[devcontainer:explore] $ run-app # single-repo toolkit
[devcontainer:explore] $ run-app <repo> # polyglot toolkit — name the member you want (`ls repos/`)
```
On a polyglot toolkit the bare form starts the toolkit's default member, which is probably not the one you're working on — first use of a member installs its dependencies and provisions its database, so it's worth naming the one you mean.
`run-app` makes sure the database is up, starts the app's server and client in the background, waits until they're listening, then prints the URL to open and a login. It writes logs to a file so your shell stays clean.
```bash
@@ -90,7 +93,7 @@ Some repos let you run the real app so you can click through the actual workflow
The welcome banner prints the exact URL and login for your repo when the container starts.
**Running more than one Explore container at once.** With zero config you can run _one of each repo_ side by side: each repo defaults to a different host port (Palolo `3000`/`3001`, ZenBill `3100`), and `run-app` always prints the right URL for the repo you're in.
**Running more than one Explore container at once.** With zero config you can run _one of each repo_ side by side: each repo defaults to its own host port, and `run-app` always prints the right URL for the repo you're in.
To run _another container with its own separate working tree_ — e.g. to explore a different commit / repo state at the same time — use the `instance.js` helper. (If you only want several Claude sessions on the **same** state, you don't need this at all — just open more shells into the one container with `npx @devcontainers/cli exec bash`.) You do **not** unzip the toolkit again: each instance gets its own container, its own auto-picked host port, and its own repo working tree, so a `git checkout` in one never disturbs another.
@@ -209,7 +212,7 @@ The end of `verifier/test-stdout.txt` prints the score at a glance.
### 11. Iterate
Run multiple times (`-k 4` for 4 parallel attempts). Read the grade.md files — every criterion section, not just the headline score. Adjust `tests/holistic-rubric.md` and re-run (`scripts/harbor-regrade` re-grades a captured run without re-running the agent). Score clustering across runs is normal — what matters is that the task reliably produces clear signal worth grading, not landing in a specific score band. Runs that behaved differently should score differently. Only runs that finished cleanly count toward the four: a run cut short by an API error, a non-zero agent exit or the agent timeout never finished its turn, so re-run it rather than shipping it.
Run multiple times (`-k 4` for 4 parallel attempts). Read the grade.md files — every criterion section, not just the headline score. Adjust `tests/holistic-rubric.md` and re-run (`scripts/harbor-regrade` re-grades a captured run without re-running the agent; `scripts/harbor-regrade harbor-tasks/<slug> --all` re-grades every run you have captured, 2 at a time, and `--jobs N` changes that). Score clustering across runs is normal — what matters is that the task reliably produces clear signal worth grading, not landing in a specific score band. Runs that behaved differently should score differently. Only runs that finished cleanly count toward the four: a run cut short by an API error, a non-zero agent exit or the agent timeout never finished its turn, so re-run it rather than shipping it.
### 12. Copy reference runs
@@ -233,7 +236,7 @@ explore/ # Explore container workspace
plugins/create-snapshot/ # Snapshot skill
snapshots/ # Snapshot output (shared with Authoring)
corpus-viewer/ # Corpus web viewer + index docs (corpus toolkits)
repo/ # Source repo (mounted read-only from parent)
repo/ — or repos/<member>/ # Source repo(s), bind-mounted read-write
data/ # (corpus toolkits only)
zeta-corpus/ # Reference-data corpus (mounted at /data/zeta-corpus)
corpus-index/ # Prebuilt search index over it (corpus.db)
@@ -247,7 +250,7 @@ scripts/
copy-reference-run.ts # Copy Harbor trial data into reference-runs
submit-task.ts # Validate and package a task for submission
task-shared/ # Shared infrastructure (don't modify)
repo/ # Full source repo with git history
repo/ — or repos/<member>/ # Full source repo(s) with git history
.claude/skills/ # Skills for the Authoring container
CLAUDE.md # Project instructions (claude reads this)
AGENTS.md # Same instructions for other agents (generated; don't edit)
@@ -342,7 +345,7 @@ See `.claude/skills/` for detailed guidance (available in the Authoring containe
**Container exited** — Re-run the `npx @devcontainers/cli up` command to restart.
**`http://localhost:<port>` shows nothing** — The app doesn't start on its own. Run `run-app` inside the Explore container (see "Running the app in a browser"), then open the URL it prints. For ZenBill, also add the `/etc/hosts` entries in that section.
**`http://localhost:<port>` shows nothing** — The app doesn't start on its own. Run `run-app` (on a polyglot toolkit, `run-app <repo>`) inside the Explore container (see "Running the app in a browser"), then open the URL it prints. For ZenBill, also add the `/etc/hosts` entries in that section.
**The database isn't running after a reboot or container stop** — Re-run `npx @devcontainers/cli up`; postgres is restarted automatically on every container start. (You no longer need to start it by hand.)