cyberine run refuses a repository with no commit yet (k4zpd)

Every implementer works in a detached git worktree off HEAD, so a repo that has git init but no commit cannot dispatch anything: before 2026-09-12 the run got a run id, reserved spend, and then died inside git worktree add ... HEAD with fatal: invalid reference: HEAD. cyberine run and cyberine run --bg now check git rev-parse --verify HEAD first and exit 2 with one line naming the state and the fix; /cyberine:setup's probe reports the same repo as gap: no commit yet (HEAD is unborn) instead of git ok.

git init scratch && cd scratch
cyberine run "create hello.txt containing the word hi"
#   cyberine run: /path/scratch has no commit yet (HEAD is unborn). Every implementer works in a git worktree off HEAD, so nothing can be dispatched until the repository has a first commit: run `git commit --allow-empty -m init` (or commit your files), then retry.
git commit --allow-empty -m init && cyberine run "create hello.txt containing the word hi"

npm run selftest:first-run-readiness drives the refusal (and the three init/next fixes below it) against temp repos.

Known limitations and deferred work. Only the two cyberine run entry points check; npm run wf -- <def.ts> and the MCP orchestrate tool still fail inside the worktree step. A cwd outside any git repository is not this refusal — that path keeps its existing compare-pool behaviour.