# CLI 0.0.4-microsoft-preview.33

Microsoft migration engine preview. Stable `latest` remains 0.0.3.

## Source-grounded BizTalk discovery

- Requires every selected BizTalk binding artifact to be read directly and
  completely before discovery output can be stored. Endpoint copies enriched
  onto orchestration IR remain useful context, but cannot stand in for the
  physical binding evidence. Orchestration and pipeline IR must also be read
  completely, and partial documents resume by their exact document ID/offset
  instead of restarting page zero.
- Canonicalizes receive locations, receive/send ports, pipelines,
  orchestrations, maps, and schemas from the parsed source inventory instead
  of trusting model-authored summary lists.
- Requires each physical receive/send endpoint to carry a structured mapping
  to its exact binding artifact and endpoint ID, including the exact BizTalk
  adapter type. Target transports must follow configured architecture policy;
  an exact orchestration association cannot be claimed when the binding export
  exposes only application-level evidence.
- Keeps ODX receive/send shapes transport-neutral until the binding is joined.
  The host derives and persists transport context, canonicalizes native
  connector descriptions, and rejects native-connector gaps that recommend a
  custom connector or Azure Function. Generic parser hints can no longer turn
  FILE receives into HTTP triggers.
- Requires every parsed orchestration trigger and action to appear exactly
  once in both component and message-flow evidence using its top-level source
  artifact ID and IR component ID. Same-named shapes in separate
  orchestrations are therefore distinct, and component IDs must be globally
  unique.
- Rejects Mermaid node IDs explicitly declared in multiple subgraphs. Mermaid
  uses a diagram-global node namespace, so the previous behavior silently
  merged distinct BizTalk actions that happened to share a shape name. Root
  declarations and declarations immediately after arrows are included, and
  every source-backed component must have a matching explicit diagram node.
- Recomputes dependency severity counts, blocker totals,
  `allCriticalResolved`, and the summary after matching missing DLL claims to
  supplied source code. Persisted aggregates can no longer contradict their
  normalized dependency entries.

The preview.32 qualification run reached discovery finalization, but its
message-flow evidence omitted four of five orchestrations, represented eleven FILE
receive locations as HTTP, reused four component/Mermaid IDs across
orchestrations, and retained stale critical dependency totals after source
reclassification. The host incorrectly accepted that discovery. Preview.33
turns each observed defect into a deterministic validation or canonicalization
boundary rather than relying on another prompt-only retry.

## Verification and limits

- 160 Microsoft migration-core tests, 255 CLI tests, and 30
  release/installer/documentation tests pass. Repository lint, TypeScript
  compilation, all production builds, and 24 VS Code compatibility tests pass;
  one platform-specific extension test remains pending on Windows.
- Regression coverage includes direct-versus-enriched binding reads, contiguous
  evidence pagination, FILE-to-HTTP rejection, complete source-node coverage,
  unique component and Mermaid IDs, source-authoritative summaries, and healed
  dependency aggregates on resumed finalization.
- The failed preview.32 evidence remains under
  `failure-evidence/2026-09-21T20-01-19-preview32-discovery-fidelity` in the
  test workspace. It establishes invalid model output accepted by insufficient
  discovery validation, not absent source artifacts or a successful migration.
- Discovery now includes the complete source-to-Logic-Apps mapping prerequisite.
  A configuration capped at 131072 context tokens fails preflight rather than
  clipping those instructions; this qualification config's 262144 maximum is
  sufficient and the runtime allocation grows as the measured prompt requires.
- A complete fresh FINACCONT2024Backup-BT migration with preview.33 remains a
  post-publication qualification step. This release does not claim an Azure
  deployment, deployed Logic Apps runtime test, or business equivalence.

## PowerShell update

```powershell
Invoke-WebRequest 'https://tools.lambogenius.com/lambogenius-integration-migration/0.0.4-microsoft-preview.33/install-cli.ps1' -OutFile install-cli-preview33.ps1
# Review the downloaded script before running it.
& .\install-cli-preview33.ps1 -SkipDependencies
li.cmd --version
```

Expected version: `0.0.4-microsoft-preview.33`. This preview is not promoted to
the stable `latest` alias. Preserve existing reports and generated output before
upgrading. Use a fresh generated workspace because the Microsoft engine
fingerprint changed; do not edit fingerprint records to force checkpoint reuse.
Installation does not reset license counters.