Cloud 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.

Cloud 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.

What is known (2026-10-12, from the launching session)

• The sessions' branches were fix/interview-tests-load-budget-cloud, fix/question-check-says-when-it-skips-cloud and fix/fidelity-gate-skips-the-index-cloud; none reached the forge.
• Each brief set the git identity used on main's recent commits (a human name with a users.noreply.github.com privacy mailbox), which the attribution gate accepts, before the first commit; each was told to stop and report if preflight failed on something it did not touch.
• Likely causes, unconfirmed until the transcripts' errors are copied in: a commit made before the identity step under the environment's default identity (a vendor name or a bare noreply@ mailbox, which the gate refuses), or the environment overriding git config; and a preflight gate needing local state or network the cloud environment lacks.

One session's report (pasted by the person, 2026-10-12)

The session for fix/question-check-says-when-it-skips-cloud made its fix and record commits and stopped before pushing, as briefed: make preflight failed 11 tests across the scanner, ahoy, history, launch and surface/cli packages, none touching its change. The container runs everything as root and has no gitleaks installed, which plausibly explains the ahoy, history and interview failures: tests that prove abcd refuses a path other accounts can write cannot hold when root bypasses permissions, and gitleaks-backed checks have no binary. It confirmed the interview failure also occurs on a clean copy of origin/main there. The commit author name came out as the product thinker's login (the repository's pre-commit identity) with the briefed mailbox, which the attribution gate accepts, so identity was not the blocker. Without a preflight receipt the pre-push hook refuses the push, and the session rightly would not use --no-verify, so nothing reached the forge.

So the finding is narrower than first recorded: abcd's preflight cannot pass in a container that runs as root or lacks gitleaks. A cloud session needs a non-root user and gitleaks (or preflight needs to say plainly which gates need them) before abcd can be worked from one.

2026-11-03 and 04: a container prepared by the cloud setup script still cannot pass make preflight, so a session there cannot push without a person. Its git is 2.43, and the setup installs no later one, so tests needing 2.44 fail rather than skip, in four packages beyond the one #1399 corrected; its session user's name reads as a person's login to the identity scanner (iss-2611032348328608); its proxy blocks the hosts a newer git comes from; its forge token was not valid; and gitleaks behaved differently from CI. #1399's run measured the total: with the container's own git, that user name and no locale, 24 tests in 7 packages fail on the untouched base.