ai-workflow-skill/docs/roadmaps/archive/rename-orchd-runtime-to-operator-api.md

Rename Operator API Runtime

Status

• completed

Owner

• Codex

Started At

• 2026-03-20

Goal

• Rename the package-owned web backend runtime from packages/orchd-runtime to packages/operator-api and rename its command entrypoint from cmd/orchd to cmd/operator-api so the current workspace no longer carries the ambiguous orchd name.

Scope

• rename the package directory and module path
• update imports, workspace metadata, and current docs
• validate the package-oriented build and test flows after the rename

Checklist

• inspect current orchd-runtime references
• rename the package directory and module path to operator-api
• update workspace metadata, imports, and current docs
• validate package-oriented Go tests and frontend build after the rename
• archive this roadmap and commit the completed rename

Files

• docs/roadmaps/archive/rename-orchd-runtime-to-operator-api.md
• go.work
• packages/operator-api/
• docs/implementation-roadmap.md
• docs/skill-workspace-monorepo.md
• docs/web-product-monorepo.md

Decisions

• rename both the package and the command entrypoint together so current source-of-truth code no longer carries the orchd name

Blockers

• none

Next Step

• continue feature work with packages/operator-api as the backend runtime name and avoid reintroducing the old orchd label

Completion Summary

• renamed the package-owned backend runtime from packages/orchd-runtime to packages/operator-api
• renamed the package-owned daemon entrypoint from cmd/orchd to cmd/operator-api
• updated current imports, workspace metadata, frontend copy, and current architecture docs to the new operator API name
• validated the renamed runtime through package-oriented Go tests, skill bundle packaging, and frontend build checks