recipe-maintainers/project-orchestrator
0
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat(fleet): register cc-ci as project #1 (poe2e staging, disabled — operator cutover later)

Browse Source
This commit is contained in:
autonomic-bot
2026-06-13 19:38:42 +00:00
parent 346ed31acb
commit 6cc3ed4f13
1 changed files with 13 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
fleet.toml
View File

@ -24,3 +24,16 @@ enabled = true # is this proje
secrets = ".env" # where the project's creds live (path/ref; never in git)
config = "agents.toml" # the project's harness config file (relative to the project root)
notes = "Sample fleet entry — replace with a real project, or remove."
# cc-ci modeled as a project (poe2e staging). enabled=false: the PO must NOT start it — the live
# cc-ci still runs under /srv/cc-ci/cc-ci-plan/agents.py in the cc-ci- tmux namespace. Taking it
# live on the new system is an operator-supervised cutover (see the project's docs/cutover-runbook.md).
[[project]]
name = "cc-ci"
location = "/home/loops/poe2e/cc-ci" # local staging repo (git, engine submodule pinned)
harness = "agent-orchestrator"
ref = "v0.1.0"
enabled = false # STAGING — never started by the PO (would collide with live)
secrets = "/srv/cc-ci/.testenv" # live cc-ci creds (Gitea bot, etc.); never in git
config = "agents.toml"
notes = "cc-ci as project #1 (staging). Migrated from live cc-ci-plan/agents.toml. Parity verified in poe2e. Cutover is operator-supervised."