microsoft/agent-governance-toolkit

Package agent-governance Description The base wheel ships only agent_compliance. Both README quick-start imports work only after: pip install "agent-governance-toolkit[full]" Separately, once [full] is installed, importing agent_os emits: DeprecationWarning: agent-os-kernel is deprecated. Use agent-governance-toolkit-core instead. (docs/package-consolidation/MIGRATION.md) — but the README quick start (and several discussion examples) still reference the deprecated path. Suggested fixes Quick Start: pip install "agent-governance-toolkit[full]", or include the governance modules in the base wheel. Update quick-start imports to the canonical agent-governance-toolkit-core paths per MIGRATION.md. Happy to PR the README change if useful. Steps to Reproduce Repro (Python 3.12, pip 24): pip install agent-governance-toolkit # v4.1.0 python -c "from agentmesh.governance import govern" # ModuleNotFoundError: No module named 'agentmesh' python -c "from agent_os.policies import PolicyD

Found during a code-quality / docs pass. In agent_os/credential_redactor.py (around lines 101-199), redact() / redact_data_structure() iterate only PATTERNS (secret-like material), not PII_PATTERNS (email / phone / SSN / credit-card / IP). So PII is detected by find_pii_matches() but not removed by redact(). The class docstring's 'redact sensitive material' phrasing can lead a caller to assume PII is scrubbed when persisting/returning data. Suggestion: either add an opt-in redact_pii=True path, or clarify in the docstring that redact() is secrets-only. Separately, the SSN pattern here (\d{3}-\d{2}-\d{4}) is narrower than the one in integrations/base.py (which also accepts space/dot/no-separator) — reconciling to one shared pattern would avoid divergent detection.

Summary The examples/flowise-governance/flowise-flow.json shipped in #3105 fails to import on Flowise 2.x and 3.x. Reported by an external adopter (jinweida) via email after trying to import the file on both major versions. Root cause The JSON was authored by hand against Flowise's documented chatflow schema rather than exported from a running Flowise instance: Contains a non-standard top-level _comment key (real Flowise exports never include this). Node data (inputParams / baseClasses / anchors) does not match Flowise's live node registry, and every node is version: 1 regardless of the installed node versions. The _comment and README claim "Flowise 2.x / 3.x" but the file was never validated against a live import. For accuracy: it is a 5-node flow (chatInput, customFunction, httpRequest, customFunction, chatOutput), not the 9-node flow the merge note described. What works (no change needed) flowise-agentmesh package: GovernanceNode, AuditNode, RateLimiterNode, TrustGateNode all exi

Summary Hypervisor (and SagaOrchestrator) expose a mixed sync/async surface. Several methods are declared async def but never await anything, while sibling methods that operate on the same objects are plain def. This is a footgun: an un-awaited coroutine is silently truthy and the failure surfaces later, far from the call site. Important correction to the original framing The original report described this as an "annotation bug" (e.g. async def create_session(...) -> ManagedSession claiming a non-coroutine return). That part is not a bug: annotating an async def with the awaited type is correct Python, and type checkers (mypy/pyright) already understand the call returns a coroutine and would flag .session_id on an un-awaited result. Annotating these as Coroutine[...] / Awaitable[...] would actively mislead type checkers and should not be done. The genuine issues are: Async-without-await. In agent-governance-python/agent-hypervisor/src/hypervisor/core.py, create_session, join_session,

Summary Update MCP docs for issue #2597 after implementation lands so AGT documents stateless 2026-07-28 as the preferred behavior and 2025-11-25 as compatibility. Scope Update docs\tutorials\27-mcp-scan-cli.md. Update related MCP trust/security docs found during implementation. Stop describing Mcp-Session-Id as the normal scanner lifecycle. Distinguish AGT application-level auth/state helpers from MCP protocol sessions. Update ADR 0027 status only if maintainers want the implementation PR to carry that change. Testing Run relevant docs checks for edited files. Verify commands, links, and lifecycle descriptions match shipped behavior. Parent: #2597