fix: pick up @alcops/core 0.2.0 (AL 18 flat VSIX layout); correct version docs

[Arthurvdv]

Picks up the AL 18 flat VSIX layout fix from @alcops/core 0.2.0 and fixes three documentation issues surfaced while diagnosing #47. Diff against main: package.json, package-lock.json, README.md, overview.md, CONTRIBUTING.md, .github/ARCHITECTURE.md. No workflow or task.json changes.

Problem

1. detectFrom: marketplace fails on AL Language 18.0.2668733 because the VSIX moved Microsoft.Dynamics.Nav.CodeAnalysis.dll from extension/bin/Analyzers/ to a flat extension/bin/ ([Bug]: Entry not found in ZIP: extension/bin/Analyzers/Microsoft.Dynamics.Nav.CodeAnalysis.dll #47). The task bundles @alcops/core 0.1.2, which only knows the legacy path.
2. The task log header reads Version: 1.0.5 while the extension on the Marketplace is 2.0.5, which looks like a version mismatch. It is not a bug: the task Major is deliberately pinned, and nothing documented that for users.
3. README.md documented the version input as latest / preview, but the task actually accepts latest / prerelease (see tasks/download/task.json helpMarkDown).

What was considered and rejected

The first commit on this branch (29fae26) stamped .version.Major from GitVersion and set "Major": 2 in all five task.json files, so the header would read 2.0.6. That is a breaking change: in Azure Pipelines the task Major is the @N in - task: ALCopsDownloadAnalyzers@1, so the next release would publish @2 and every pipeline pinned to @1 would fail to resolve the task unless a major-1 copy kept shipping alongside.

9d4fced reverts it. The task version stays independent of the extension version, matching what .github/ARCHITECTURE.md already described, and the behaviour is now explained in the user-facing docs instead.

Changes

• package.json / package-lock.json: @alcops/core ^0.1.2 → ^0.2.0 (fix: support AL 18 flat VSIX bin layout for marketplace/bc-artifact TFM detection npm-package#7). The lockfile change is limited to the @alcops/core entry.
• README.md: version input row now reads latest, prerelease.
• README.md + overview.md: note that both VSIX layouts of the AL Language extension are supported from @alcops/core 0.2.0 (the flat extension/bin/ used by AL 18+ / BC 29 and the legacy extension/bin/Analyzers/), plus a heads-up that compiling with AL 18 needs a .NET 10 runtime on the agent (out of scope here).
• README.md: new Versioning subsection under the task reference explaining that @1 is the task major version, that Version: 1.x.y in the log is the task's own version, and that it is intentionally independent of the 2.x extension version.
• overview.md: one-line version of the same note under Quick Start, where the Marketplace shows the 2.x extension version next to YAML that says @1.
• .github/ARCHITECTURE.md + CONTRIBUTING.md: spell out why task Major is pinned and what that means for the log header.

Verification

Run locally on Windows against the final branch state (after the bump):

• npx eslint shared/ tasks/*/src/ (expanded paths) — clean. npm run lint itself fails on Windows because npm shells out through cmd.exe, which does not expand the tasks/*/src/ glob; unaffected on the Linux CI runners.
• npx vitest run — 45/46 pass. The one failure, tests/download/task-runner.test.ts > calls executeDownload with detectUsing input, is pre-existing on main and Windows-only: the test asserts outputDir: '/build/src/.alcops' while path.join yields \build\src\.alcops. Not touched here.
• npm run build — clean.
• npm run bundle — 5 task bundles produced; tasks/download/dist/index.js contains the new multi-candidate VSIX probing from core 0.2.0.
• npm ls @alcops/core → @alcops/core@0.2.0.
• npx tfx extension create --manifest-globs vss-extension.json --output-path ./out — VSIX created successfully (run before the bump; CI repeats it).

Release

Merging and running "Release: Azure DevOps Extension" publishes 2.0.6 with the fix. The task header stays Version: 1.x.y by design.

Fixes #47

🤖 Generated with Claude Code