# CLI 0.0.4-microsoft-preview.38

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

## Bounded discovery-component convergence

- Inventories every parser-backed BizTalk orchestration action recursively,
  including actions nested in scopes and branches, so valid nested source
  identifiers are no longer rejected or silently omitted.
- Adds revision-bound `lambogenius_correctDiscoveryComponents` corrections for
  a rejected component draft. The host returns exact missing and unknown source
  IDs, duplicate source mappings, transport/provenance conflicts, and exact
  binding-endpoint choices instead of asking the model to regenerate the full
  component document.
- Applies only explicit correction operations, rejects stale revisions, and
  reruns the original component, source-coverage, endpoint, architecture, and
  Mermaid checks before any corrected result is stored. Ambiguous endpoints
  require an explicit configured target; fuzzy endpoint matching is not used.
- Pins every correction revision to its stored Mermaid and accepts graph repair
  only as exact-prefix, append-only declarations and directed edges for
  reported IDs. Existing nodes and topology cannot be rewritten through the
  repair tool.
- Derives diagram-scope ownership from Mermaid parser events, so semicolons or
  newlines inside unquoted labels cannot hide duplicate node declarations in
  sibling subgraphs.
- Treats source-backed component IDs that collide with stored subgraph or edge
  IDs as bounded replacement work. Generated replacements reserve every
  existing Mermaid identifier and cannot reuse the collision.
- Permits explicitly requested host additions only for exact parser-backed
  source nodes and exact binding endpoints. If those additions change diagram
  coverage, the same bounded call must supply a complete validated Mermaid
  correction by preserving the stored diagram and appending source-grounded
  execution-flow arrows; the host does not manufacture isolated declarations
  or inferred message-flow edges.
- Commits the verified component set and matching Mermaid as one paired
  persistence operation. Staging or commit failures restore the complete prior
  pair rather than exposing a mixed discovery state.
- Keeps the verifier's structured issues in the persistent model correction
  reminder so an evicted rejection result cannot degrade into a generic retry.
- Anchors helper and executable grouping roles to the original rejected draft
  across an entire correction chain. A rejected intermediate assignment cannot
  flip those roles and then bypass the helper-group merge safeguards.

The preview.37 qualification run completed bounded flow grouping and consumed
the required binding, orchestration, and pipeline evidence. Discovery then
submitted the same 43-component payload on calls 16 through 19. The payload
contained missing nested actions, combined orchestration provenance and
physical endpoint mappings, and unresolved endpoint rows; the host correctly
rejected every attempt and stopped the unchanged model/tool loop. Preview.38
adds a compact, auditable correction route for that verified rejection instead
of increasing call limits or weakening source and transport validation.

## Verification and limits

- 189 Microsoft migration-core tests, 257 CLI tests, and 30
  release/installer/documentation tests pass. Repository lint, TypeScript
  compilation, all production builds, and the VS Code compatibility suite
  pass.
- Regression coverage inventories nested orchestration actions, preserves an
  invalid draft without file changes, rejects unscoped correction operations,
  requires an explicit architecture repair, and requires the original verifier
  to accept the completed result. Fault injection verifies paired-file rollback
  at every staging and commit point. Separate coverage prevents two-step
  grouping role flips, scoped declaration evasions, and reserved graph-ID
  deadlocks, and retains structured issues after history eviction.
- The failed preview.37 evidence remains under
  `failure-evidence/2026-09-22T00-58-25-preview37-component-loop` in the test
  workspace. It establishes an audited component-correction loop, not missing
  BizTalk source or successful discovery.
- A complete fresh FINACCONT2024Backup-BT migration with preview.38 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.38/install-cli.ps1' -OutFile install-cli-preview38.ps1
# Review the downloaded script before running it.
& .\install-cli-preview38.ps1 -SkipDependencies
li.cmd --version
```

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