Release v5.0.1

Documentation revision for Marketplace: use ALDC-5.0.1-docs.vsix, which includes the refreshed README and changelog. SHA256: 9573bee7d718a7ca81eb4b5a1cfb8123732c1babc77e0facec3e15e943367f9c.

This documentation-only rebuild comes from canonical ea0128167e9a6b26e9d495da0bee6fdb55e4b338 and extension 8e2dbb638ac9990c30c7f236c28a8fe683f89037, after the original v5.0.1 tag. Compared with the original VSIX, only the two README files, extension changelog and build provenance differ. The original tag and assets are retained. See the separate docs SHA256/provenance assets for this package. Marketplace publication is a separate step.

[5.0.1] - 2026-10-05

Changed

• Copilot Chat's installer projection selects Claude Sonnet 5.5 (copilot) for
  all 12 agents and five prompts with explicit models in BC28 and BC29-native.
  Model-less prompts inherit the selected agent; explicit handoff model overrides
  follow the same policy. Canonical shared agents and terminal model selections
  are unchanged.
• Chat AL tooling guidance distinguishes AL LSP, official AL MCP and terminal
  providers; grants remain role-scoped and build/publication human gates remain.
• Initialize can prepare an existing App/Test on the actual executing AL MCP
  connection without running full setup. Registration and retry are bounded;
  a parent connection does not establish readiness for a child agent.
• Installation, profile switching and rollback retain the consumer's existing
  .vscode/mcp.json. The extension packages the Chat projector and guide from
  matching clean canonical/extension inputs.

Tool availability and model execution require the host's actual capabilities.
Architect/Spec's BCQuality context path remains direct corpus reading; automatic
al-knowledge integration is not included in this release.

Fixed

• The al-symbols-mcp server never started, in any host. Every distribution
  launched it as npx -y @nicholasglazer/al-symbols-mcp, a package that does not
  exist in the npm registry: hosts reported CONNECTION_CLOSED on every session,
  so the AL symbol tools the agents declare were never actually reachable. The
  server keeps its name, so agent prose and tool allowlists are unchanged; only the
  package changes, to al-mcp-server@2.5.0 — the published package of
  StefanMaron/AL-Dependency-MCP-Server, which is the project this repository's
  own README has linked all along. Affected both the Claude Code plugin and the
  Copilot CLI distribution.

• microsoft-docs was broken in this repository's development config. The
  distributed manifests already used the official learn.microsoft.com/api/mcp
  endpoint; only the root .mcp.json, used by contributors working on ALDC, still
  pointed at another nonexistent package. Users were not affected.

• The installer could not verify itself from a real installation. Claude Code
  writes an .in_use lock into the installed plugin cache while a session holds
  the plugin, and verify() rejected any file absent from provenance.json. So
  init.js --verify — and the dry run — failed with Unexpected file in plugin payload precisely where the installer's own commands run. .in_use is now
  treated as derived, like __pycache__.

• Templates named a plans root that two surfaces do not use. Templates are
  copied byte for byte to every surface, by design: path rewriting belongs in the
  agent bodies that reference them. Nine of them still wrote .github/plans/…,
  which is right for Copilot and the VS Code extension and wrong for Claude Code
  (.claude/plans) and Codex (.agents/plans). The sharpest case was the BCQuality
  design guidance: the Architect was told to write bcq-constraints.md under its
  own root and, in the same step, bcq-selection.json under .github/plans — so
  the Spec Agent, reading plans.root, would not find the selection. Templates now
  name the root by its key, plans.root, and check-conformance.js rejects a
  template that fixes one again.

• external.bcquality.consumedBy omitted the Developer Reviewer, which runs the
  review path like the three agents listed. The list is informational; nothing
  reads it to decide behaviour.

Added

• A packaging test that asks the registry whether declared packages exist.
  scripts/test-mcp-packages.js runs in npm test and npm run validate. It
  checks shape offline (a distributed manifest must pin an exact version, never a
  floating dist-tag) and then resolves every npx-launched package against npm.
  When the registry is unreachable it says so and names each unverified package
  rather than passing quietly. Nothing before this asked whether a shipped package
  was real, which is why the defect above survived to release.

What's Changed

• docs: announce 5.0.0, and stop sending people to a tag that never existed by @javiarmesto in #107
• fix(mcp): ship an AL symbols package that exists, and let the installer verify itself by @javiarmesto in #108
• fix(codex): correct MCP guidance and verify configuration preservation by @javiarmesto in #110
• feat(cli): adaptar ALDC al host nativo de Copilot CLI by @javiarmesto in #109
• refactor(packaging): isolate surface generation and preserve VSIX inputs by @javiarmesto in #111
• feat(claude): integrate AL LSP and official AL MCP by role by @javiarmesto in #112
• feat(cli): integrate AL tooling and isolate audit persistence by @javiarmesto in #113
• feat(codex): adapt AL tooling scopes and document LSP integration gap by @javiarmesto in #114
• fix(templates): stop naming a plans root that two surfaces do not use by @javiarmesto in #117
• feat(chat): isolate AL LSP and MCP tooling for Copilot Chat by @javiarmesto in #115
• feat(initialize): prepare existing AL MCP projects across all surfaces by @javiarmesto in #116
• fix(chat): select Sonnet 5.5 in both Copilot Chat profiles by @javiarmesto in #118

Full Changelog: v5.0.0...v5.0.1