Config Variants

Config variants

config.yaml is the active run profile. For experiments — a different dataset, model, agent version, concurrency, or retry setting — create a separate variant file next to it instead of editing the active one:

config.glm5-smoke.yaml
config.<dataset>.<agent>.yaml

Only replace config.yaml when you are ready to make a variant active. Each launched job should include a snapshot of the active config at:

artifacts/jobs/<job>/config.yaml

so a run can always be reproduced from its own snapshot.

Tunable parameters

The block declares the parameters that are safe to auto-tune under evolving.tunable_params in config.yaml:

Build and deploy the docs site

These docs are a fumadocs (Next.js) site under docs/, statically exported and served from Cloudflare Pages.

Requirements

The site needs Node >= 20. This host's system Node is 18 (apt-pinned), so a newer Node is installed via nvm. Activate it before building:

export NVM_DIR="$HOME/.nvm"
[ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh"
nvm use 22

Build locally

cd docs
npm install
npm run build     # static export to docs/out/

next.config.mjs sets output: 'export', so the build emits a static out/ directory. The root redirect (/ -> /docs) is expressed in public/_redirects rather than Next's redirects(), which static export disables.

Deploy to Cloudflare Pages

docs/deploy_cloudflare_pages.sh builds and deploys to a dedicated Cloudflare Pages project (swe-trajgen-docs), separate from the dashboard's swe-trajgen-databoard project:

bash docs/deploy_cloudflare_pages.sh

It activates Node 22 via nvm, runs the static build, and deploys docs/out/ with wrangler pages deploy. It reuses the same Cloudflare credentials as the dashboard (CLOUDFLARE_API_TOKEN + CLOUDFLARE_ACCOUNT_ID from .env.cf or ~/.config/trajgen_progress_cloudflare.env); set PROJECT_NAME=swe-trajgen-docs to keep the docs project independent.