Skip to content

chore: complete PyPI naming alignment — migrate 10 agentmesh_* modules to agent-governance-toolkit-* #2741

@jackbatzner

Description

@jackbatzner

Summary

Follow-up to #1597. The naming pass closed, but 10 modules under agent-governance-python/agent-os/modules/ still publish on PyPI under the agentmesh_* prefix even though the canonical project brand is agent-governance-toolkit. The folder name says agent-os, the wheel says agentmesh, and the recommended install surface says agent-governance-toolkit — three concentric brands ship today.

Affected packages

Folder Current PyPI name
agent-os/modules/amb agentmesh_message_bus
agent-os/modules/atr agentmesh_tool_registry
agent-os/modules/caas agentmesh_context
agent-os/modules/cmvk agentmesh_drift
agent-os/modules/control-plane agentmesh_control_plane
agent-os/modules/emk agentmesh_memory
agent-os/modules/iatp agentmesh_trust_protocol
agent-os/modules/mcp-kernel-server agentmesh_mcp_server
agent-os/modules/nexus agentmesh_nexus
agent-os/modules/observability agentmesh_observability

What needs to happen

For each module, decide and implement one of:

  • Rename in place — new distribution agent-governance-toolkit-<module>, old name becomes a dep-only redirect stub
  • Fold into umbrella — stop publishing the standalone distribution; consumers get the module via agent-governance-toolkit-core (or an extras group)
  • Hybrid — keep importable module path, expose via extras (pip install agent-governance-toolkit-core[message-bus])

A consistent answer across all 10 is preferable to per-module decisions.

Constraints

  • Old PyPI names need backwards-compat stubs through the deprecation window (see MIGRATION.md)
  • Whatever path is chosen should match the approach used in the package consolidation follow-up (sibling issue), to avoid stubbing the same names twice
  • PyPI namespace ownership for agent-governance-toolkit-* distributions should be confirmed before any rename lands

Out of scope

  • Source-tree (folder) rename → separate follow-up
  • Module-level convergence with parallel implementations in agent-mesh/src/agentmesh/ → tracked separately

Closes the unfinished tail of #1597.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions