Migrates go.mod + 22 Go imports + README + comments + generated config
templates off the dead github.com/Molecule-AI/ identity onto the vanity
host go.moleculesai.app, owned by us.
Surfaces touched:
- go.mod module declaration: github.com/Molecule-AI/molecule-cli ->
go.moleculesai.app/cli
- Every Go import statement under cmd/ + internal/
- README install section: rewritten to lead with the vanity install
command (the previous text was migration-in-progress hedging)
- Comment URLs in internal/backends/backend.go + internal/cmd/connect.go
(https://github.com/Molecule-AI/molecule-cli/issues/10) -> point at
git.moleculesai.app/molecule-ai/molecule-cli
- Generated config templates in internal/cmd/init.go +
internal/cmd/config.go: header URL updated so new users land on the
live SCM
- Adds internal/lint/import_path_lint_test.go — structural test that
walks every *.go / *.mod / Dockerfile / *.md / *.sh / *.yml in the
module and rejects future references to github.com/Molecule-AI/ or
Molecule-AI/molecule-monorepo. Mutation-tested before commit.
Test plan
- go build ./... clean
- go test ./... green (cmd/molecule + 5 internal packages + new lint
gate, all pass)
- TestNoLegacyGitHubImportPaths fails on injected canary, passes on
clean tree (no tautology)
Open dependency
- go.moleculesai.app responder must be deployed before
'go install go.moleculesai.app/cli/cmd/molecule@latest' works
externally. Internal builds + 'go build ./cmd/molecule' from a fresh
clone work today (self-referential module path).
- Responder code prepared (worker.js, vendor-portable for CF Workers /
Vercel Edge); deploy tracked separately under internal#71 phase 1.
Pairs with parallel migrations of plugin-gh-identity (#3) +
molecule-controlplane + molecule-core under the same internal#71 sweep.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
