Development record
Nothing prepares a cloud container to work on abcd the way the development machine is prepared: on 2026-10-12 the container ran everything as root, had no gitleaks, and needed the brief to set the git identity, so preflight failed (iss-2610120724251698). abcd documents its local prerequisites but has no setup step or check for a cloud environment.
issueopenminoriss-2610120729094755
Nothing prepares a cloud container to work on abcd the way the development machine is prepared: on 2026-10-12 the container ran everything as root, had no gitleaks, and needed the brief to set the git identity, so preflight failed (iss-2610120724251698). abcd documents its local prerequisites but has no setup step or check for a cloud environment.
Frontmatter
| id | iss-2610120729094755 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | minor |
.abcd/work/issues/open/iss-2610120729094755-no-cloud-environment-setup-for-abcd.md
open on GitHub ↗ · commit history ↗
References1
- itd-2610120738075547Work handed to a cloud session comes back, or says why notrelated
mentions2
- iss-2610120724251698Cloud agent sessions started on 2026-10-12 to work drain-eligible issues all failed abcd's preflight and had git identity problems, so none pushed a branch (the person reported this; the exact errors are with the launching session abcd-0b). abcd's gates assume the local development machine: every commit must name a human author (the attribution gate refuses a machine identity or none), and preflight resolves the go.mod-pinned toolchain and other local prerequisites. A cloud session gets neither by default, so abcd cannot yet be worked from a cloud session.
- spc-2610120941441282a-person-hands-an-item-from-their