gitlisted

# git — the event procedures Your boot's VERSION CONTROL section carries the every-session rules: sync the base, branch before you build, commit → push → PR → stop, the merge gate's two forms, the disposable `shell/<shortname>` base, and the finish gate. This skill holds what fires on an event. One repo at its root -> plain `git` (cwd = repo root) is safe. Project = this repo minus `.super-coder/`. In a tracking fork the engine (`.super-coder/`) is gitignored, materialized by `sc update`, and authored upstream in Subfloor — NEVER commit or edit anything under it. In the Subfloor source repository (`git ls-files --error-unmatch .super-coder/schema.sql` exits 0) `.super-coder/` is tracked project source and `.sc-state/engine.ref` is not the delivery unit; engine changes still land by branch and PR. ## GitHub capability boundary `sc launch` and `sc restart` re-resolve Git transport and GitHub API capabilities from the host on every invocation, including `--no-build` forms. `build`, `enter`, and an already running sandbox do not refresh auth. Pass = the lifecycle summary says `ready` for the operation you need; `unavailable` and `unverified` are NEVER readiness claims. Preserve the configured `origin` transport. For SSH, fix the host agent and load an authorized GitHub identity; NEVER copy or mount private keys. For HTTPS/API, fix a scoped host `SC_GH_TOKEN` or the host `gh` OAuth login. Then run `sc launch` or `sc restart`; the running sandbox remains unchanged until that r