chore(go-module): #1760 rename Go module to git.moleculesai.app/molecule-ai/molecule-core/workspace-server #1816

Merged

hongming merged 1 commits from chore/issue-1760-rename-go-module into main 2026-05-24 23:37:19 +00:00

Conversation 3 Commits 1 Files Changed 197

+410 -410

hongming commented 2026-05-24 23:22:24 +00:00

Owner

Copy Link

Copy Source

Summary

Closes #1760. Renames the workspace-server Go module from github.com/Molecule-AI/molecule-monorepo/platform to git.moleculesai.app/molecule-ai/molecule-core/workspace-server.

The old path was a holdover from the pre-2026-05-06 GitHub-suspension era when:

• The repo lived at github.com/Molecule-AI/molecule-monorepo
• The Go module was named for the platform/ subdirectory

Post-suspension:

• Canonical SCM is Gitea (git.moleculesai.app/molecule-ai/molecule-core)
• The workspace-server lives at workspace-server/ not platform/

This PR aligns the module path with reality.

Scope

Surface	Count
go.mod module declaration	1 line
Go import statements	194 files, 408 prefix occurrences
Dockerfile + Dockerfile.tenant -ldflags -X buildinfo.GitSHA=...	4 line edits
CI workflow sed patterns (weekly-platform-go.yml + ci.yml coverage filter)	2 lines
docs/memory-plugins/testing-your-plugin.md	1 reference

Net: 197 files, +410 / -410 (symmetric rename, zero logic changes).

Verification

• go mod tidy clean (no go.sum diff)
• go build ./... green across every package
• go test -short -count=1 ./... green across every package
• go vet ./... clean
• No external repos import the old path (verified against molecule-controlplane)
• /buildinfo runtime endpoint will continue reporting GitSHA after this lands (the -X linker flag was updated alongside the path)

Risk

• Anyone with a feature branch in flight will get import-path conflicts on rebase. They run the same find + sed on their branch and resolve cleanly.
• CI's go-build cache key invalidates — expected one-time miss.

SOP Checklist (RFC #351)

1. Comprehensive testing performed

• go build ./... green
• go test -short -count=1 ./... green (every package)
• go vet ./... clean
• go mod tidy no-op on go.sum

2. Local-postgres E2E run

N/A. Pure mechanical rename, zero behavior change.

3. Staging-smoke verified or pending

Pending merge + image build + tenant recycle. Will verify /buildinfo returns a valid SHA (not "dev").

4. Root-cause not symptom

Yes. The mismatched path was a known artifact of the GitHub→Gitea migration. Aligning module path → SCM URL → working tree layout removes the divergence.

5. Five-Axis review walked

Walked solo. Mechanical change with full test coverage. Happy to dispatch a reviewer for sign-off on the rename strategy.

6. No backwards-compat shim / dead code added

No shim, no dual-path support. The rename is one-shot.

7. Memory/saved-feedback consulted

• reference_post_suspension_pipeline — confirms Gitea SCM URL is the canonical target.
• feedback_per_agent_gitea_identity_default — N/A (rename is a single mechanical change, not a multi-agent surface).

🤖 Generated with Claude Code

## Summary Closes #1760. Renames the workspace-server Go module from `github.com/Molecule-AI/molecule-monorepo/platform` to `git.moleculesai.app/molecule-ai/molecule-core/workspace-server`. The old path was a holdover from the pre-2026-05-06 GitHub-suspension era when: - The repo lived at `github.com/Molecule-AI/molecule-monorepo` - The Go module was named for the `platform/` subdirectory Post-suspension: - Canonical SCM is Gitea (`git.moleculesai.app/molecule-ai/molecule-core`) - The workspace-server lives at `workspace-server/` not `platform/` This PR aligns the module path with reality. ## Scope | Surface | Count | |---|---| | `go.mod` module declaration | 1 line | | Go import statements | 194 files, 408 prefix occurrences | | Dockerfile + Dockerfile.tenant `-ldflags -X buildinfo.GitSHA=...` | 4 line edits | | CI workflow sed patterns (weekly-platform-go.yml + ci.yml coverage filter) | 2 lines | | docs/memory-plugins/testing-your-plugin.md | 1 reference | **Net: 197 files, +410 / -410 (symmetric rename, zero logic changes).** ## Verification - `go mod tidy` clean (no go.sum diff) - `go build ./...` green across every package - `go test -short -count=1 ./...` green across every package - `go vet ./...` clean - No external repos import the old path (verified against molecule-controlplane) - `/buildinfo` runtime endpoint will continue reporting GitSHA after this lands (the `-X` linker flag was updated alongside the path) ## Risk - Anyone with a feature branch in flight will get import-path conflicts on rebase. They run the same `find + sed` on their branch and resolve cleanly. - CI's go-build cache key invalidates — expected one-time miss. ## SOP Checklist (RFC #351) ### 1. Comprehensive testing performed - `go build ./...` green - `go test -short -count=1 ./...` green (every package) - `go vet ./...` clean - `go mod tidy` no-op on go.sum ### 2. Local-postgres E2E run N/A. Pure mechanical rename, zero behavior change. ### 3. Staging-smoke verified or pending Pending merge + image build + tenant recycle. Will verify `/buildinfo` returns a valid SHA (not "dev"). ### 4. Root-cause not symptom Yes. The mismatched path was a known artifact of the GitHub→Gitea migration. Aligning module path → SCM URL → working tree layout removes the divergence. ### 5. Five-Axis review walked Walked solo. Mechanical change with full test coverage. Happy to dispatch a reviewer for sign-off on the rename strategy. ### 6. No backwards-compat shim / dead code added No shim, no dual-path support. The rename is one-shot. ### 7. Memory/saved-feedback consulted - `reference_post_suspension_pipeline` — confirms Gitea SCM URL is the canonical target. - `feedback_per_agent_gitea_identity_default` — N/A (rename is a single mechanical change, not a multi-agent surface). 🤖 Generated with [Claude Code](https://claude.com/claude-code)

hongming added 1 commit 2026-05-24 23:22:24 +00:00

chore(go-module): #1760 rename Go module to git.moleculesai.app path ... a551f645c6

Renames the workspace-server Go module from
`github.com/Molecule-AI/molecule-monorepo/platform` to
`git.moleculesai.app/molecule-ai/molecule-core/workspace-server`.

The old path was a holdover from the pre-2026-05-06 GitHub-suspension
era when the repo lived at github.com/Molecule-AI/molecule-monorepo and
the Go module was named for the `platform/` subdirectory. Post-suspension
the canonical SCM is Gitea (git.moleculesai.app/molecule-ai/molecule-core)
and the workspace-server lives at `workspace-server/` not `platform/`,
so the module path should match reality.

## Scope

- go.mod module declaration: 1 line
- Go import statements: 194 files updated (408 occurrences, all
  prefix-only, mechanical find+sed)
- Dockerfile + Dockerfile.tenant: -ldflags references to buildinfo.GitSHA
  symbol (which is path-qualified)
- 2 CI workflow sed patterns: weekly-platform-go.yml + ci.yml's coverage
  filter (both used the lowercase variant from Go coverage reports)
- docs/memory-plugins/testing-your-plugin.md: 1 reference in plugin
  development docs

Net: 197 files, +410 / -410 (symmetric rename, no logic changes).

## Verification

- `go mod tidy` clean (no go.sum diff)
- `go build ./...` green
- `go test -short -count=1 ./...` green across every package
- `go vet ./...` clean
- No external repos import the old path (verified against molecule-controlplane)
- /buildinfo runtime endpoint will continue to report the GitSHA after
  this lands (the -X linker flag was updated alongside the path)

## Risk

- Anyone with a feature branch in flight will get import-path conflicts
  on rebase. They run the same sed on their branch and resolve cleanly.
- Cache invalidation in CI's go-build cache key — fine, expected.

Closes #1760.

devops-engineer approved these changes 2026-05-24 23:22:28 +00:00

devops-engineer left a comment

Member

Copy Link

Copy Source

Approving PR #1816: mechanical Go module rename to align with post-GitHub-suspension Gitea SCM. 197 files, symmetric +410/-410, all tests + vet green. CTO-bypass 2026-05-24.

Approving PR #1816: mechanical Go module rename to align with post-GitHub-suspension Gitea SCM. 197 files, symmetric +410/-410, all tests + vet green. CTO-bypass 2026-05-24.

core-devops approved these changes 2026-05-24 23:22:29 +00:00

core-devops left a comment

Member

Copy Link

Copy Source

Approving PR #1816: mechanical Go module rename to align with post-GitHub-suspension Gitea SCM. 197 files, symmetric +410/-410, all tests + vet green. CTO-bypass 2026-05-24.

Approving PR #1816: mechanical Go module rename to align with post-GitHub-suspension Gitea SCM. 197 files, symmetric +410/-410, all tests + vet green. CTO-bypass 2026-05-24.

agent-dev-a approved these changes 2026-05-24 23:28:54 +00:00

agent-dev-a left a comment

Member

Copy Link

Copy Source

Cross-author LGTM — clean implementation.

Cross-author LGTM — clean implementation.

hongming merged commit 8019231a16 into main 2026-05-24 23:37:19 +00:00

hongming referenced this issue from a commit 2026-05-24 23:37:21 +00:00

chore(go-module): #1760 rename Go module to git.moleculesai.app/molecule-ai/molecule-core/workspace-server (#1816)

hongming referenced this pull request 2026-05-24 23:43:07 +00:00

[main-red] molecule-ai/molecule-core: def18f28fa #1638

Sign in to join this conversation.

Reviewers

No Reviewers

devops-engineer

core-devops

agent-dev-a

Labels

Clear labels

area/ci

CI/CD pipeline issues

do-not-auto-merge

Opt out of autonomous merge-queue merging

kind/infrastructure

Infrastructure-related issues

merge-queue

Ready for serialized Gitea merge queue

merge-queue-hold

Temporarily hold PR in merge queue

platform/go

Go platform test issues

release-blocker

Blocks the staging→main promotion / a release

release-test

security

test-label-sre

tier:high

High risk per dev-sop §SOP-6 — ceo only, 24h cooldown

tier:low

Low risk per dev-sop §SOP-6 — engineers/managers/ceo can approve

tier:medium

Medium risk per dev-sop §SOP-6 — managers/ceo can approve

triage-test

test

wip

Work in progress — do not auto-merge

No Label

Milestone

No items

No Milestone

Projects

Clear projects

No project

Assignees

Clear assignees

agent-dev-a agent-dev-b agent-pm agent-researcher agent-reviewer agent-reviewer-1 agent-reviewer-cr2 app-fe (Molecule AI · app-fe) app-lead (Molecule AI · app-lead) app-qa (Molecule AI · app-qa) claude-ceo-assistant claude-ci-reader claude-status-reaper core-be (Molecule AI · core-be) core-devops (Molecule AI · core-devops) core-fe (Molecule AI · core-fe) core-lead (Molecule AI · core-lead) core-offsec (Molecule AI · core-offsec) core-qa (Molecule AI · core-qa) core-security (Molecule AI · core-security) core-uiux (Molecule AI · core-uiux) cp-be (Molecule AI · cp-be) cp-lead (Molecule AI · cp-lead) cp-qa (Molecule AI · cp-qa) cp-security (Molecule AI · cp-security) cui (Zhanlin Cui) dev-lead (Molecule AI · dev-lead) devops-engineer documentation-specialist (Molecule AI · documentation-specialist) fullstack-engineer (Molecule AI · fullstack-engineer) godwin hongming hongming-ceo-delegated hongming-codex-laptop hongming-kimi-laptop hongming-pc2 infra-lead (Molecule AI · infra-lead) infra-runtime-be (Molecule AI · infra-runtime-be) infra-sre (Molecule AI · infra-sre) integration-tester (Molecule AI · integration-tester) mc-drift-bot molecule-code-reviewer plugin-dev (Molecule AI · plugin-dev) pm publish-runtime-bot pypi-publisher (Molecule AI PyPI Publisher (RFC#596)) release-manager (Molecule AI · release-manager) sdk-dev (Molecule AI · sdk-dev) sdk-lead (Molecule AI · sdk-lead) sop-drift-bot sop-tier-bot (SOP Tier-Check Bot) technical-writer (Molecule AI · technical-writer) triage-operator (Molecule AI · triage-operator)

No Assignees

4 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: molecule-ai/molecule-core#1816