Files

T

Kai 53ffa2fd7f docs: state the Gitea repo structure and SSH push auth in the README and every scenario root

One Gitea repo (kai/pi-agent-config, SSH key auth as user git on :222) holds the runtime config, all scenario agent configs, and the curator backend; no per-agent repos. Each scenario now carries a root README pointing at the shared repo and push flow so a directory's provenance and push method are unambiguous.

2026-08-30 20:37:11 -07:00

backend

feat(curator): vendor the application backend as the scenario's tracked source

2026-08-30 18:49:10 -07:00

eval/golden

test(curator): re-record phase 2 goldens against the capable pipeline

2026-08-30 07:13:24 -07:00

workspace/.pi

feat(curator): phase 2 - source-extraction skill guidance, structured prompt scope

2026-08-30 06:47:06 -07:00

profile.toml

feat(curator): vendor the application backend as the scenario's tracked source

2026-08-30 18:49:10 -07:00

README.md

docs: state the Gitea repo structure and SSH push auth in the README and every scenario root

2026-08-30 20:37:11 -07:00

README.md

curator — Pi agent scenario

This directory is the curator Pi agent. It is tracked as part of the pi-agent-config repository — it is not a standalone repository.

Gitea repo: kai/pi-agent-config on 192.168.50.45 (web :3000, SSH :222).
Remote: origin -> gitea-45:kai/pi-agent-config.git, branch main.
Auth: SSH key only (~/.ssh/id_ed25519_gitea, Git user git); no HTTP token.
Push and pull from the repository root, not from here:

git pull --rebase origin main
git push origin main

See the repository README.md, section “Gitea repository and push authentication”, for the full SSH config and caveats.

Layout

profile.toml — the launch contract (single source of truth).
workspace/ — the .pi configuration deployed into the live workspace.
eval/ — recorded golden transcripts.
backend/ — the authoritative Python service source; the live workspace checkout is a runtime copy.
docs/ — scenario-specific documentation.