$ the-wire · showcase
Policy engine pins agent-control-spec 0.4.0-alpha.4, deprecates REMOVED_MANIFEST_FIELDS
By RepoJournal · Filed · About Agent Security · Composed from the cited sources · methodology
The agent-governance-toolkit moved to agent-control-spec 0.4.0-alpha.4 and corrected the manifest fields its engine rejects, while the TypeScript 7 migration advanced scanner work first.
feat(policy-engine): upgrade ACS and clarify upstream ownership microsoft/agent-governance-toolkit
AGT now pins agent-control-spec to =0.4.0-alpha.4 while keeping agent-hooks-sdk at 0.1.0-alpha.5 and the existing host APIs unchanged. Previously the compatibility layer rejected URL sources that alpha.4 implements and could not pass download limits to the bundled dispatcher, so if you configure policy sources by URL, that path now works instead of being refused.
fix(policy-engine): record alpha.4 follow-ups from the ACS upgrade review (#4272) microsoft/agent-governance-toolkit
The review follow-ups from the ACS upgrade add UNSUPPORTED_MANIFEST_FIELDS, listing only system_prompt_file, and deprecate REMOVED_MANIFEST_FIELDS, which no longer describes what the engine rejects now that alpha.4 accepts bundle_url and system_prompt_url again. The old array keeps its shape for source compatibility, with a test pinning both constants, so switch any validation built on the remo...
chore(typescript): upgrade three packages to TypeScript 7 microsoft/agent-governance-toolkit
TypeScript moves to 7.0.2 across the SDK, Copilot extension, and MCP server without dropping test typechecking or ESLint compatibility. Because TypeScript 7 drops node10 module resolution and the TypeScript 6 compiler API that typescript-eslint and ts-jest rely on, and bare tsc is ambiguous with both compilers installed, the scanner compatibility prerequisite must merge first.
fix(supply-chain): verify npm aliases for TypeScript 7 migration microsoft/agent-governance-toolkit
The strict supply-chain scanners now verify canonical registry identities for the approved TypeScript 7 compiler and TypeScript 6 API npm aliases, which were previously queried as nonexistent packages while node_modules/typescript resolves to @typescript/typescript6. It is a scanner-only change that touches no dependency manifests or lockfiles.
