# CLI 0.0.4-microsoft-preview.43

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

## Atomic hybrid endpoint correction and candidate recovery

- Recognizes the exact BizTalk evidence case where a rejected component row
  combines invalid source-node provenance with a valid physical binding
  endpoint whose only mapping defect is its association.
- Exposes that compound repair explicitly with
  `requiresClearSourceProvenance=true`. The bounded correction must clear the
  reported source provenance and set
  `applyAuthoritativeTransportAssociations=true` in the same revision-bound
  call. Missing either half, adding an unrelated ID, or combining any other
  same-ID operation remains rejected.
- Derives the replacement association solely from parser-backed binding and
  orchestration port evidence. It cannot change endpoint identity, direction,
  adapter, source transport, target transport, or unrelated component fields.
- Reruns the complete component schema, source-evidence, transport, Mermaid,
  coverage, and execution-flow validators before the existing atomic
  component/architecture commit. Failed drafts and memory-only candidates do
  not reach disk.
- Establishes a safe baseline candidate from the exact stored Mermaid after
  bounded component operations validate. If a model prematurely uses
  `architectureMermaidAppend`, a copied or rewritten full diagram is rejected
  while the validated candidate and its exact missing/isolated IDs remain
  available for a small continuation.
- Makes premature reuse and missing-reuse responses actionable, preserves exact
  missing/isolated ID guidance whenever a candidate exists, and compares
  repeated authorized operations structurally rather than by JSON key order.
- Retains preview.42's bounded Mermaid continuation, preview.41's
  parser-authoritative transport checks, and preview.40's atomic
  grouped/ungrouped reconciliation.

The preview.42 FINACCONT2024Backup-BT qualification exposed 15 hybrid endpoint
rows in `flow-2-finance-orchestrations`. Calls 16 and 17 proved that clearing
their invalid source provenance revealed an association-only mismatch, but the
original correction scope could not authorize the parser-derived association
normalization in the same atomic attempt. Calls 20 through 23 then repeated a
full-diagram continuation without a candidate and were stopped without writes
or a success claim. Preview.43 adds only the narrowly scoped compound operation
needed by that preserved evidence; it does not relax endpoint matching or
Mermaid topology rules.

## Verification and limits

- 205 Microsoft migration-core tests, 257 CLI tests, and 30
  release/installer/documentation tests pass. The VS Code extension has 24
  passing tests and one expected pending POSIX-permission test on Windows;
  repository lint, TypeScript compilation, and production builds pass.
- Regression coverage includes hybrid/unknown-source endpoint rows, required
  clear-plus-association composition, apply-only and clear-only rejection,
  the archived false-flag rejection followed by its required true-flag repair,
  unrelated overlap rejection, valid-source hybrid splitting with regenerated
  source evidence, rewritten-full-append rejection with candidate retention,
  exact continuation guidance, and final atomic persistence.
- The failed preview.42 evidence remains under
  `failure-evidence/2026-09-22T14-10-54-preview42-discovery-continuation-without-candidate`
  in the test workspace.
- A complete fresh FINACCONT2024Backup-BT migration with preview.43 remains a
  post-publication qualification step.
- This preview 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.43/install-cli.ps1' -OutFile install-cli-preview43.ps1
# Review the downloaded script before running it.
& .\install-cli-preview43.ps1 -SkipDependencies
li.cmd --version
```

Expected version: `0.0.4-microsoft-preview.43`. 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.