chore: Rename packages

[dpup]

Handle package renaming while things are quiet.

[claude]

📦 Previous Review (superseded by newer review)

Pull Request Review: Package Rename

Summary

This PR performs a comprehensive package rename from github.com/andybons/moat to github.com/majorcontext/moat. The change is mechanical and affects 90 files, updating all Go import paths and documentation references.

Code Quality ✅

Strengths:

• Comprehensive coverage: The rename correctly updates all 90 files including:
  • go.mod module declaration
  • All Go source files (cmd/, internal/ packages)
  • Documentation (README.md, CONTRIBUTING.md)
  • Design documents in docs/plans/
• Consistent pattern: All changes follow the exact same pattern (andybons → majorcontext)
• No code logic changes: This is purely a refactoring with no behavioral changes
• Equal additions/deletions: 208 additions and 208 deletions indicates clean mechanical replacement

Potential Issues 🔍

Minor observations:

1. Historical plan documents contain old references: The following plan documents in docs/plans/ contain references to the old package path and username:

   • 2025-01-15-pluggable-secrets-impl.md
   • 2026-01-13-dependencies-plan.md
   • 2026-01-12-tamper-proof-logs-phase1.md
   • 2026-01-16-container-management-impl.md
   • 2025-01-12-hostname-routing-plan.md

   These files also contain references to agentops (the old project name) and local paths like /Users/andybons/dev/agentops/.

   Recommendation: These are historical documents capturing point-in-time work, so leaving them unchanged is reasonable. However, you may want to either:

   • Update them for consistency
   • Add a note that they're historical artifacts
   • Leave as-is (acceptable for historical docs)

2. Build verification: Unable to verify the build succeeds due to permission constraints, but the changes are mechanical and should compile correctly.

Security Concerns ✅

No security concerns. This is a straightforward package rename with no:

• Changes to authentication/authorization logic
• Modifications to credential handling
• Alterations to proxy security model
• Updates to audit logging

Performance Considerations ✅

No performance impact. Package names don't affect runtime performance, and no algorithmic changes were made.

Test Coverage ✅

All test files were updated with the new import paths:

• Unit test files: *_test.go files updated consistently
• E2E tests: internal/e2e/*_test.go files updated
• Test imports match production code imports

The test suite should continue to provide the same coverage as before.

Best Practices ✅

Follows Go conventions:

• Module path updated in go.mod
• All import paths consistently updated
• No breaking changes to public APIs (same package names)

Follows repository conventions:

• Commit message uses conventional commit format: chore: Rename packages
• Per CLAUDE.md guidelines, no Co-Authored-By line was added ✅
• Clear PR description

Recommendations

1. Verify build: Run go build ./... locally to confirm everything compiles
2. Run tests: Execute go test ./... to ensure all tests pass
3. Optional - Update historical docs: Decide on strategy for old plan documents (see issue feat(routing): add hostname-based service routing for agents #1 above)
4. Tag release: After merging, consider creating a release/tag to mark this organizational change
5. Update external references: Check if there are any external references (blog posts, docs sites, package registries) that need updating

Conclusion

This is a clean, well-executed package rename. The changes are comprehensive and consistent. The PR is ready to merge after verification that:

• Tests pass
• Build succeeds

Great work handling this organizational change while things are quiet!

[claude]

Pull Request Review: Package Rename

Overview

This PR performs a package rename from github.com/andybons/moat to github.com/majorcontext/moat. The changes are systematic and comprehensive, updating all import paths across the codebase.

Code Quality: ✅ Excellent

Strengths:

• Systematic approach: The rename consistently updates all Go import paths across 89+ files
• Documentation updated: README.md, CONTRIBUTING.md, and installation docs all reflect the new package path
• Module updated: go.mod correctly updated to the new module path
• Equal additions/deletions (208/208): Strong indicator this is a clean refactor with no functional changes

Consistency:

• All CLI command files properly updated
• All internal packages updated consistently
• Test files updated alongside implementation files
• Documentation plan files updated to match

Potential Issues: ⚠️ Minor

1. Incomplete documentation updates in historical plan files

Four older plan files still reference the previous project name "agentops" (not even "andybons/moat"):

• docs/plans/2026-01-13-dependencies-plan.md
• docs/plans/2026-01-16-container-management-impl.md
• docs/plans/2025-01-12-hostname-routing-plan.md
• docs/plans/2025-01-15-pluggable-secrets-impl.md

Recommendation: These are historical design documents, so the old references may be intentionally preserved. However, for consistency, consider either:

1. Updating these references to majorcontext/moat
2. Adding a note at the top indicating these are historical documents

2. Build/test verification

The PR description mentions "Handle package renaming while things are quiet" but doesn't include evidence of successful builds or test runs.

Recommendation: Verify that:

• go build ./... completes successfully
• go test ./... passes all tests
• E2E tests with -tags=e2e still work (if applicable in CI)

Security: ✅ No Concerns

• No code logic changes
• No new dependencies
• No credential handling modifications
• Pure refactoring operation

Best Practices: ✅ Excellent

• Follows Go module naming conventions
• Import path updates are atomic (all in one commit)
• No breaking API changes for internal code
• Matches the repository location (majorcontext/moat)

Performance: ✅ No Impact

No functional changes means no performance impact.

Test Coverage: ✅ Maintained

All test files updated alongside implementation files, maintaining existing test coverage.

Recommendations

1. Verify builds: Confirm go build ./... and go test ./... succeed
2. Consider historical docs: Decide whether to update the 4 plan files with old "agentops" references
3. Update CLAUDE.md: The CLAUDE.md file instructs not to include Co-Authored-By lines for Claude, which is good for this mechanical change

Verdict: ✅ LGTM with minor suggestions

This is a well-executed package rename. The changes are mechanical, systematic, and comprehensive. Once build/test verification is confirmed, this is ready to merge.

The rename aligns with the repository's new organization location and follows Go best practices for module paths.