Skip to content

note.md

Latest commit

 

History

History
21 lines (17 loc) · 2.14 KB

note.md

File metadata and controls

21 lines (17 loc) · 2.14 KB
Raw

Runtime Provider Homes

Delivery

  • Delivery has exactly three workflows: CLI update and develop auto-merge, develop-to-main PR creation with required checks, and main-push image/GitHub release.
  • The CLI update changes MULTICA_CLI_VERSION and increments the root patch VERSION together.
  • Bot-created PR checks are attached to the exact head through repository_dispatch; merging the main PR publishes the numeric and latest multi-platform GHCR tags.
  • A successful runtime release stops after publishing its image and GitHub Release; it does not invoke or authenticate to the Helm repository.
  • The Helm repository independently checks public GHCR hourly, or on manual workflow dispatch, and retains ownership of chart updates and releases when it discovers a newer stable runtime.
  • Merge develop-to-main promotion PRs with a merge commit so develop remains an ancestor of main; no recurring ancestry-sync workflow is needed.

Runtime

  • The chart runs one controller Deployment and shares one ordinary workspace claim with short-lived task Pods.
  • korioinc/helm is the sole owner of the chart source, rendering and schema validation, version updates, packaging, and publishing.
  • The controller uses HOME=/home/multica/agents and provider defaults. Do not add a controller-owned provider state root.
  • Codex reads shared configuration from $HOME/.codex; remove task-local CODEX_HOME overrides.
  • Pi uses $HOME/.pi/agent; do not set PI_CODING_AGENT_DIR. Treat provider configuration paths as relative to $HOME/.pi instead of adding agent during copy.
  • The workspace PVC is mounted at $HOME/.pi (.pi) and $HOME/.multica/pi-sessions (.multica/pi-sessions) in controller and task Pods.
  • Install declared Pi packages with the bundled pi install command instead of implementing package layout or reconciliation in Go.
  • Convert GITHUB_PAT_TOKEN, GITHUB_USER_NAME, and GITHUB_USER_EMAIL in daemonEnvironment: expose GH_TOKEN, use environment-scoped Git identity and gh auth git-credential, and rewrite GitHub SSH-style URLs to HTTPS so controller cache operations and provider child processes share one non-persistent authentication path.