mirror of
https://github.com/stablyai/orca.git
synced 2026-11-15 18:37:24 +00:00
Neil
0a625740cc
On every Orca Cloud start and wake, orcad ran its disposable startup preflight child. That child is a second full load of the 15 MB bundle plus the SQLite and node-pty probes, and it ran before main(). The cloud slot could never be qualified: qualification needed the managed-activation env, and the marker lives in the slot directory, which is root-owned in the image. In-VM profiles showed the main thread idle for about 580 ms waiting on that child. - ORCA_ORCAD_STARTUP_QUALIFICATION_DIR names a writable directory for the startup-qualified marker and opts the slot into qualification. The key is unchanged: artifact version, file stat identity, runtime, ABI, kernel and launch env. It survives a stop and resume: inode, mtime and ctime are identical after resume, and the first launch after resume skipped the preflight. - The image creates /opt/orca/startup-qualification. The provisioning smoke run records the marker, and orca-sandbox-start passes the env. - Agent-state-rules live updates and speech-model warm-up now start after the ready line instead of before it. - Once the ready line is published, a terminal list warms the terminal path (worktree catalog, daemon inventory) before the reconnecting desktop asks for it. Real 4-vCPU VMs, readyMs median of 5: idle 1475 -> 903 ms; with 3 busy cores 1921 -> 1200 ms.