Aster engine automation
workflows contains repository workflows.
CI checkout prerequisites
All workflows use runs-on: ces-control; no shared Runner configuration is changed.
Configure repository or organization secrets CODEX_BOT_SSH_KEY (the dedicated
codex-bot private SSH key) and GITEA_SSH_KNOWN_HOSTS (the independently verified
known_hosts entry for [gitea.entroia.com]:22222). The bot needs read access to the
repository and its Aster submodule. Workflows use an isolated SSH command with
-F /dev/null, IdentitiesOnly=yes, an explicit key and port, strict host-key
checking, and temporary credential files removed after checkout. Keys are never
written into tracked files. Missing secrets fail checkout explicitly.
The SSH submodule URL's repository owner is separate from the authenticated bot.
Local Git operations must use the same dedicated bot identity; configure the
checkout's isolated command in GIT_SSH_COMMAND for submodule initialization.
Workflow definitions do not prove CI passed. CI/deployment state is not queried automatically. Local runtime checks are not performed for Aster, Lyra or Hestia; Tessera permits local native builds/window runs, with automated tests in CI.