All published versions & release notes
0.0.4-microsoft-preview.43
Published 2026-09-22
# 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.
Version-pinned installation and checksum
wget -qO- https://tools.lambogenius.com/lambogenius-integration-migration/0.0.4-microsoft-preview.43/install-cli.sh | sh
Invoke-WebRequest 'https://tools.lambogenius.com/lambogenius-integration-migration/0.0.4-microsoft-preview.43/install-cli.ps1' -OutFile install-cli.ps1
./install-cli.ps1
SHA-256: 3d554fc9023f5a4a5b1bbe7f6b17a1c97f97e47e559412901db012f88d60beb4
0.0.4-microsoft-preview.42
Published 2026-09-22
# CLI 0.0.4-microsoft-preview.42
Microsoft migration engine preview. Stable `latest` remains 0.0.3.
## Deterministic discovery correction continuation
- Retains the best fully validated but incomplete component/architecture
correction in memory, bound to the exact correction revision, stored
architecture, and canonical corrected-component signature.
- Adds a small `architectureMermaidAppend` continuation so the model can supply
only the remaining declarations and source-grounded directed edges instead
of replaying a large diagram and losing verified progress.
- Separately reports missing declarations and already-declared isolated nodes;
continuation scope rejects unknown IDs, redeclarations, unrelated or self
edges, styling, subgraphs, directives, and Markdown fences.
- Forces the retained continuation once it exists and blocks message flow,
gaps, patterns, dependencies, finalization, and other discovery writes until
the exact component correction resolves. An explicitly stale stored
architecture can still establish a new architecture/component revision.
- Reruns the unchanged component schema, parser/source evidence, transport,
Mermaid grammar, append-only scope, declaration, and execution-flow checks
before committing components plus architecture through the existing atomic
paired store. Partial candidates never reach disk and the host invents no
graph edges.
- Retains preview.41's parser-authoritative transport-association repair and
preview.40's atomic grouped/ungrouped reconciliation.
The fresh preview.41 qualification reached a safe near-complete correction with
only `BT_ENDPOINT_015` unresolved. The model then lost that candidate, switched
briefly to message-flow authoring, corrupted one full-diagram replay, and
finally repeated the original 79-ID gap through calls 23 to 26. The host
rejected every attempt without changing the stored component/architecture pair
and stopped without claiming migration success. Preview.42 preserves that
validated progress and makes the only permitted next write a bounded Mermaid
continuation rather than increasing call limits or weakening evidence checks.
## Verification and limits
- 201 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 the exact near-complete-to-small-continuation
flow, mandatory correction continuity, declaration-only then edge-only
progress, unsafe continuation rejection, blocked message-flow diversion,
stale-revision rebase, and unchanged atomic persistence.
- The failed preview.41 evidence remains under
`failure-evidence/2026-09-22T12-25-33-preview41-discovery-mermaid-correction-loop`
in the test workspace.
- A complete fresh FINACCONT2024Backup-BT migration with preview.42 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.42/install-cli.ps1' -OutFile install-cli-preview42.ps1
# Review the downloaded script before running it.
& .\install-cli-preview42.ps1 -SkipDependencies
li.cmd --version
```
Expected version: `0.0.4-microsoft-preview.42`. 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.
Version-pinned installation and checksum
wget -qO- https://tools.lambogenius.com/lambogenius-integration-migration/0.0.4-microsoft-preview.42/install-cli.sh | sh
Invoke-WebRequest 'https://tools.lambogenius.com/lambogenius-integration-migration/0.0.4-microsoft-preview.42/install-cli.ps1' -OutFile install-cli.ps1
./install-cli.ps1
SHA-256: 403ead00d5ab62df128e6f2d3ce4d1715e4e63b5fc9d6c9ce3fdb476c4cc645c
0.0.4-microsoft-preview.41
Published 2026-09-22
# CLI 0.0.4-microsoft-preview.41
Microsoft migration engine preview. Stable `latest` remains 0.0.3.
## Parser-authoritative transport-association repair
- Adds a revision-bound component correction that changes only transport
associations proven by parsed BizTalk orchestration `portBindings` evidence.
- Reports the exact affected component IDs and expected association values, so
association-only mismatches can be repaired without replaying full component
inventories or selecting target transports.
- Suppresses source- and transport-clear suggestions when the corresponding
provenance or mapping field is absent.
- Accepts an authorized complete transport-mapping upsert as authoritative over
a redundant same-ID transport clear, while preserving all remove/upsert,
cross-clear, stale-revision, schema, source-evidence, Mermaid, and atomic
persistence safeguards.
- Updates the packaged BizTalk discovery guidance to require the bounded
authoritative operation for association-only mismatches.
- Retains preview.40's atomic grouped/ungrouped reconciliation and preview.39's
complete parser-proven shared-binding repair.
The fresh preview.40 qualification passed precheck, parsed all 180 selected
BizTalk artifacts, and verified grouping after 12 model/tool rounds. Discovery
then found 22 receive/send endpoints whose submitted `exact` association
contradicted direct application-level orchestration bindings. The model supplied
the correct replacement rows but paired them with redundant clears, later sent
out-of-scope rows, and finally repeated an unchanged no-op correction in calls
22 through 25. The host rejected every attempt atomically and stopped without
claiming success. Preview.41 makes that parser-owned correction bounded and
deterministic instead of increasing model-call limits or weakening validation.
## Verification and limits
- 197 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 association-only authoritative repair, bulk
endpoint correction, redundant-clear normalization, stale/no-op rejection,
both parser-proven association directions, mixed unresolved transport errors,
and preservation of unrelated fields and the stored Mermaid diagram.
- The failed preview.40 evidence remains under
`failure-evidence/2026-09-22T11-09-54-preview40-discovery-transport-association-loop`
in the test workspace. It establishes a model/tool convergence defect, not a
missing binding, missing dependency, or successful discovery.
- A complete fresh FINACCONT2024Backup-BT migration with preview.41 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.41/install-cli.ps1' -OutFile install-cli-preview41.ps1
# Review the downloaded script before running it.
& .\install-cli-preview41.ps1 -SkipDependencies
li.cmd --version
```
Expected version: `0.0.4-microsoft-preview.41`. 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.
Version-pinned installation and checksum
wget -qO- https://tools.lambogenius.com/lambogenius-integration-migration/0.0.4-microsoft-preview.41/install-cli.sh | sh
Invoke-WebRequest 'https://tools.lambogenius.com/lambogenius-integration-migration/0.0.4-microsoft-preview.41/install-cli.ps1' -OutFile install-cli.ps1
./install-cli.ps1
SHA-256: d9d69acbb77c9be06683047c6b0c5fded3fee443968f97d964fdd66547f50ccc
0.0.4-microsoft-preview.40
Published 2026-09-22
# CLI 0.0.4-microsoft-preview.40
Microsoft migration engine preview. Stable `latest` remains 0.0.3.
## Atomic grouped/ungrouped reconciliation
- Extends the revision-bound `applyAuthoritativeBindingMemberships` correction
to remove contradictory ungrouped markers only for artifacts already owned by
retained groups after assignments and helper-group merges.
- Preserves genuinely ungrouped artifacts and never invents or changes a group
destination from an ungrouped marker.
- Counts overlap reconciliation as real progress, rejects a true no-op without
advancing the correction revision, and reruns the unchanged strict Microsoft
grouping validator before storage.
- Updates the packaged BizTalk grouping guidance so the bounded operation and
its safety limits are explicit to the model.
- Retains preview.39's complete parser-proven shared-binding repair, atomic
discovery persistence, parser-backed Mermaid validation, and bounded Ollama
stream recovery.
The fresh preview.39 qualification run completed precheck and parsed all 180
selected BizTalk artifacts. Its ranged grouping proposal placed every artifact
in a flow and also marked indexes 0 through 179 ungrouped. The first correction
merged the helper-only flow and repaired the authoritative binding, but 179
stale ungrouped markers remained. Calls 4 through 10 repeatedly touched only
the already-correct binding, so the host stopped the loop on the first remaining
conflict, `BizTalk Financial Accounting.sln`, without claiming success.
Preview.40 reconciles that exact contradiction within the existing atomic
correction instead of increasing model-call limits or weakening source-evidence
validation.
## Verification and limits
- 193 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 the exact live merge-plus-binding correction,
preservation of a truly ungrouped artifact, flag-only overlap repair, and
true no-op rejection.
- The failed preview.39 evidence remains under
`failure-evidence/2026-09-22T09-53-11-preview39-grouping-ungrouped-loop` in
the test workspace. It establishes a model/tool convergence defect, not a
missing binding, missing dependency, or successful discovery.
- A complete fresh FINACCONT2024Backup-BT migration with preview.40 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.40/install-cli.ps1' -OutFile install-cli-preview40.ps1
# Review the downloaded script before running it.
& .\install-cli-preview40.ps1 -SkipDependencies
li.cmd --version
```
Expected version: `0.0.4-microsoft-preview.40`. 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.
Version-pinned installation and checksum
wget -qO- https://tools.lambogenius.com/lambogenius-integration-migration/0.0.4-microsoft-preview.40/install-cli.sh | sh
Invoke-WebRequest 'https://tools.lambogenius.com/lambogenius-integration-migration/0.0.4-microsoft-preview.40/install-cli.ps1' -OutFile install-cli.ps1
./install-cli.ps1
SHA-256: 1d9db8ec7a7049279ff79b4bd880591960d742e0cb75fa80ec36a495d2e58965
0.0.4-microsoft-preview.39
Published 2026-09-22
# CLI 0.0.4-microsoft-preview.39
Microsoft migration engine preview. Stable `latest` remains 0.0.3.
## Convergent authoritative-binding repair
- Returns every parser-proven BizTalk binding membership requirement together,
including the binding artifact ID, current owners, required owners, missing
owners, and the exact complete replacement `groupIds` list.
- Adds revision-bound `applyAuthoritativeBindingMemberships` to
`lambogenius_correctFlowGroups`. The operation only adds group memberships
established by exact binding-to-orchestration identity, preserves existing
optional owners, removes contradictory ungrouped membership, and reruns the
unchanged Microsoft grouping validator before storage.
- Keeps ordinary assignment semantics unchanged: `groupIds` remains the
complete intended owner set, never an implicit additive edit. Helper-group
merges and binding repair remain one atomic correction when both are needed.
- Updates the grouping instructions to prevent a shared binding from
oscillating between individually reported flows.
- Retains preview.38's bounded component correction, paired component/diagram
persistence, recursive source-action inventory, parser-backed Mermaid
safeguards, and bounded Ollama stream recovery.
The preview.38 qualification run completed precheck and parsed all 180 selected
BizTalk artifacts. During grouping, one authoritative binding named
orchestrations in both retained flows. Fail-fast feedback named only one missing
flow per round while correction assignments replace the complete owner set, so
calls alternated the binding between the two flows and calls 14 through 17
eventually repeated unchanged. The host stopped the loop and claimed no
migration success. Preview.39 exposes and applies the complete deterministic
binding assignment in one bounded operation instead of increasing call limits
or weakening transport-evidence validation.
## Verification and limits
- 191 Microsoft migration-core tests, 257 CLI tests, and 30
release/installer/documentation tests pass. Repository lint, TypeScript
compilation, and production builds pass.
- Regression coverage splits two parser-identified orchestrations into separate
flows behind one shared application binding, verifies the complete repair
suggestion, applies it atomically, and confirms both memberships are stored.
- The failed preview.38 evidence remains under
`failure-evidence/2026-09-22T03-31-22-preview38-grouping-binding-loop` in the
test workspace. It establishes a model/tool convergence defect, not a missing
binding, missing dependency, or successful discovery.
- A complete fresh FINACCONT2024Backup-BT migration with preview.39 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.39/install-cli.ps1' -OutFile install-cli-preview39.ps1
# Review the downloaded script before running it.
& .\install-cli-preview39.ps1 -SkipDependencies
li.cmd --version
```
Expected version: `0.0.4-microsoft-preview.39`. 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.
Version-pinned installation and checksum
wget -qO- https://tools.lambogenius.com/lambogenius-integration-migration/0.0.4-microsoft-preview.39/install-cli.sh | sh
Invoke-WebRequest 'https://tools.lambogenius.com/lambogenius-integration-migration/0.0.4-microsoft-preview.39/install-cli.ps1' -OutFile install-cli.ps1
./install-cli.ps1
SHA-256: fc7ed560eaeffbbb83410ae03df753de22fdc81f3f2b42d739d015ba1f3de43b
0.0.4-microsoft-preview.38
Published 2026-09-22
# 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.
Version-pinned installation and checksum
wget -qO- https://tools.lambogenius.com/lambogenius-integration-migration/0.0.4-microsoft-preview.38/install-cli.sh | sh
Invoke-WebRequest 'https://tools.lambogenius.com/lambogenius-integration-migration/0.0.4-microsoft-preview.38/install-cli.ps1' -OutFile install-cli.ps1
./install-cli.ps1
SHA-256: 669b72d8c5c2c9edefc7b6028c65860ac348a5c5ac380b60d56c01ef8b298381
0.0.4-microsoft-preview.37
Published 2026-09-22
# CLI 0.0.4-microsoft-preview.37
Microsoft migration engine preview. Stable `latest` remains 0.0.3.
## Bounded helper-group convergence
- Extends `lambogenius_correctFlowGroups` with revision-bound `mergeGroups`.
Each merge atomically moves every artifact from one helper-only source group
into an existing executable target group and removes the invalid source
definition before the original Microsoft grouping checks run again.
- Returns all structurally readable helper-only groups as `invalidGroups` and
all current orchestration- or binding-backed targets as
`executableGroupIds`. This lets one compact correction merge multiple helper
groups without enumerating artifact UUIDs or regenerating the complete
grouping document.
- Restricts merge sources to groups with no orchestration or binding and merge
targets to groups that already contain one. Executable flows cannot be
collapsed into each other, helper groups cannot receive merges, stale
revisions fail, and the full orchestration, binding, caller/callee, and
selected-artifact coverage checks remain mandatory.
- Distinguishes a repairable draft with an ungrouped entry point from a source
inventory containing no BizTalk orchestration or binding at all. The former
receives an exact assignment remedy; the latter must correct source
selection and cannot invent an executable flow.
- Retains preview.36's audited, one-round recovery for Ollama connection resets
and preview.35's range-bounded initial grouping transport.
The preview.36 qualification run submitted a bounded ranged draft and reached
normal correction calls, but three proposed groups contained only maps,
schemas, or custom code. The correction API could move individual artifacts
but could not delete a helper-only group definition. Calls 12 through 15
therefore repeated an operation that could never resolve
`flow-1-presto-processing`, and the host correctly stopped the model/tool loop.
Preview.37 provides the missing bounded structural operation instead of
increasing call limits or accepting an invalid group.
## Verification and limits
- 165 Microsoft migration-core tests, 257 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 begins with the ranged grouping tool, merges multiple
helper sources into one executable target, and verifies exact stored
membership. Negative coverage rejects executable sources, helper targets,
self-merges, stale revisions, unknown memberships, and inventories with no
possible executable entry point.
- The failed preview.36 evidence remains under
`failure-evidence/2026-09-21T23-39-42-preview36-grouping-helper-loop` in the
test workspace. It establishes a missing correction operation and an audited
model/tool stall, not absent BizTalk source or successful discovery.
- A complete fresh FINACCONT2024Backup-BT migration with preview.37 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.37/install-cli.ps1' -OutFile install-cli-preview37.ps1
# Review the downloaded script before running it.
& .\install-cli-preview37.ps1 -SkipDependencies
li.cmd --version
```
Expected version: `0.0.4-microsoft-preview.37`. 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.
Version-pinned installation and checksum
wget -qO- https://tools.lambogenius.com/lambogenius-integration-migration/0.0.4-microsoft-preview.37/install-cli.sh | sh
Invoke-WebRequest 'https://tools.lambogenius.com/lambogenius-integration-migration/0.0.4-microsoft-preview.37/install-cli.ps1' -OutFile install-cli.ps1
./install-cli.ps1
SHA-256: 81d9a784c8db61ed88792b6a1175b22d28b1fa5f932f52aa8f6d345f7d91bcea
0.0.4-microsoft-preview.36
Published 2026-09-21
# CLI 0.0.4-microsoft-preview.36
Microsoft migration engine preview. Stable `latest` remains 0.0.3.
## Audited Ollama connection-reset recovery
- Classifies an Ollama socket reset before response headers or during an
accepted response as an incomplete model stream. Any captured response is
retained in the engine audit as rejected output and is never parsed or
executed as a migration tool call.
- Reuses the existing bounded Microsoft tool-loop recovery: one fresh model
round may regenerate the current action, consumes the normal stage call
budget, and cannot continue the discarded partial JSON. A second consecutive
incomplete stream still fails closed.
- Preserves the original behavior and structured diagnostics for intentional
absolute/inactivity deadlines, malformed stream records, response-size
limits, non-success HTTP responses, and model output limits. These failures
are not relabeled as transient connection resets.
- Retains preview.35's ranged flow-group submission and targeted correction,
including exact global bounds and authoritative orchestration and binding
membership validation.
The preview.35 qualification run proved the ranged grouping transport worked:
the initial ranged submission and two targeted corrections reached normal tool
execution. During round 5, Ollama then reset the connection after 774 response
characters while generating another correction. The audit retained the partial
JSON with `toolExecuted: false`, but the raw `ECONNRESET` lacked the structured
incomplete-stream issue needed to invoke the already bounded recovery.
Preview.36 closes that transport-classification gap; it does not accept the
partial response or replay any tool side effect.
## Verification and limits
- 164 Microsoft migration-core tests, 257 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 destroys a local Ollama socket both before response
headers and after valid partial NDJSON, verifies the structured
`MODEL_STREAM_INCOMPLETE` result and rejected partial response, and confirms
the original timeout cases remain `MODEL_TIMEOUT` with truthful usage
accounting.
- The failed preview.35 evidence remains under
`failure-evidence/2026-09-21T23-04-32-preview35-ollama-econnreset` in the test
workspace. It establishes an external stream interruption after an
unexecuted partial model response, not missing BizTalk source or a completed
discovery stage.
- A complete fresh FINACCONT2024Backup-BT migration with preview.36 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.36/install-cli.ps1' -OutFile install-cli-preview36.ps1
# Review the downloaded script before running it.
& .\install-cli-preview36.ps1 -SkipDependencies
li.cmd --version
```
Expected version: `0.0.4-microsoft-preview.36`. 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.
Version-pinned installation and checksum
wget -qO- https://tools.lambogenius.com/lambogenius-integration-migration/0.0.4-microsoft-preview.36/install-cli.sh | sh
Invoke-WebRequest 'https://tools.lambogenius.com/lambogenius-integration-migration/0.0.4-microsoft-preview.36/install-cli.ps1' -OutFile install-cli.ps1
./install-cli.ps1
SHA-256: 7658de066b1f4aa96c54c8473dc6e29bd2487f12773acd273bdbe8eef0df1210
0.0.4-microsoft-preview.35
Published 2026-09-21
# CLI 0.0.4-microsoft-preview.35
Microsoft migration engine preview. Stable `latest` remains 0.0.3.
## Range-bounded flow grouping
- Adds `lambogenius_submitRangedFlowGroups`, which represents every
consecutive global artifact-index run as one inclusive `{start,end}` object.
Multiple ranges and a few optional sparse singleton indexes remain supported
without requiring the model to count through long numeric arrays.
- Advertises the exact global inventory bounds in the grouping result and next
action. Unknown, negative, and descending ranges fail before storage with the
valid bound, while overlap within one membership list remains idempotent.
- Makes the ranged tool mandatory in the bounded grouping prompt and after an
output-limit recovery. The recovery explicitly forbids another consecutive
`artifactIndexes` enumeration; partial output remains rejected and can never
reach tool execution.
- Retains preview.34's targeted membership repair, including unowned
orchestrations and authoritative BizTalk bindings, after a valid bounded
grouping draft reaches the host.
The preview.34 qualification run never reached a complete tool call. Both the
initial grouping response and its one permitted recovery began a compact-tool
envelope at index 170, counted beyond the valid maximum 179, and reached the
8,192-token output ceiling near index 1963. Neither partial response executed.
Preview.35 removes the sequential encoding that enabled that numeric generation
loop; the same intended run can be represented as `{ "start": 170, "end": 179 }`
and corrected against the host's exact range validation.
## Verification and limits
- 164 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 range expansion, overlap normalization,
canonical global indexes, out-of-bounds and descending ranges, and the exact
output-limit recovery instruction that mandates a ranged next call.
- The failed preview.34 evidence remains under
`failure-evidence/2026-09-21T22-31-07-preview34-grouping-output-limit` in the
test workspace. It establishes a bounded model-output failure, not missing
BizTalk source, insufficient context, or an executed partial response.
- A complete fresh FINACCONT2024Backup-BT migration with preview.35 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.35/install-cli.ps1' -OutFile install-cli-preview35.ps1
# Review the downloaded script before running it.
& .\install-cli-preview35.ps1 -SkipDependencies
li.cmd --version
```
Expected version: `0.0.4-microsoft-preview.35`. 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.Version-pinned installation and checksum
wget -qO- https://tools.lambogenius.com/lambogenius-integration-migration/0.0.4-microsoft-preview.35/install-cli.sh | sh
Invoke-WebRequest 'https://tools.lambogenius.com/lambogenius-integration-migration/0.0.4-microsoft-preview.35/install-cli.ps1' -OutFile install-cli.ps1
./install-cli.ps1
SHA-256: ad1b7e01da79c326294285e2d446ec77c06ffcda7235b11918b40214a4731e59
0.0.4-microsoft-preview.34
Published 2026-09-21
# CLI 0.0.4-microsoft-preview.34
Microsoft migration engine preview. Stable `latest` remains 0.0.3.
## Bounded BizTalk grouping recovery
- Treats repeated artifact indexes within one compact group or ungrouped list
as idempotent set membership. Unknown indexes, ownership conflicts between
groups, and grouped-versus-ungrouped conflicts still fail closed and receive
the original Microsoft grouping and coverage validation.
- Keeps a structurally valid compact grouping available for targeted repair
instead of forcing the model to regenerate every group after harmless
repeated indexes. The correction response now identifies authoritative
BizTalk bindings that have no group as well as orchestrations without their
required single owner.
- Makes the correction contract explicit: every orchestration must belong to
exactly one flow, every authoritative binding must belong to at least one
flow, and a repair must use the returned revision and existing group IDs.
- Updates the packaged BizTalk grouping procedure to prefer compact indexed
submission, use only global indexes from the complete inventory, and apply a
membership-only correction without repeating the graph or re-listing
evidence already returned.
The preview.33 qualification run's first grouping response reached its 8,192
token output limit and was rejected without execution. Its compact recovery
then repeated index ranges while leaving five orchestrations and the binding
ungrouped. The host classified the repeated memberships as non-repairable, so
the model re-read the graph and custom-code inventory before a second oversized
response failed the stage. Preview.34 preserves the compact draft as set
membership and returns the six exact ownership corrections needed for a small
follow-up call. It does not weaken source coverage or accept partial model
output.
## Verification and limits
- 162 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 the exact repeated-index support-group shape,
canonical global indexes in filtered inventory pages, orchestration and
binding conflict disclosure, and completion through one targeted correction.
- The failed preview.33 evidence remains under
`failure-evidence/2026-09-21T21-55-11-preview33-output-limit` in the test
workspace. It establishes a model/tool-control failure, not missing BizTalk
source, insufficient context, or an executed partial response.
- A complete fresh FINACCONT2024Backup-BT migration with preview.34 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.34/install-cli.ps1' -OutFile install-cli-preview34.ps1
# Review the downloaded script before running it.
& .\install-cli-preview34.ps1 -SkipDependencies
li.cmd --version
```
Expected version: `0.0.4-microsoft-preview.34`. 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.
Version-pinned installation and checksum
wget -qO- https://tools.lambogenius.com/lambogenius-integration-migration/0.0.4-microsoft-preview.34/install-cli.sh | sh
Invoke-WebRequest 'https://tools.lambogenius.com/lambogenius-integration-migration/0.0.4-microsoft-preview.34/install-cli.ps1' -OutFile install-cli.ps1
./install-cli.ps1
SHA-256: ce5fc277012dab59fbea9064b22a9c6ae14f4b83d955e4b769b1f22f3779a66c
0.0.4-microsoft-preview.33
Published 2026-09-21
# 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.
Version-pinned installation and checksum
wget -qO- https://tools.lambogenius.com/lambogenius-integration-migration/0.0.4-microsoft-preview.33/install-cli.sh | sh
Invoke-WebRequest 'https://tools.lambogenius.com/lambogenius-integration-migration/0.0.4-microsoft-preview.33/install-cli.ps1' -OutFile install-cli.ps1
./install-cli.ps1
SHA-256: 7673b126a136f9a536201f07170df07eab53146d89d2c8d97f8ea047dec3ed29
0.0.4-microsoft-preview.32
Published 2026-09-21
# CLI 0.0.4-microsoft-preview.32
Microsoft migration engine preview. Stable `latest` remains 0.0.3.
## Workflow Mermaid input compatibility
- Keep `input.mermaid` as the canonical top-level sibling of
`input.workflowDefinition`, and place it before the large workflow object in
the advertised tool schema. The tool description and BizTalk planning skill
now state that location explicitly.
- Accept the exact compatibility alias `input.workflowDefinition.mermaid` only
when top-level `input.mermaid` is absent. The host removes the alias from the
Logic Apps runtime wrapper before workflow validation and storage, while the
engine audit retains the raw submitted input and records which Mermaid
location was used.
- Continue to reject a missing, non-string, invalid, or conflicting diagram
without writing a workflow file. Lifting the alias does not correct or bypass
Logic Apps workflow validation, orchestration coverage, reference-evidence
requirements, connector checks, or Mermaid grammar validation.
The preview.31 qualification run completed Microsoft Discovery and advanced
through target architecture and reference lookup. Planning calls 25 through 27
then supplied the same valid 915-character diagram under
`workflowDefinition.mermaid` instead of at top-level `mermaid`. Schema
validation rejected all three before tool execution. No workflow file was
written. Preview.32 recognizes only that observed structural alias so the
existing strict workflow validator can report the remaining workflow-body
errors instead of terminating in a field-placement loop.
## Earlier reliability fixes retained
This preview retains preview.31's bounded, audited recovery for an Ollama 2xx
stream that ends without `done: true`, and preview.30's deterministic Mermaid
repair for quoted or space-containing endpoints on labelled solid, dotted, and
thick links. Partial model output still cannot reach tool execution, and
ambiguous Mermaid labels are never resolved arbitrarily.
## Verification and limits
- 149 Microsoft migration-core tests, 254 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.
- Coverage includes nested-alias canonicalization, canonical storage, missing
diagrams, non-string aliases, invalid Mermaid, conflicting duplicate values,
and preservation of the no-write boundary for rejected submissions.
- The failed preview.31 reports and stage audits are preserved under
`failure-evidence/2026-09-21T18-01-41-preview31-workflow-mermaid-invalid` in
the test workspace. They establish a model tool-shape error, not absent
source evidence or a successfully stored workflow.
- A complete fresh FINACCONT2024Backup-BT migration with preview.32 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.32/install-cli.ps1' -OutFile install-cli-preview32.ps1
# Review the downloaded script before running it.
& .\install-cli-preview32.ps1 -SkipDependencies
li.cmd --version
```
Expected version: `0.0.4-microsoft-preview.32`. 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.
Version-pinned installation and checksum
wget -qO- https://tools.lambogenius.com/lambogenius-integration-migration/0.0.4-microsoft-preview.32/install-cli.sh | sh
Invoke-WebRequest 'https://tools.lambogenius.com/lambogenius-integration-migration/0.0.4-microsoft-preview.32/install-cli.ps1' -OutFile install-cli.ps1
./install-cli.ps1
SHA-256: eb9b9b393b49e2ab4dd8ca14a7bf6e67f7f059934e8f4a9717102c5a753bd0e6
0.0.4-microsoft-preview.31
Published 2026-09-21
# CLI 0.0.4-microsoft-preview.31
Microsoft migration engine preview. Stable `latest` remains 0.0.3.
## Audited Ollama stream recovery
- Treat a successful Ollama HTTP response that ends without its required final
`done: true` record as a structured `MODEL_STREAM_INCOMPLETE` failure. The
accumulated response remains rejected and cannot reach tool validation or
execution.
- Preserve the incomplete response and diagnostic as a distinct engine-audit
round, count its estimated token usage, and permit one fresh model round for
the same current-stage action. Two consecutive incomplete streams still fail
closed, and the retry cannot exceed the existing stage round limit.
- Reset the consecutive recovery allowance only after a complete model
response. This permits separate transient interruptions during a long stage
without creating an unbounded retry loop.
- Accept only 2xx Ollama generation responses. Redirects and other non-2xx
responses now report their HTTP status instead of being misclassified as a
missing completion marker.
- Count an empty 2xx stream that lacks its completion marker as an estimated
provider invocation, so retry and failure reports do not hide an attempted
model call.
The preview.30 qualification run completed grouping and the full Microsoft
Discovery stage, including the architecture that preview.29 rejected. Planning
also stored its target architecture, then Ollama planning call 11 ended after
84.791 seconds with valid partial NDJSON but no terminal completion record. The
host executed no tool and rejected the partial response. Preview.31 adds the
bounded, audited recovery for exactly that pre-tool condition.
## Mermaid labelled-edge recovery retained
This preview includes preview.30's deterministic repair for quoted or
space-containing Mermaid endpoints on labelled solid, dotted, and thick links.
When a label has one declared node ID, its edges reconnect to that ID instead
of creating a duplicate logical orchestration. Undeclared and ambiguous labels
retain stable, fail-closed handling through the pinned Mermaid grammar.
## Verification and limits
- 149 Microsoft migration-core tests and 254 CLI tests pass, including bounded
retry, audit separation, round-limit, repeated-interruption, redirect, empty
stream accounting, and the exact Mermaid regression coverage.
- The failed preview.30 reports and stage audit are preserved under
`failure-evidence/2026-09-21T16-43-41-preview30-ollama-stream` in the test
workspace. They establish a provider-stream interruption, not a missing
BizTalk dependency or an executed partial tool call.
- A complete fresh FINACCONT2024Backup-BT migration with preview.31 remains a
post-publication qualification step. This release does not claim a 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.31/install-cli.ps1' -OutFile install-cli-preview31.ps1
# Review the downloaded script before running it.
& .\install-cli-preview31.ps1 -SkipDependencies
li.cmd --version
```
Expected version: `0.0.4-microsoft-preview.31`. 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.
Version-pinned installation and checksum
wget -qO- https://tools.lambogenius.com/lambogenius-integration-migration/0.0.4-microsoft-preview.31/install-cli.sh | sh
Invoke-WebRequest 'https://tools.lambogenius.com/lambogenius-integration-migration/0.0.4-microsoft-preview.31/install-cli.ps1' -OutFile install-cli.ps1
./install-cli.ps1
SHA-256: 9e416781665896c4991e2cd41f7c031b186fee66767f9f9c22ee2718dbcd002d
0.0.4-microsoft-preview.30
Published 2026-09-21
# CLI 0.0.4-microsoft-preview.30
Microsoft migration engine preview. Stable `latest` remains 0.0.3.
## Mermaid labelled-edge recovery
- Normalize quoted or space-containing node endpoints used with Mermaid's
labelled solid, dotted, and thick link forms before pinned grammar
validation. Edge labels remain labels and are never converted into nodes.
- Resolve an endpoint label to its unique declared node ID when one exists. For
example, an edge from `"ParkedAccDocWorkflow"` now reconnects to the declared
`Orch1["ParkedAccDocWorkflow"]` node instead of creating a duplicate logical
orchestration.
- Retain deterministic hashed-node fallback for undeclared labels, but never
choose arbitrarily between duplicate declarations. Quoted subgraph titles and
commented-out declarations are excluded from endpoint resolution.
- Keep normalization idempotent and fail closed through the pinned Mermaid
parser. Malformed labelled links remain rejected and cannot replace a stored
architecture.
The FINACCONT2024Backup-BT discovery audit submitted the same rejected diagram
in calls 11 through 14. Its ten outbound routes used quoted orchestration labels
as endpoints before `-- "Orchestration Port Binding ..." -->` links. The exact
captured payload now validates with those routes connected to `Orch1` through
`Orch5`, without creating duplicate nodes. The existing model-loop guard and
rejection audit remain unchanged and continue to stop genuinely unchanged,
unrepairable submissions.
## Verification and limits
- 146 Microsoft migration-core tests, 252 CLI tests, and 30
release/installer/documentation tests pass. Repository lint, TypeScript
compilation, all workspace tests, and production builds pass; the VS Code
compatibility suite has 24 passing tests and one platform-specific pending
test.
- The exact archived failing Mermaid payload passes the pinned grammar after
deterministic normalization, retains all five Presto and five SAP routing
links, and does not introduce duplicate orchestration nodes.
- This release does not claim a completed live FINACCONT2024Backup-BT
migration, deployed Logic Apps runtime test, or business equivalence. Those
require the fresh post-publication qualification run and deployment-specific
validation.
## PowerShell update
```powershell
Invoke-WebRequest 'https://tools.lambogenius.com/lambogenius-integration-migration/0.0.4-microsoft-preview.30/install-cli.ps1' -OutFile install-cli-preview30.ps1
# Review the downloaded script before running it.
& .\install-cli-preview30.ps1 -SkipDependencies
li.cmd --version
```
Expected version: `0.0.4-microsoft-preview.30`. This preview is not promoted to
the stable `latest` alias. Preserve existing reports and generated output before
upgrading. Use a fresh generated workspace for qualification because the
Microsoft engine fingerprint changed; do not edit fingerprint records to force
checkpoint reuse. Installation does not reset license counters.
Version-pinned installation and checksum
wget -qO- https://tools.lambogenius.com/lambogenius-integration-migration/0.0.4-microsoft-preview.30/install-cli.sh | sh
Invoke-WebRequest 'https://tools.lambogenius.com/lambogenius-integration-migration/0.0.4-microsoft-preview.30/install-cli.ps1' -OutFile install-cli.ps1
./install-cli.ps1
SHA-256: dcf24a9de194c9bb6eda09ee7866eb7934a82ed71921d4e62b0e21678939a9a6
0.0.4-microsoft-preview.29
Published 2026-09-21
# CLI 0.0.4-microsoft-preview.29
Microsoft migration engine preview. Stable `latest` remains 0.0.3.
## Exact connector and transform evidence
- Require the complete set of ServiceProvider `inputs.parameters` names to
exactly match one fully read eligible packaged workflow reference. A payload
can no longer add undocumented parameters to an otherwise proven connector
shape.
- For a File System `whenFilesAre*` polling trigger feeding XSLT, require every
XSLT action to reference a documented `getFileContent*` action in
`inputs.content` and to name that same action in `runAfter`.
- Require the file-content action and its XSLT consumer to be in the same action
scope using the actual action-container identity, not a display path. An
unrelated or nested get-file-content action cannot satisfy the transform
guard, even when different scopes have colliding labels.
- Accept the linkage only from a real Workflow Definition Language expression
and a `runAfter` status containing `Succeeded`; literal text, empty status
lists, and failure-only dependencies do not prove that file bytes are
available.
- Exclude packaged negative fixtures such as `BadRequest`, invalid, and
incorrect examples from connector evidence. A present `inputs.parameters`
value must be an object; malformed reference values cannot become an empty
parameter shape.
These checks harden the planning-workflow correction introduced in preview.28.
They prevent a superficially present connector action from authorizing a
workflow whose XSLT still consumes File System trigger metadata instead of file
bytes.
## Verification and limits
- 143 Microsoft migration-core tests and 252 CLI tests pass. Repository lint,
TypeScript compilation, all workspace tests, and production builds pass; the
VS Code compatibility suite has 24 passing tests and one platform-specific
pending test.
- The release/installer/documentation suite has 30 passing tests. The packaged
archive, public asset manifest, and isolated public installation are verified
as part of publication.
- This release does not claim a completed live FINACCONT2024Backup-BT migration,
deployed Logic Apps runtime test, or business equivalence. Invalid or
source-incomplete model output still fails closed.
## PowerShell update
```powershell
Invoke-WebRequest 'https://tools.lambogenius.com/lambogenius-integration-migration/0.0.4-microsoft-preview.29/install-cli.ps1' -OutFile install-cli-preview29.ps1
# Review the downloaded script before running it.
& .\install-cli-preview29.ps1 -SkipDependencies
li.cmd --version
```
Expected version: `0.0.4-microsoft-preview.29`. This preview is not promoted to
the stable `latest` alias. Preserve existing reports and generated output. Use a
fresh generated workspace for qualification because the Microsoft engine
fingerprint changed; do not edit fingerprint records to force checkpoint reuse.
Installation does not reset license counters.
Version-pinned installation and checksum
wget -qO- https://tools.lambogenius.com/lambogenius-integration-migration/0.0.4-microsoft-preview.29/install-cli.sh | sh
Invoke-WebRequest 'https://tools.lambogenius.com/lambogenius-integration-migration/0.0.4-microsoft-preview.29/install-cli.ps1' -OutFile install-cli.ps1
./install-cli.ps1
SHA-256: 69d124688f65da8d81cd018eccb6be829f212f4e3a4d5b2f363471430b3111b7
0.0.4-microsoft-preview.28
Published 2026-09-21
# CLI 0.0.4-microsoft-preview.28
Microsoft migration engine preview. Stable `latest` remains 0.0.3.
## Planning workflow correction
- Prevent repeated `migration_planning_storeWorkflowDefinition` submissions from
hiding the underlying validation problem. Structured schema errors and the
concrete repair action remain in subsequent prompts and in a terminal
`MODEL_TOOL_LOOP` report.
- Return all side-effect-free workflow corrections together before writing a
planning file. This includes misplaced `/actions/metadata`, invalid runtime
types such as `Decision`, malformed ServiceProvider and XSLT inputs,
undeclared parameters or variables, missing source coverage, and missing or
invalid per-workflow Mermaid.
- Normalize legacy bare definitions to a complete Stateful `workflow.json`
wrapper so orchestration coverage pointers continue to address
`/definition/actions` and `/definition/triggers`.
- Require a successful documentation search and complete reference-document
read, plus a workflow-reference search and complete workflow read, before the
planning host accepts a workflow definition. Search-only or tail-page reads do
not satisfy the prerequisite.
- For every ServiceProvider trigger/action, require a fully read eligible
packaged example with the exact trigger/action role, provider ID, operation ID,
and compatible parameter shape. Incorrect reference fixtures cannot authorize
an operation, and File System metadata triggers cannot feed XSLT directly
without a documented get-file-content action.
## Fail-closed runtime validation and resume
- Use runtime JSON type `If` for source/Designer labels such as Decision or
Condition, and `Workflow` for child-workflow calls. Invalid aliases are
rejected with their exact replacement rather than retained as warnings.
- Validate File System ServiceProvider configuration and polling recurrence,
XSLT `content` plus `map`, control-action containers, `runAfter` dependencies,
migration metadata, and parameter/variable declarations.
- Require a Mermaid diagram for every planned workflow, including the first,
and require one migration correlation ID/timestamp across the flow.
- A workflow stored by an older preview is not counted as completed coverage if
it is a bare definition, lacks Mermaid, or fails the strengthened validator. The
next action names that workflow and directs the model to repair it under the
same name instead of silently skipping it or creating duplicate coverage.
- Obsolete invalid workflow files that cannot be repaired in place can be moved
out of the active plan by a host-gated archive tool. The original file remains
preserved under `invalid-workflows`; valid workflow files cannot be archived.
The reported FINACCONT2024Backup-BT audit placed `MigrationMetadata` under
`actions` on call 13 and repeated the identical rejected payload through call
16. Its preceding stored workflow also used the non-runtime `Decision` type.
Regression tests reproduce both checkpoint states and verify that neither can
be finalized as a runnable migration plan.
## Verification and limits
- 142 Microsoft migration-core tests and 252 CLI tests pass. Repository lint,
TypeScript compilation, all workspace tests, and production builds pass; the
VS Code compatibility suite has 23 passing tests and one platform-specific
pending test.
- Representative packaged File System trigger/create-file and XSLT reference
workflows pass the strengthened validator after migration metadata is added.
- All 147 previously published public assets through preview.27 matched the
local staging tree byte-for-byte over HTTPS before this release was added.
- This release does not claim a completed live FINACCONT2024Backup-BT migration,
deployed Logic Apps runtime test, or business equivalence. Invalid or
source-incomplete model output still fails closed.
## PowerShell update
```powershell
Invoke-WebRequest 'https://tools.lambogenius.com/lambogenius-integration-migration/0.0.4-microsoft-preview.28/install-cli.ps1' -OutFile install-cli-preview28.ps1
# Review the downloaded script before running it.
& .\install-cli-preview28.ps1 -SkipDependencies
li.cmd --version
```
Expected version: `0.0.4-microsoft-preview.28`. This preview is not promoted to
the stable `latest` alias. Preserve existing reports and generated output. The
new host can identify and request repair of stale invalid planning workflows,
but a fresh generated workspace remains the cleanest qualification path because
the Microsoft engine fingerprint changed. Do not edit fingerprint records to
force checkpoint reuse. Installation does not reset license counters.
Version-pinned installation and checksum
wget -qO- https://tools.lambogenius.com/lambogenius-integration-migration/0.0.4-microsoft-preview.28/install-cli.sh | sh
Invoke-WebRequest 'https://tools.lambogenius.com/lambogenius-integration-migration/0.0.4-microsoft-preview.28/install-cli.ps1' -OutFile install-cli.ps1
./install-cli.ps1
SHA-256: 946fae24f5651a34bd284c9da94ddcd1cdf10bbebd49f434d011a7b5c01073a7
0.0.4-microsoft-preview.27
Published 2026-09-21
# CLI 0.0.4-microsoft-preview.27
Microsoft migration engine preview. Stable `latest` remains 0.0.3.
## Mermaid link-style recovery
- Recover target architecture diagrams when Mermaid 11 reports its opaque
`Cannot set properties of undefined (setting 'style')` error because the
model supplied `linkStyle` indexes that do not identify real edges.
- Retry the exact normalized graph without presentation-only `linkStyle`
directives. The repair is accepted only when the pinned Mermaid grammar then
validates the diagram; nodes, edges, labels, and architecture content are not
changed.
- Prevent the planning model from spending repeated long calls resubmitting the
same otherwise-valid architecture until the host's `MODEL_TOOL_LOOP` guard
stops the stage.
The reported FINACCONT-BT planning audit contained 28 graph edges and 201
`linkStyle` directives, reaching index 200. The regression test reproduces the
same out-of-range styling failure class and verifies that only presentation
directives are removed.
## Microsoft stage safeguards
- Treat matching custom source code anywhere in the selected migration
inventory as available migration input instead of persisting it as a missing
binary dependency merely because it is outside the current flow group.
- Reject helper/library-only flow groups without an executable BizTalk entry
point, require every selected artifact to be grouped or explicitly ungrouped,
keep caller/callee orchestrations together, and revalidate resumed grouping
caches before later stages can use them.
- Require a distinct runnable Logic Apps workflow for every selected source
orchestration, including child, parked, and error workflows. Existing workflow
names cannot be overwritten in a way that silently removes verified source
coverage.
## Verification and limits
- 131 Microsoft migration-core tests, 252 CLI tests, and 30 public
release/installer/documentation tests pass. CLI lint, TypeScript compilation,
and the production build also pass.
- All 141 previously published assets through preview.26 matched the local
staging tree byte-for-byte over HTTPS before this release was added.
- The Mermaid fallback does not accept a malformed graph: if parsing still
fails after presentation-only link styling is removed, the architecture is
rejected and no planning file is changed.
- No live end-to-end customer migration, deployed Logic Apps runtime test, or
business-equivalence test was performed for this release.
## PowerShell update
```powershell
Invoke-WebRequest 'https://tools.lambogenius.com/lambogenius-integration-migration/0.0.4-microsoft-preview.27/install-cli.ps1' -OutFile install-cli-preview27.ps1
# Review the downloaded script before running it.
& .\install-cli-preview27.ps1 -SkipDependencies
li.cmd --version
```
Expected version: `0.0.4-microsoft-preview.27`. This preview is not promoted to
the stable `latest` alias. Preserve existing reports and generated output, then
use a fresh generated workspace because Microsoft engine changes participate in
migration fingerprints. Do not edit fingerprint records to force checkpoint
reuse. Installation does not reset license counters.
Version-pinned installation and checksum
wget -qO- https://tools.lambogenius.com/lambogenius-integration-migration/0.0.4-microsoft-preview.27/install-cli.sh | sh
Invoke-WebRequest 'https://tools.lambogenius.com/lambogenius-integration-migration/0.0.4-microsoft-preview.27/install-cli.ps1' -OutFile install-cli.ps1
./install-cli.ps1
SHA-256: ecfbe444ec09a5d96b6b9dbdb97b75a3333a0a0b152dd0ede3ba36149d3f1943
0.0.4-microsoft-preview.26
Published 2026-09-15
# CLI 0.0.4-microsoft-preview.26
Microsoft migration engine preview. Stable `latest` remains 0.0.3.
## Optional configuration v3 extensions
- Add configuration version 3 with optional, additive standards-document and
skill packs routed independently to discovery, planning, and conversion.
- Preserve the pinned Microsoft stage prompts when extensions are absent,
globally disabled, or individually disabled.
- Fail before a model call when an enabled resource is missing, linked,
oversized, non-UTF-8, or outside its declared pack root. Extension bytes and
hashes participate in context-capacity checks and checkpoint fingerprints.
- Keep starter templates, IaC catalogs, pipeline repositories, standards, and
skills optional. `li config init` emits a Microsoft-only v3 configuration;
v3 continues to support batch execution and optional starter scaffolding.
## Repository provider metadata
- Repository entries may optionally declare `provider: azure-devops`, `github`,
`gitlab`, `bitbucket`, or `generic-git`.
- Provider metadata is validated, supplied to Microsoft agent stages when
configured, and recorded in deployment-package provenance.
- Repository hosting remains separate from the deployment runner. The field
does not clone a repository, authenticate to a host, infer pipeline syntax,
or authorize deployment. Omission retains existing local/unknown behavior.
- Document that `migration.applicationRepository` is a required reference to a
key under `repositories`, not a path or enum. It targets a read-only starter
when scaffolding is enabled and a prepared writable output otherwise.
## Verification and limits
- 124 Microsoft migration-core tests, 252 CLI tests, and 30 public
release/installer tests pass, together with workspace compilation, lint, and
production builds. The VS Code compatibility suite has 16 passing tests and
one platform-specific pending test.
- Focused tests verify optional extension fallback, strict resource loading,
stage routing, repository-provider validation, agent context, and package
provenance.
- No live end-to-end customer migration, runtime business-equivalence test, or
Azure deployment was performed for this release. Operational skills still
require explicit post-conversion operator or CI gates.
## PowerShell update
```powershell
Invoke-WebRequest 'https://tools.lambogenius.com/lambogenius-integration-migration/0.0.4-microsoft-preview.26/install-cli.ps1' -OutFile install-cli-preview26.ps1
# Review the downloaded script before running it.
& .\install-cli-preview26.ps1 -SkipDependencies
li.cmd --version
```
Expected version: `0.0.4-microsoft-preview.26`. This preview is not promoted to
the stable `latest` alias. Preserve existing reports and generated output, then
use a fresh generated workspace because extension inputs and repository metadata
participate in migration fingerprints. Do not edit fingerprint records to force
checkpoint reuse. Installation does not reset license counters.
Version-pinned installation and checksum
wget -qO- https://tools.lambogenius.com/lambogenius-integration-migration/0.0.4-microsoft-preview.26/install-cli.sh | sh
Invoke-WebRequest 'https://tools.lambogenius.com/lambogenius-integration-migration/0.0.4-microsoft-preview.26/install-cli.ps1' -OutFile install-cli.ps1
./install-cli.ps1
SHA-256: 7a4782e3b343a399f2a30fd3a59eddc51b5bcca18b6518a8653f13a18c34d42f
0.0.4-microsoft-preview.25
Published 2026-09-11
# CLI 0.0.4-microsoft-preview.25
Microsoft migration engine preview. Stable `latest` remains 0.0.3.
## Mermaid node-spacing normalization
- Normalize a line-leading square node declaration from the common model form
`NodeId ["Label"]` to valid Mermaid `NodeId["Label"]` before grammar
validation and storage.
- Limit the normalization to standalone, line-leading node IDs. Valid constructs
such as `subgraph Inbound [Inbound]` remain unchanged.
- Retain preview.24's support for standalone Mermaid `%%` comment lines.
The reported `MODEL_TOOL_LOOP` remained a secondary safeguard: calls 16 through
19 submitted the same invalid architecture. The loop guard and its finite
no-progress limit are unchanged.
## Verification and limits
- 124 Microsoft migration-core tests, 244 CLI tests, and 30 public
release/installer tests pass, together with TypeScript compilation, CLI lint,
and production bundling.
- The exact 8,040-character FINACCONT-BT architecture from retained audit call
16 passes after the bounded normalizer corrects its 93 spaced square-node
declarations. No source or generated customer artifact was modified.
- This corrects one deterministic Mermaid syntax pattern; it does not establish
complete Discovery, planning, conversion, runtime business equivalence, or
Azure deployment. Other invalid or unsupported model output still fails
closed.
## PowerShell update
```powershell
Invoke-WebRequest 'https://tools.lambogenius.com/lambogenius-integration-migration/0.0.4-microsoft-preview.25/install-cli.ps1' -OutFile install-cli-preview25.ps1
# Review the downloaded script before running it.
& .\install-cli-preview25.ps1 -SkipDependencies
li.cmd --version
```
Expected version: `0.0.4-microsoft-preview.25`. This preview is not promoted to
the stable `latest` alias. Preserve existing reports and generated output, then
use a fresh generated workspace because the Microsoft engine fingerprint
changes. Do not edit fingerprint records to force checkpoint reuse. Installation
does not reset license counters.
Version-pinned installation and checksum
wget -qO- https://tools.lambogenius.com/lambogenius-integration-migration/0.0.4-microsoft-preview.25/install-cli.sh | sh
Invoke-WebRequest 'https://tools.lambogenius.com/lambogenius-integration-migration/0.0.4-microsoft-preview.25/install-cli.ps1' -OutFile install-cli.ps1
./install-cli.ps1
SHA-256: 77ad2502193ddabbff5e93ea412e6e41f005081c7582f839fd1060f7c0f81aef
0.0.4-microsoft-preview.24
Published 2026-09-11
# CLI 0.0.4-microsoft-preview.24
Microsoft migration engine preview. Stable `latest` remains 0.0.3.
## Mermaid architecture validation fix
- Accept standalone Mermaid `%%` comment lines during Discovery and Planning
architecture validation. The pinned flowchart parser previously rejected a
valid comment immediately after `flowchart TB`, even though Mermaid renderers
accept that syntax.
- Replace comment-only lines with blank lines only in the parser input. This
preserves grammar error line numbers and retains the normalized diagram,
including its comments, for storage and rendering.
- Do not treat `%%` text inside node labels as a comment.
The failure reported as `MODEL_TOOL_LOOP` was a secondary safeguard: the model
submitted the same rejected architecture repeatedly. The loop guard remains
unchanged and will still stop genuinely repeated requests that add no evidence.
## Verification and limits
- 123 Microsoft migration-core tests, 244 CLI tests, and 30 public
release/installer tests pass, together with TypeScript compilation, CLI lint,
and production bundling.
- A regression covers comment lines before and inside a flowchart while
preserving a literal `%%` label. The exact 17,447-character architecture from
the retained FINACCONT-BT audit call 29 also passes the patched validator.
- This corrects architecture syntax validation; it does not establish complete
Discovery, planning, conversion, runtime business equivalence, or Azure
deployment. Other model output can still fail deterministic validation.
## PowerShell update
```powershell
Invoke-WebRequest 'https://tools.lambogenius.com/lambogenius-integration-migration/0.0.4-microsoft-preview.24/install-cli.ps1' -OutFile install-cli-preview24.ps1
# Review the downloaded script before running it.
& .\install-cli-preview24.ps1 -SkipDependencies
li.cmd --version
```
Expected version: `0.0.4-microsoft-preview.24`. This preview is not promoted to
the stable `latest` alias. Preserve the existing reports and generated output,
then use a fresh generated workspace because the Microsoft engine fingerprint
changes. Do not edit fingerprint records to force checkpoint reuse. Installation
does not reset license counters.
Version-pinned installation and checksum
wget -qO- https://tools.lambogenius.com/lambogenius-integration-migration/0.0.4-microsoft-preview.24/install-cli.sh | sh
Invoke-WebRequest 'https://tools.lambogenius.com/lambogenius-integration-migration/0.0.4-microsoft-preview.24/install-cli.ps1' -OutFile install-cli.ps1
./install-cli.ps1
SHA-256: 7eea8731f90f863725290e565c8847cab91ae71266dab4b513f452e576236977
0.0.4-microsoft-preview.23
Published 2026-09-11
# CLI 0.0.4-microsoft-preview.23
Microsoft migration engine preview. Stable `latest` remains 0.0.3.
## Changes
- Discover custom BizTalk pipeline-component dependencies declared by `.btp`
`Component` elements, including `AssemblyQualifiedName`, `Type`, `Name`, and
nested `Name` forms.
- Match assembly-qualified component identities to source projects anywhere in
the recursively inventoried source tree. When a component contains only its
fully qualified type, use the longest matching source assembly namespace
prefix without treating the candidate as a verified binary.
- Retain a matched nested project, its source files, and its transitive source
dependencies as migration evidence. A missing compiled DLL therefore does not
hide supplied source such as
`COMMON-BT/TTC.BTS.Common.PipelineComponents/TTC.BTS.Common.PipelineComponents.csproj`.
The match remains a static source candidate. It does not prove assembly version,
public-key-token compatibility, successful compilation, or runtime behavior.
## Verification and limits
- 122 Microsoft migration-core tests, 244 CLI tests, and 30 public
release/installer tests pass, together with TypeScript compilation, CLI and
provider lint, production bundling, and byte-for-byte verification of all 117
previously published assets.
- The regression reproduces a parent BizTalk solution with the component project
under nested `COMMON-BT/TTC.BTS.Common.PipelineComponents` and confirms that
the project and C# implementation remain selected evidence.
- Full live FINACCONT-BT Discovery, planning, conversion, runtime business
equivalence, and Azure deployment are not established by this targeted fix.
Application bindings and all other required migration inputs still have to be
supplied.
## PowerShell update
```powershell
Invoke-WebRequest 'https://tools.lambogenius.com/lambogenius-integration-migration/0.0.4-microsoft-preview.23/install-cli.ps1' -OutFile install-cli-preview23.ps1
# Review the downloaded script before running it.
& .\install-cli-preview23.ps1 -SkipDependencies
li.cmd --version
```
Expected version: `0.0.4-microsoft-preview.23`. This preview is not promoted to
the stable `latest` alias. Preserve previous reports/output and select a fresh
generated workspace so old Discovery grouping does not exclude the newly
retained dependency artifacts. Installation does not reset license counters.
Version-pinned installation and checksum
wget -qO- https://tools.lambogenius.com/lambogenius-integration-migration/0.0.4-microsoft-preview.23/install-cli.sh | sh
Invoke-WebRequest 'https://tools.lambogenius.com/lambogenius-integration-migration/0.0.4-microsoft-preview.23/install-cli.ps1' -OutFile install-cli.ps1
./install-cli.ps1
SHA-256: f5100b8b64b3f8ab82cceead63fb87041c4e7c4dad4977d4591889b6352fd788
0.0.4-microsoft-preview.22
Published 2026-09-10
# CLI 0.0.4-microsoft-preview.22
Microsoft migration engine preview. Stable `latest` remains 0.0.3.
**Known limitation: full FINACCONT-BT Discovery is not yet qualified.** The live
continuation advanced beyond repeated artifact reads, but component generation
still exceeded the isolated test's ten-minute response deadline. This release
contains verified host fixes, not a claim of successful end-to-end migration.
## Changes
- Honor the configured global context ceiling unless a phase explicitly overrides
it. Use verified tokenizer units consistently for prompts and retained evidence.
- Factor identical repeated artifact objects into a lossless shared dictionary.
Preserve all source fields, hashes and exact audit records. Complete paginated
documents are assembled only after contiguous coverage and SHA-256 verification.
- Allocate Ollama runtime context for the complete measured prompt plus output and
template reserves, growing up to the configured ceiling. No smaller model is
selected and no evidence is discarded to fit a smaller runtime allocation.
- Keep changing archive bookkeeping after source evidence for prompt-prefix reuse.
- Accept a whole Mermaid code fence through envelope normalization, followed by
the original pinned grammar. Invalid syntax returns feedback before storage;
custom validation and storage failures still stop the stage.
- Strengthen bounded-write guidance. Allow one shared recovery for output-limit
stops or timeouts with partial output; incomplete responses are audited and
never executed. Silent timeouts and repeated failed recovery remain fatal.
Microsoft instructions, coverage/finalization checks, model selection, production
deadlines and tool-call limits remain unchanged. No customer YAML, activation,
entitlements, source files or Azure resources are modified by installation.
## Verification and remaining work
- 122 core, 243 CLI and 24 release/installer regressions pass (389 total);
CLI lint and production build pass.
- Captured FINACCONT evidence round-trips exactly: five orchestrations and their
binding. Shared representation reduces the document from 50701 to 20761 Qwen
tokens without summarizing away source content.
- A live seeded-read continuation with the same local `qwen3-coder:30b` accepted
model-generated metadata. Its complete architecture candidate passed the
pinned grammar after the fence normalization fix.
- A later continuation replayed those real writes through normal validation,
then timed out on two component responses, including bounded recovery. The
model ignored chunk guidance. Neither partial response executed; source and
grouping bytes stayed unchanged. This diagnostic used a 600-second limit,
shorter than the application's default 3600-second absolute limit.
- Reliable bounded component output and a successful complete live Discovery
remain outstanding. Planning, conversion and runtime business equivalence
are not established by these continuation or fixture tests.
## PowerShell update
```powershell
Invoke-WebRequest 'https://tools.lambogenius.com/lambogenius-integration-migration/0.0.4-microsoft-preview.22/install-cli.ps1' -OutFile install-cli-preview22.ps1
# Review the downloaded script before running it.
& .\install-cli-preview22.ps1 -SkipDependencies
li.cmd --version
```
Expected version: `0.0.4-microsoft-preview.22`. Omit `-SkipDependencies` to install
missing prerequisites. Preserve previous reports/output and select a fresh
generated workspace: the engine fingerprint changed, so do not force old
Discovery or Conversion checkpoints to resume. Keep your chosen model and
supported context settings. Installation does not reset license counters.
Version-pinned installation and checksum
wget -qO- https://tools.lambogenius.com/lambogenius-integration-migration/0.0.4-microsoft-preview.22/install-cli.sh | sh
Invoke-WebRequest 'https://tools.lambogenius.com/lambogenius-integration-migration/0.0.4-microsoft-preview.22/install-cli.ps1' -OutFile install-cli.ps1
./install-cli.ps1
SHA-256: 322e16ce3e07cac2301f4f942b1e25859c1b56980a51bd958e56c051203814db
0.0.4-microsoft-preview.21
Published 2026-09-10
# CLI 0.0.4-microsoft-preview.21
Microsoft migration engine preview. Stable `latest` remains 0.0.3.
## Cross-stage reliability fixes
- Compact grouping submissions use explicit inventory indexes, translated exactly
to selected artifact IDs before the original Microsoft grouping and coverage
checks. Empty or malformed groups no longer enter membership-only repair.
- All model phases support bounded write-input chunks. Only a complete JSON input
reaches the original authorized tool; schema, scope and finalization checks remain.
One output-limit correction per phase is allowed within the existing round limit.
Truncated output is audited, never executed or artificially completed.
- Persistent phase guidance, pagination validation and structured failure reports
identify outstanding work. Unchanged reads/drafts cannot evade loop detection.
- Test, package and cost records are tied to current input/configuration hashes.
Test records include generated runtime binaries. Cost resume also checks the
report hash and a 24-hour age limit. Legacy unfingerprinted records require reruns.
- Package verification rejects missing, changed, linked and unlisted content.
Replacement builds separately and retains the previous package for recovery.
- Deployment saves intent before queuing and its run ID before polling.
`deploy --resume` reattaches without submitting another run; `--new-run` requires
an explicitly completed prior run. Unknown queue outcomes require reconciliation.
Microsoft stage logic and mandatory verification remain in place. This release
does not select a smaller model, raise the production tool-call limit, change
customer YAML, reset license counters, or perform an Azure deployment.
## PowerShell update
```powershell
Invoke-WebRequest 'https://tools.lambogenius.com/lambogenius-integration-migration/0.0.4-microsoft-preview.21/install-cli.ps1' -OutFile install-cli-preview21.ps1
# Review the downloaded script before running it.
& .\install-cli-preview21.ps1 -SkipDependencies
li.cmd --version
```
Expected version: `0.0.4-microsoft-preview.21`. Omit `-SkipDependencies` if you
want the installer to install missing prerequisites. Preserve earlier output
and select a fresh generated workspace: the engine fingerprint changed, so do
not force an old discovery/conversion checkpoint to resume. Keep your model and
supported context settings; installation does not reset entitlements.
## Verification and limits
- 107 Microsoft-core, 240 CLI and 24 release/installer tests passed (371 total).
Compilation, CLI lint and production build passed.
- A fresh live FINACCONT-BT grouping run passed in three model/tool calls, with
no seeded responses, covering 98 selected files and five orchestrations.
It used the unchanged local `qwen3-coder:30b`, 64K context and 8192 output tokens.
The isolated qualification allowed a 600-second response deadline. Customer
source, generated output and original audit files remained unchanged.
- An earlier seeded recovery test reached a compact submission but stopped at
its ten-call test cap with two explicitly missing memberships; it was not
reported as successful. Model responses can still fail validation.
- Cross-stage fixture tests exercise parsing, discovery, planning, conversion,
finalization, output-limit handling, freshness and deployment failure paths.
Deployment queuing/polling tests use mocks, not live Azure resources.
**Fresh grouping success is not a complete FINACCONT-BT migration qualification.**
Full discovery, planning, conversion, local tests and deployed business behavior
remain to be validated against the actual solution. Static coverage and package
integrity do not establish runtime equivalence. Clean-machine dependency setup
on every supported OS/architecture also remains a separate qualification task.
Version-pinned installation and checksum
wget -qO- https://tools.lambogenius.com/lambogenius-integration-migration/0.0.4-microsoft-preview.21/install-cli.sh | sh
Invoke-WebRequest 'https://tools.lambogenius.com/lambogenius-integration-migration/0.0.4-microsoft-preview.21/install-cli.ps1' -OutFile install-cli.ps1
./install-cli.ps1
SHA-256: cd69a4fcfef84fb08e2d51c1825dd3bfce1aea222269e4de7e90d20df978345a
0.0.4-microsoft-preview.20
Published 2026-09-10
# CLI 0.0.4-microsoft-preview.20
Microsoft migration engine preview. Stable `latest` remains 0.0.3.
## Fix: artifact-detail reads could trigger a discovery loop
The inspected FINACCONT-BT run completed grouping, then detailed discovery
repeated graph and bulk artifact reads without storing its outputs. The
`migration_getArtifactDetails` schema advertised pagination, but its handler
ignored the cursor and returned the entire roughly 204KB result.
- Implemented native exact-text pagination on the same artifact-detail tool.
Large results provide a stable document ID and an explicit `nextRead` input;
the model no longer needs to resubmit long lists or switch to the archive reader.
- Each serialized page is bounded to 12,000 UTF-8 bytes, including escaping and
metadata. Contiguous pages reconstruct the exact serialized artifact IR.
Small complete responses retain the upstream `artifacts[]` shape.
- Added persistent first-unread-page guidance across prompt-history eviction.
Reading only the last page cannot mark the whole document delivered.
- Reordered/duplicate artifact IDs, default offsets and document aliases cannot
make the same evidence appear new to the repeated-call guard.
- Invalid cursors receive explicit corrective feedback. Source-scope restrictions,
finite budgets, exact audits and mandatory Microsoft finalization remain intact.
No model change, longer timeout, higher call limit, synthetic migration output,
source truncation or relaxed orchestration verification is used as the fix.
## PowerShell update
```powershell
Invoke-WebRequest 'https://tools.lambogenius.com/lambogenius-integration-migration/0.0.4-microsoft-preview.20/install-cli.ps1' -OutFile install-cli-preview20.ps1
# Review the downloaded script before running it.
& .\install-cli-preview20.ps1 -SkipDependencies
li.cmd --version
```
Expected version: `0.0.4-microsoft-preview.20`. Keep your existing model and
configuration. Preserve previous output and use a fresh generated workspace:
the engine fingerprint changes, so do not force an old checkpoint to resume.
Installation does not reset license counters.
## Verification and limits
- 95 Microsoft-core tests, 234 CLI tests and 24 release/installer tests passed
(353 total). Compilation and CLI lint passed.
- Replayed the captured FINACCONT-BT bulk request against 98 selected files and
five orchestrations. All 20 pages reconstructed the exact serialized IR. A
synthetic metadata write was accepted only as a transport test; discovery was
deliberately not finalized. Source and existing customer files were unchanged.
- After two seeded setup reads, the existing local `qwen3-coder:30b` followed four
consecutive real page continuations correctly, including across history eviction.
This bounded test used a 64K context and retained exact local audits.
**This verifies the pagination defect and live continuation behavior, not a fresh
end-to-end FINACCONT-BT migration.** The model must still analyse the evidence and
pass discovery, planning, orchestration coverage, conversion and runtime checks.
Earlier pages remain retrievable in the audit/archive, not permanently in the
finite prompt. Other model loops or semantic errors remain possible and must
fail visibly rather than be reported as successful migration.
Version-pinned installation and checksum
wget -qO- https://tools.lambogenius.com/lambogenius-integration-migration/0.0.4-microsoft-preview.20/install-cli.sh | sh
Invoke-WebRequest 'https://tools.lambogenius.com/lambogenius-integration-migration/0.0.4-microsoft-preview.20/install-cli.ps1' -OutFile install-cli.ps1
./install-cli.ps1
SHA-256: 1439745b8b6f9eefddafd7d45630231368e23d6eec767be73f8fe161ee7aca1c
0.0.4-microsoft-preview.19
Published 2026-09-10
# CLI 0.0.4-microsoft-preview.19
Microsoft migration engine preview. Stable `latest` remains 0.0.3.
## Ollama runtime changes
- Phase-specific context allocation and optional `agent.phaseContextWindowTokens` overrides. `agent.contextWindowTokens` is the ceiling, not an allocation forced on every phase. The configured model is unchanged.
- Model-specific token counting using the installed Ollama GGUF vocabulary/merges for the verified Qwen2 tokenizer and raw prompt template. Unsupported templates/models keep the conservative byte guard. No tokenizer/model downloads or evidence truncation.
- Complete Microsoft prerequisite text is retained without redundant JSON escaping. Every prompt is checked before inference; suspicious server input-token counts reject the response before tool execution.
- Model context capacity is checked for all phases before inference. GPU/CPU placement is checked before sending stage prompts, including loading the existing model at the selected context where needed. CPU offload is explicitly reported.
- Configurable finite `agent.requestTimeoutSeconds` (default 3600) and `agent.inactivityTimeoutSeconds` (default 1800). Empty keepalives cannot bypass inactivity; continuous streaming cannot bypass the absolute deadline. Timeouts report `MODEL_TIMEOUT` with a remedy and never accept partial output.
- Progress includes characters/second, first-output latency and server-measured final tokens/second when available.
## Configuration
Merge into your existing `agent` section:
```yaml
agent:
provider: ollama
model: qwen3-coder:30b
contextWindowTokens: 65536
maxOutputTokens: 8192
requestTimeoutSeconds: 3600
inactivityTimeoutSeconds: 1800
```
This 64K example fits the tokenizer/template verified on the test server. Unknown
templates retain the conservative guard and may need more capacity. Explicit
phase overrides must fit inside the global ceiling. Larger evidence may require
additional capacity; never bypass source coverage or finalization checks.
## PowerShell update
```powershell
Invoke-WebRequest 'https://tools.lambogenius.com/lambogenius-integration-migration/0.0.4-microsoft-preview.19/install-cli.ps1' -OutFile install-cli-preview19.ps1
# Review the downloaded script before running it.
& .\install-cli-preview19.ps1 -SkipDependencies
li.cmd --version
```
Expected version: `0.0.4-microsoft-preview.19`. Preserve earlier outputs and use a
fresh generated workspace because the engine fingerprint changes. Do not edit
checkpoint fingerprints to force resume. Installation does not reset license counters.
## Verification and limitations
234 CLI tests, 88 Microsoft-core tests and 24 installer/release tests passed
(346 total). Compilation and lint passed.
Regression coverage includes tokenizer fallback/Unicode, per-phase ceilings,
cold-model placement, finite absolute/inactivity deadlines, empty keepalives,
partial token accounting and rejection of truncated server prompts.
The local qwen3-coder:30b probe succeeded, including Unicode/special-token
measurement and GPU placement diagnostics. Complete planning instructions
measured about 31.4K tokens and fit a 64K context, versus the old 256K allocation.
The FINACCONT-BT live grouping qualification retained 98 selected files and five
orchestrations. It read the graph and artifact inventory, rejected an invented
flow reference, then reached the deliberately bounded 180-second test deadline
while generating its fourth response. It did not finalize grouping. Source
bytes were unchanged. The tested 8GB GPU still offloaded 75.5% of model memory
to CPU at 64K. This preview improves budgeting, diagnosis and timeout control;
**it does not claim a completed FINACCONT-BT migration or eliminate hardware limits.**
Version-pinned installation and checksum
wget -qO- https://tools.lambogenius.com/lambogenius-integration-migration/0.0.4-microsoft-preview.19/install-cli.sh | sh
Invoke-WebRequest 'https://tools.lambogenius.com/lambogenius-integration-migration/0.0.4-microsoft-preview.19/install-cli.ps1' -OutFile install-cli.ps1
./install-cli.ps1
SHA-256: c07ee090af19cf1ce2e081566a2c701ec8f42cea64c0fd43ad5d6d24f9a88b83
0.0.4-microsoft-preview.18
Published 2026-09-09
# CLI 0.0.4-microsoft-preview.18
Microsoft migration engine preview. Stable `latest` remains 0.0.3.
## Invalid flow-reference recovery
- Graph lookups now reject nonexistent, malformed and out-of-scope flow IDs with explicit corrective feedback instead of a fatal lookup exception. No graph is returned and no group is created for rejected inputs.
- During grouping, feedback distinguishes a missing initial graph read from an already available inventory. The model is directed to read the inventory without an invented ID or submit evidence-backed groups, respectively.
- During later phases, feedback identifies the host-selected flow. The host does not silently replace an explicitly wrong ID or broaden the source scope.
- Three rejected graph references stop with `INVALID_FLOW_REFERENCE`, the affected tool/ID, and the exact next action. Changing invented IDs or interleaving valid reads does not reset the budget. Corrections stay visible and exact requests/results remain audited.
- Storage, handler and audit failures remain fatal. This narrowly scoped input correction does not retry side effects, weaken grouping validation or bypass Microsoft finalization.
## PowerShell update
```powershell
Invoke-WebRequest 'https://tools.lambogenius.com/lambogenius-integration-migration/0.0.4-microsoft-preview.18/install-cli.ps1' -OutFile install-cli-preview18.ps1
# Review the downloaded script before running it.
& .\install-cli-preview18.ps1 -SkipDependencies
li.cmd --version
```
Expected version: `0.0.4-microsoft-preview.18`. Keep supported YAML context settings from preview.16/17. No further context increase is needed for this fix. Preserve earlier output and use a fresh generated workspace because the engine fingerprint changes. Do not edit checkpoint fingerprints to force resume. License counters are not reset by installation.
## Verification
88 Microsoft-core tests, 222 CLI tests and 24 installer/release tests passed (334 total); compilation and lint passed.
FINACCONT-BT regression used the invalid request captured during inspection of the customer's audit: `migration_detectFlowGroups` with `groupId: flow-1-order-processing`. The original audit was no longer present at its former path at test time, so a labeled reconstructed request fixture was used. Four scripted calls against the actual parser/source selection covered inventory, custom-code listing, rejection, and a valid synthetic grouping submission. All 98 artifacts and five orchestrations were retained; source bytes were unchanged and the nonexistent group was not created.
The test performs zero model calls and validates input recovery, not the semantic correctness of a live model's grouping or an end-to-end migration. Synthetic outputs exist only in a disposable test directory. No customer output, global CLI, license state or cloud migration resources were changed.
Version-pinned installation and checksum
wget -qO- https://tools.lambogenius.com/lambogenius-integration-migration/0.0.4-microsoft-preview.18/install-cli.sh | sh
Invoke-WebRequest 'https://tools.lambogenius.com/lambogenius-integration-migration/0.0.4-microsoft-preview.18/install-cli.ps1' -OutFile install-cli.ps1
./install-cli.ps1
SHA-256: cc9c7bcbf291baccb9d947145aa8be202047db30fe7ff4b3827ed1dbe3f2f64f
0.0.4-microsoft-preview.17
Published 2026-09-09
# CLI 0.0.4-microsoft-preview.17
Microsoft migration engine preview. Stable `latest` remains 0.0.3.
## Discovery phase guidance and safe correction
- Fixed a conflicting host instruction: reading a flow graph during discovery no longer tells the model to store flow groups again. Non-group phases receive read-only evidence for their existing selected flow, including when `groupId` is omitted.
- Discovery explicitly selects the upstream analyser's Task B, not its grouping Task A. Complete pinned Microsoft instructions and required skills remain unchanged.
- Persistent discovery guidance identifies the next missing output from the saved partial files: metadata, architecture, components, message flow, gaps, patterns, dependencies, then verified finalization. Existing files are not treated as proof of correctness.
- Known imported tools excluded by the current phase can receive at most two correction opportunities. The third wrong-stage request stops the stage, even with valid reads between attempts. The existing consecutive invalid-input budget can stop earlier.
- Rejected operations are never invoked, renamed, or applied. The model must supply a fresh authorized request. Exact rejected responses are audited. Unknown tools, shell requests and storage/audit failures remain immediately fatal.
- Repeated stage violations report `WRONG_STAGE_TOOL` with the affected phase/tool and a specific remedy. Other unauthorized requests report `UNAUTHORIZED_STAGE_TOOL`. Neither is mislabeled as a missing binding.
These are host orchestration changes, not replacements for Microsoft stage logic. Source selection, dependency requirements, workflow coverage, authorization and finalization checks remain enforced.
## Update in PowerShell
```powershell
Invoke-WebRequest 'https://tools.lambogenius.com/lambogenius-integration-migration/0.0.4-microsoft-preview.17/install-cli.ps1' -OutFile install-cli-preview17.ps1
# Review the downloaded script before execution.
& .\install-cli-preview17.ps1 -SkipDependencies
li.cmd --version
```
Expected version: `0.0.4-microsoft-preview.17`. Omit `-SkipDependencies` if prerequisites need installation.
Keep the supported context settings from preview.16 (`contextWindowTokens: 262144`, `maxOutputTokens: 8192`); this bug does not require another context increase. Sufficient model/server memory is still necessary. The engine fingerprint changes: preserve previous outputs and use a fresh generated workspace. Do not edit checkpoint fingerprints to force resume. Installation does not reset license counters.
## Verification and limitations
- 84 Microsoft-core tests, 221 CLI tests and 24 installer/release tests passed; compilation and lint passed.
- FINACCONT-BT regression replay used the exact saved rejected model response and the actual selected source/parser results: 98 artifacts, five orchestrations, three scripted calls, zero model calls, maximum prompt 76,085 UTF-8 bytes.
- The rejected group write executed nothing; a subsequent authorized discovery metadata write succeeded in an isolated fixture. Saved groups, source files and original audit bytes were unchanged.
- The fixture deliberately remained incomplete and did not finalize discovery. This validates phase correction, not semantic discovery or an end-to-end migration. No customer generated output or cloud resources were changed.
This release does not tune Ollama inference performance or promise shorter model responses.
Version-pinned installation and checksum
wget -qO- https://tools.lambogenius.com/lambogenius-integration-migration/0.0.4-microsoft-preview.17/install-cli.sh | sh
Invoke-WebRequest 'https://tools.lambogenius.com/lambogenius-integration-migration/0.0.4-microsoft-preview.17/install-cli.ps1' -OutFile install-cli.ps1
./install-cli.ps1
SHA-256: 5448d1cdbc7f9c5341e2ea078c0c35419deb7d01998491ff4a024ebf1e1958d7
0.0.4-microsoft-preview.16
Published 2026-09-09
# CLI 0.0.4-microsoft-preview.16
Microsoft migration engine preview. Stable `latest` remains 0.0.3.
## Context capacity checked before model work
- Precheck now measures the required prompts for grouping, discovery, planning, task planning and conversion tasks before starting model work. Direct Microsoft stage sessions enforce the same check.
- Runtime and precheck share the actual prompt builder and phase-specific tool definitions. Required Microsoft agent instructions and prerequisite skills remain complete and unmodified.
- Insufficient capacity produces structured `CONTEXT_BUDGET` requirements identifying every affected phase, its byte allowance, reserves, minimum configured context and suggested YAML. This is not reported as a missing binding or dependency.
- Planning no longer duplicates the full orchestration coverage dataset in its mandatory prompt. Exact requirements remain available through `migration_getMigrationContext` and paginated archive reads. All coverage rules and finalization checks remain enforced.
- Context measurements use the existing conservative UTF-8 byte bound, not estimated token counts. Tool-loop limits and evidence retention are unchanged.
## YAML setting for the full Microsoft pipeline
Merge these settings into the existing `agent` section, preserving provider, model and endpoint:
```yaml
agent:
contextWindowTokens: 262144
maxOutputTokens: 8192
```
Use this only when the model, Ollama server and available memory support it. With the current pinned instructions and conservative guard, 131072 fits discovery but not planning. Planning's minimum configured context is approximately 185,387 with an 8192 output reserve; 262144 gives additional evidence headroom. Passing preflight is not a guarantee of inference memory availability or successful migration.
## Install or update (PowerShell)
```powershell
Invoke-WebRequest 'https://tools.lambogenius.com/lambogenius-integration-migration/0.0.4-microsoft-preview.16/install-cli.ps1' -OutFile install-cli-preview16.ps1
# Review the downloaded script before running it.
& .\install-cli-preview16.ps1 -SkipDependencies
li.cmd --version
```
Expected version: `0.0.4-microsoft-preview.16`. Omit `-SkipDependencies` if prerequisites need installation. Use `li.cmd` to avoid PowerShell's built-in alias.
The engine fingerprint changes. Preserve old output and select a fresh generated workspace; do not force resume by editing checkpoint fingerprints. Installation does not reset entitlements or extend the license term.
## Verification and limitations
78 Microsoft-core tests, 219 CLI tests and 24 installer/release tests passed, along with compilation and lint. Seven new regressions cover the reported 54,748-byte prefix, zero-call early failure, all-stage 64K/128K/256K capacity, structured precheck guidance, complete upstream skill content, non-duplicated coverage data, Unicode and output reserves.
These tests verify context handling and retained validation requirements. They do not constitute a new end-to-end FINACCONT-BT conversion or demonstrate runtime behavioral equivalence. No customer source/output, global installation, license counters or Azure resources were changed.
Version-pinned installation and checksum
wget -qO- https://tools.lambogenius.com/lambogenius-integration-migration/0.0.4-microsoft-preview.16/install-cli.sh | sh
Invoke-WebRequest 'https://tools.lambogenius.com/lambogenius-integration-migration/0.0.4-microsoft-preview.16/install-cli.ps1' -OutFile install-cli.ps1
./install-cli.ps1
SHA-256: 80b631d277afdffce38f56be664bdfda3d2ec14834998c906b666debf14d8bc4
0.0.4-microsoft-preview.15
Published 2026-09-09
# CLI 0.0.4-microsoft-preview.15
Microsoft migration engine preview. Stable `latest` remains 0.0.3.
## Grouping-loop fixes
- Keep the newest complete tool result in the prompt when it fits, instead of archiving it at half the available history budget. The grouping overview retains every selected artifact ID and the complete Microsoft connection graph; redundant paths remain available through detail/list tools.
- Keep host-confirmed grouping progress visible, so the model is instructed to submit groups rather than restart detection.
- When grouping validation fails, identify every unaccounted selected artifact ID and explain how to correct the submission. Orchestrations still must belong to exactly one flow, and caller/callee chains must stay together.
- Keep an outstanding validation correction visible across intervening evidence reads, even if its original call moves to the exact-result archive.
- A host-only `lambogenius_correctFlowGroups` tool lets the model explicitly amend individual artifact memberships in its latest rejected submission. Revision checks prevent stale changes; missing and conflicting memberships are listed together. Corrections still pass through the normal grouping validator and storage path.
- Stop three consecutive repeated request/result pairs with an explicit `MODEL_TOOL_LOOP` requirement. Alternating already-seen tools is also detected. Different pages, corrected inputs and changed results remain valid progress.
- Retain all executed calls in the audit and report the affected tool and next action. No success is inferred from a model response alone.
These are Lambogenius host-control improvements around the pinned Microsoft tools and instructions. They do not replace Microsoft parsing/grouping rules, truncate required evidence, or relax finalization checks.
## Install or update (PowerShell)
```powershell
Invoke-WebRequest 'https://tools.lambogenius.com/lambogenius-integration-migration/0.0.4-microsoft-preview.15/install-cli.ps1' -OutFile install-cli-preview15.ps1
# Review the downloaded script before running it.
& .\install-cli-preview15.ps1 -SkipDependencies
li.cmd --version
```
Expected version: `0.0.4-microsoft-preview.15`. Omit `-SkipDependencies` if prerequisites need installation. Use `li.cmd` to avoid PowerShell's built-in `li` alias.
The engine fingerprint changes. Preserve previous outputs and use a fresh generated workspace; do not edit checkpoint fingerprints to force resume. Installation does not reset entitlement counters or extend the license term.
## Regression verification
- 78 Microsoft-core tests, 212 CLI tests, and 24 installer/release tests passed; CLI compilation and lint passed.
- FINACCONT-BT scripted regressions preserved all 98 selected artifacts and 5 orchestrations. The complete grouping response was directly available within the 55,296-byte ceiling, and a deliberately repeated detection call stopped after four calls instead of 100. Customer source bytes were unchanged.
- Bundled startup/license display, standalone precheck, stage failure diagnostics, and machine-readable output smoke checks passed. The packaged bundle matched the smoke-tested bundle byte-for-byte.
### Local-model recovery qualification
An initial local `qwen3-coder:30b` run produced a real FINACCONT-BT grouping submission with omitted and conflicting memberships. That exact rejected submission was replayed into the final host, after its real detection tool ran. The local model then corrected it using the targeted correction tool in **one real model call** (11,727 input + 902 output tokens). Host validation accepted coverage of all 98 selected artifacts and five orchestrations. The largest prompt was 49,123 bytes against a 55,296-byte ceiling, and source bytes were unchanged.
This was a live **recovery** qualification with two scripted setup calls, not a fresh end-to-end CLI migration. Earlier development runs also reproduced an alternating-tool loop, which the new guard stopped after five calls, and a three-minute local-response timeout. The final streaming harness allows ten minutes per response with a 12-call cap. No universal model-success guarantee is implied.
These transport and grouping checks do not establish full discovery, conversion, runtime behavioral equivalence, or deployment success. No customer generated output, global installation, license counters, or Azure resources are changed by these tests.
Version-pinned installation and checksum
wget -qO- https://tools.lambogenius.com/lambogenius-integration-migration/0.0.4-microsoft-preview.15/install-cli.sh | sh
Invoke-WebRequest 'https://tools.lambogenius.com/lambogenius-integration-migration/0.0.4-microsoft-preview.15/install-cli.ps1' -OutFile install-cli.ps1
./install-cli.ps1
SHA-256: 90f9f4d09bc4b64fcbeb57ee8ec426eb0ed184658838629a3f60e7d2492a74ab
0.0.4-microsoft-preview.14
Published 2026-09-09
# CLI 0.0.4-microsoft-preview.14
Released September 9, 2026. Microsoft migration engine preview; stable `latest` remains 0.0.3.
## Microsoft stage context-budget fix
- Flow grouping returns a compact inventory and the complete Microsoft connection graph instead of embedding every artifact's full parsed IR.
- Full artifact details and source text remain available through detail and paginated read tools.
- All model-driven Microsoft stages use bounded prompt history. Oversized results and earlier calls remain available through exact archived-result reads, with optional JSON-field selection and pagination.
- Full tool inputs and results are retained in the stage audit. Partial previews are explicitly labeled; they do not establish that evidence is absent.
- Context limits also account for UTF-8 bytes. Required Microsoft instructions remain complete, and progress messages explain when results are archived.
- Microsoft parsers, graph-building logic, orchestration coverage, and host finalization checks are unchanged.
## Install or update (PowerShell)
```powershell
Invoke-WebRequest 'https://tools.lambogenius.com/lambogenius-integration-migration/0.0.4-microsoft-preview.14/install-cli.ps1' -OutFile install-cli-preview14.ps1
# Review the downloaded script before running it.
& .\install-cli-preview14.ps1 -SkipDependencies
li.cmd --version
```
Expected version: `0.0.4-microsoft-preview.14`. Omit `-SkipDependencies` if prerequisites also need installation. Use `li.cmd` in PowerShell to avoid its built-in `li` alias.
This changes the engine fingerprint. Preserve previous generated work and use a fresh generated workspace for the new run; do not edit checkpoint fingerprints to force reuse. Installation does not reset license counters or extend the license term.
## Verification and limits
70 Microsoft-core tests and 211 CLI tests passed, including a regression matching the reported 388,852-character result and 55,296-byte prompt limit.
A read-only FINACCONT-BT regression preserved all 98 selected artifacts, 5 orchestrations and 42 Microsoft graph connections. Its grouping response dropped from 361,471 to 27,738 characters; its largest scripted prompt was 47,974 bytes. Full detailed IR remained retrievable, and omitting an orchestration was still rejected.
The source regression used scripted requests with zero real model calls. It verifies context transport and coverage enforcement, not end-to-end customer conversion or semantic equivalence. No customer source/output, license activation, metering, or cloud resources were changed by the regression. Required instructions must still fit within the configured model context, and the tool-round limit still applies.
Version-pinned installation and checksum
wget -qO- https://tools.lambogenius.com/lambogenius-integration-migration/0.0.4-microsoft-preview.14/install-cli.sh | sh
Invoke-WebRequest 'https://tools.lambogenius.com/lambogenius-integration-migration/0.0.4-microsoft-preview.14/install-cli.ps1' -OutFile install-cli.ps1
./install-cli.ps1
SHA-256: 6d8d4ab7966f11a0fa14cb470b97f809fdf948420b9cb6b5bc78e887d434e7ca
0.0.4-microsoft-preview.13
Published 2026-09-09
# CLI 0.0.4-microsoft-preview.13
Released September 9, 2026. Microsoft migration engine preview; stable `latest` remains 0.0.3.
## Startup license summary
- Show license details directly below the startup ASCII word art.
- Display the purchased license expiry separately from the short-lived device certificate expiry.
- Show remaining migration units, named-user seats, registered applications, and client organizations from the verified signed certificate.
- Label balances as cached, not live, with the certificate issue timestamp. No extra network requests or metering changes are made just to display the summary.
- Show additional assessment allowance or Unlimited. Remaining assessment usage is unavailable because the licensing service does not supply that counter.
- Handle missing activation, expired licenses, expired certificates, and offline grace explicitly. Unknown fields in older certificates are not guessed.
- Preserve clean JSON, redirected output, CI, help, and version output. `--no-banner` hides both the art and summary; `NO_COLOR` remains supported.
## Refresh existing installations
The licensing backend now includes contract expiry and usage counts in newly
issued signed certificates. After installing this preview, refresh your existing
certificate to receive these fields:
```powershell
Invoke-WebRequest 'https://tools.lambogenius.com/lambogenius-integration-migration/0.0.4-microsoft-preview.13/install-cli.ps1' -OutFile install-cli-preview13.ps1
# Review the downloaded script before running it.
& .\install-cli-preview13.ps1 -SkipDependencies
li.cmd --version
li.cmd license refresh
```
The summary printed before `license refresh` shows the previous snapshot; the
next command displays the refreshed data. Refreshing does not reset usage or
extend the purchased license term. Omit `-SkipDependencies` if prerequisites
also need installation. Use `li.cmd` in PowerShell to avoid its built-in `li` alias.
## Verification
211 CLI tests, 38 backend licensing tests, and production-bundle startup/stage
smoke tests passed. Tests cover signed fixtures, legacy/missing/expired licenses,
unknown usage, remaining quotas, narrow terminals, output suppression, and unchanged
authorization. No customer activation, usage counters, or migration output was changed.
Version-pinned installation and checksum
wget -qO- https://tools.lambogenius.com/lambogenius-integration-migration/0.0.4-microsoft-preview.13/install-cli.sh | sh
Invoke-WebRequest 'https://tools.lambogenius.com/lambogenius-integration-migration/0.0.4-microsoft-preview.13/install-cli.ps1' -OutFile install-cli.ps1
./install-cli.ps1
SHA-256: 97843f2b759d8a00797d892b5893e308722a174733ae906ecca6f1b12d81f72c
0.0.4-microsoft-preview.12
Published 2026-09-09
# CLI 0.0.4-microsoft-preview.12
Released September 9, 2026. Microsoft migration engine preview; stable `latest` remains 0.0.3.
## Dependency readiness fixes
- When a referenced DLL is not present, look for nested source projects with a matching static `AssemblyName`, including projects whose filenames differ from their assembly names.
- Retain matching project implementations and their transitive source dependencies for migration without requiring the old BizTalk solution to be built first.
- Report `DEPENDENCY_SOURCE_AVAILABLE` with the matching source path instead of a false missing-DLL blocker. Multiple matches remain unverified candidates; binary version/public-key compatibility is not claimed.
- Keep original-project `.snk` signing keys private and excluded from migration evidence. Missing or excluded signing keys no longer block migration analysis.
- Keep loose bindings and other files in unrelated nested solutions out of the selected migration scope unless referenced or explicitly included. Unrelated projects do not introduce readiness blockers.
- Genuine missing dependencies, excluded required source, and missing application binding files still produce actionable errors.
## Verification
- 205 CLI tests passed, including source-producer matching, transitive missing dependencies, exclusions, ambiguous matches, signing keys, and unrelated nested-solution artifacts.
- Read-only FINACCONT-BT source-readiness check: two blockers reduced to zero; nine relevant projects retained and 24 unrelated projects ignored.
- No full customer conversion or Azure deployment was performed. Source readiness is not proof of successful orchestration conversion or runtime compatibility.
## Update in PowerShell
```powershell
Invoke-WebRequest 'https://tools.lambogenius.com/lambogenius-integration-migration/0.0.4-microsoft-preview.12/install-cli.ps1' -OutFile install-cli-preview12.ps1
# Review the downloaded script before running it.
& .\install-cli-preview12.ps1 -SkipDependencies
li.cmd --version
```
Omit `-SkipDependencies` if prerequisites also need installation. Use `li.cmd` in
PowerShell because `li` can resolve to the built-in `Get-ChildItem` alias.
Finish any running migration before updating. Preserve previous generated output;
use a fresh generated workspace if a changed scope or engine fingerprint prevents
checkpoint reuse. Do not edit checkpoint fingerprints to bypass validation.
Version-pinned installation and checksum
wget -qO- https://tools.lambogenius.com/lambogenius-integration-migration/0.0.4-microsoft-preview.12/install-cli.sh | sh
Invoke-WebRequest 'https://tools.lambogenius.com/lambogenius-integration-migration/0.0.4-microsoft-preview.12/install-cli.ps1' -OutFile install-cli.ps1
./install-cli.ps1
SHA-256: dc066c2a8b38f1c43b9b35b67bd0222bd00eea76097920650cb317e578005748
0.0.4-microsoft-preview.11
Published 2026-09-09
# CLI 0.0.4-microsoft-preview.11
Opt-in Microsoft-backed evaluation preview. Stable `latest` remains 0.0.3.
## Startup ASCII branding
- Terminal startup displays a pulse-style ASCII logo followed by the entire
Lambogenius name in ASCII word art, with the CLI version beneath it.
- Narrow terminals stack the logo above the wordmark and wrap whole letters;
the name is not replaced by plain text. Extremely narrow terminals suppress
the banner when even one complete letter cannot fit.
- JSON output, redirected stdout, CI, help, and version queries omit the banner.
Worker threads do not print a second banner. `NO_COLOR` disables color only.
- Use `li.cmd --no-banner <command>` to hide startup branding explicitly.
- Includes preview.10's detailed offline HTML/Mermaid batch reports and shared
actionable stage failure summaries.
## Verification and limitations
201 CLI tests, TypeScript compilation, lint, production build, and bundled CLI
checks passed on Windows. Startup checks cover terminal output, whole-letter
wrapping, JSON, redirects, CI, help/version, `NO_COLOR`, and `--no-banner`.
This remains an evaluation preview, not migration or orchestration equivalence
certification. No customer migration or Azure deployment was performed. Preserve
previous outputs and use a fresh generated workspace when evaluating a new
fingerprint-changing preview; do not edit checkpoint fingerprints to force reuse.
## PowerShell update
```powershell
Invoke-WebRequest 'https://tools.lambogenius.com/lambogenius-integration-migration/0.0.4-microsoft-preview.11/install-cli.ps1' -OutFile install-cli-preview11.ps1
# Review the downloaded script and respect your organization's execution policy.
& .\install-cli-preview11.ps1 -SkipDependencies
li.cmd --version
```
Omit `-SkipDependencies` to install missing prerequisites. Use `li.cmd` in
PowerShell because `li` is a built-in alias. Updating does not reset activation,
usage counters, or license expiry. Finish an existing migration before upgrading.
Run `li.cmd` in a terminal to see the word art and enter interactive mode.
`li.cmd --version` deliberately prints only the version number.
Version-pinned installation and checksum
wget -qO- https://tools.lambogenius.com/lambogenius-integration-migration/0.0.4-microsoft-preview.11/install-cli.sh | sh
Invoke-WebRequest 'https://tools.lambogenius.com/lambogenius-integration-migration/0.0.4-microsoft-preview.11/install-cli.ps1' -OutFile install-cli.ps1
./install-cli.ps1
SHA-256: 740bd0a11a7aa4ab4b16e9313e4c42b3d2bd4923b324443c1e31d7c6cfe84340
0.0.4-microsoft-preview.10
Published 2026-09-09
# CLI 0.0.4-microsoft-preview.10
Opt-in Microsoft-backed evaluation preview. Stable `latest` remains 0.0.3.
## Detailed batch reports with offline Mermaid diagrams
- Each completed batch writes Markdown, JSON, and a self-contained HTML report.
The terminal prints the Markdown and HTML paths, including when the batch
stops after a migration failure.
- HTML renders a batch outcome diagram and per-solution stage diagrams locally
in your browser. The pinned Mermaid renderer is embedded: no CDN, internet
connection, extension, or extra user installation is required.
- Reports include solution/stage outcomes and timings, source/output and artifact
links, token counts and count quality, failure remedies, and Azure monthly cost
estimates calculated during the run. Reused cost reports remain linked.
- Solutions not reached after an early failure are listed as not run. Reused
results and stages excluded by conversion-only/preflight mode are explicit.
- Model-call time and total elapsed time are separate. Missing token accounting
is identified rather than silently treated as zero.
- Browser Print / Save as PDF is supported after diagrams render. HTML escapes
report text, redacts common credential patterns, and blocks network requests.
Reports may still contain sensitive names, paths, and diagnostic information.
- Reports show run status, not architecture diagrams imported from stage files
or proof of orchestration business equivalence. Deployed integration and
business acceptance testing remain separate.
## Actionable failures across stages
- Text-mode failures repeat blocking requirements, affected artifacts/settings
when known, and next actions at the end of the stage.
- Precheck, discovery, planning, conversion, testing, packaging, cost estimation,
and deployment use the shared failure summary. Interactive errors use the
same formatter; worker-thread failures retain structured details.
- Missing stage prerequisites and failed local checks are enumerated. Unverified
dependency warnings remain warnings, not confirmed missing files. Unknown
diagnoses stay explicit. JSON mode remains machine-readable.
## Verification and limitations
198 CLI tests, TypeScript compilation, lint, production build, and bundled CLI
smoke tests passed on Windows. Offline Chromium testing rendered actual Mermaid
SVG diagrams from the built CLI's batch report with network resolution blocked.
No customer conversion, paid model calls, or Azure deployments were performed.
This is still a preview, not production migration certification. Preserve prior
outputs and reports. Implementation fingerprints change between previews; use
a fresh generated workspace for evaluation rather than editing fingerprints to
force checkpoint reuse. Clean-machine macOS/ARM64 migration qualification and
customer orchestration equivalence remain outstanding.
## PowerShell update
```powershell
Invoke-WebRequest 'https://tools.lambogenius.com/lambogenius-integration-migration/0.0.4-microsoft-preview.10/install-cli.ps1' -OutFile install-cli-preview10.ps1
# Review the downloaded script and respect your organization's execution policy.
& .\install-cli-preview10.ps1 -SkipDependencies
li.cmd --version
```
Omit `-SkipDependencies` if missing prerequisites should be installed. Use
`li.cmd` because `li` is a built-in PowerShell alias. Updating does not reset
activation, usage counters, or license expiry. Existing running commands retain
their loaded version; finish the current run before upgrading.
After running a batch, open the exact HTML path printed by the CLI:
```powershell
Invoke-Item -LiteralPath '.\reports\migration-batch-<timestamp>.html'
```
Version-pinned installation and checksum
wget -qO- https://tools.lambogenius.com/lambogenius-integration-migration/0.0.4-microsoft-preview.10/install-cli.sh | sh
Invoke-WebRequest 'https://tools.lambogenius.com/lambogenius-integration-migration/0.0.4-microsoft-preview.10/install-cli.ps1' -OutFile install-cli.ps1
./install-cli.ps1
SHA-256: 885c2b86f125e71d1e2b6d411f2c86d0ecb83b2da79220d527207c2086f9b4cc
0.0.4-microsoft-preview.9
Published 2026-09-09
# CLI 0.0.4-microsoft-preview.9
Opt-in evaluation preview. Stable `latest` remains 0.0.3.
## Stage progress and reports
- Standalone precheck, discovery, planning, conversion, testing, deployment
packaging, and cost estimation display timestamped start and finish/failure
messages with model token totals and a Markdown report path.
- Interactive terminals show an animated activity line with the current operation
and elapsed time. Precheck identifies prerequisite checks, source binding and
dependency scanning, provider availability checks, and report writing.
- Standalone precheck, testing, and packaging run local checks in worker threads
so synchronous work does not freeze the terminal activity indicator.
- Batch-configured standalone precheck identifies each solution separately and
writes its reports under `reportDirectory/<solution-id>/`.
- Missing application bindings remain a failed precheck with corrective guidance,
zero model calls, and exit code 2. They never produce a success tick.
- Human-readable precheck output lists Markdown first and JSON second. Explicit
`--json` output remains machine-readable, without animation or stage logs.
- Redirected output uses plain-text progress and periodic heartbeats.
## Verification and preview limitations
188 CLI tests, TypeScript compilation, lint, production bundle, and the bundled
precheck smoke test passed on Windows before packaging. The smoke test verifies
timestamped lifecycle messages, current-work descriptions, missing-binding
failure, zero model tokens, Markdown paths, and parseable JSON output.
This remains the Microsoft-backed migration preview, not production migration
certification. Customer orchestration equivalence, complete Ollama migrations,
Copilot live migrations, and macOS execution remain unqualified. No customer
conversion or Azure deployment was performed for this progress update.
Checkpoint fingerprints include implementation changes. Preserve previous outputs
and reports, and use a fresh generated workspace when testing a new preview.
Do not edit checkpoint fingerprints to force reuse.
## PowerShell update
```powershell
Invoke-WebRequest 'https://tools.lambogenius.com/lambogenius-integration-migration/0.0.4-microsoft-preview.9/install-cli.ps1' -OutFile install-cli-preview.ps1
# Review the script before execution; respect your organization's execution policy.
./install-cli-preview.ps1 -SkipDependencies
li.cmd --version
li.cmd precheck --config .\migration.config.batch.win.yaml
```
Omit `-SkipDependencies` to install missing prerequisites. Updating preserves
activation and usage counters. Use `li.cmd` to avoid PowerShell's built-in `li` alias.
Version-pinned installation and checksum
wget -qO- https://tools.lambogenius.com/lambogenius-integration-migration/0.0.4-microsoft-preview.9/install-cli.sh | sh
Invoke-WebRequest 'https://tools.lambogenius.com/lambogenius-integration-migration/0.0.4-microsoft-preview.9/install-cli.ps1' -OutFile install-cli.ps1
./install-cli.ps1
SHA-256: be2d18c370e4084391b02e2bf505f7d0396d8a59d3abdc91059b5025ab0d8570
0.0.4-microsoft-preview.8
Published 2026-09-09
# CLI 0.0.4-microsoft-preview.8
Opt-in evaluation preview of the Microsoft-backed migration engine. Stable
`latest` remains 0.0.3. This is not a production migration certification.
## Changes
- Discovery, planning, and conversion share extracted services, parsers, tools,
and instructions from the pinned Microsoft Logic Apps Migration Agent import,
with LambOGenius naming, architecture, licensing, and output safety controls.
- Microsoft is the default migration engine. The historical engine requires
explicit `migration.engine: legacy`; failures never silently fall back.
- Missing application binding XML blocks conversion with
`MISSING_APPLICATION_BINDING`, affected orchestration names, searched paths,
and instructions for supplying the application's binding export.
- Dependency diagnostics distinguish confirmed missing inputs from unverified
references. Unverified warnings are not counted as confirmed missing files.
- Completion requires source-grounded orchestration coverage and verified workflow
files; a generic starter health-check workflow cannot satisfy this check.
- Checkpoints verify source, configuration, implementation, and output hashes.
Interrupted tasks require explicit recovery. Progress and token reports remain
available on success and failure.
## Verification and limitations
278 automated tests passed on Windows. Shared-core and selected CLI tests also
passed on Linux Node 20. The package starts on Windows and Linux.
A live Codex synthetic migration generated and applied 16 files. Its actual
Logic Apps workflow passed local XML delivery, transient HTTP retry/recovery,
and permanent HTTP failure-reporting tests. Resume reverified completion with
zero model calls.
This synthetic HTTP receive-and-forward test does not establish customer
orchestration equivalence. Maps, rules, correlations, compensation, transactions,
custom pipelines, RPC ports, and production deployment need further qualification.
Copilot live migrations and macOS execution are not qualified. Complete Ollama
migration is not qualified; model context capacity can be a blocker.
Precheck, cost estimation, testing, and packaging remain LambOGenius host stages.
This preview does not mean every CLI stage is Microsoft's implementation.
## Install and test in PowerShell
```powershell
Invoke-WebRequest 'https://tools.lambogenius.com/lambogenius-integration-migration/0.0.4-microsoft-preview.8/install-cli.ps1' -OutFile install-cli-preview.ps1
# Review the downloaded script before running it.
./install-cli-preview.ps1 -SkipDependencies
li.cmd --version
li.cmd precheck --config .\migration.config.batch.win.yaml
```
Omit `-SkipDependencies` if missing prerequisites should be installed. Respect
your organization's execution policy. Use `li.cmd` in PowerShell to avoid its
built-in `li` alias. Updating does not reset activation or usage counters.
Precheck may report missing prerequisites as well as source requirements. Supply
an application-specific binding XML export, not a group export; do not paste
credentials into support messages.
Preserve existing sources, outputs, and reports. Before conversion, use a fresh
generated workspace when switching engines. Logic Apps Standard output must use
the supported `logicapp/` layout. Review generated business behavior and validate
with independent business test cases before deployment.
## Archive checksum
SHA-256: `7d3b397bdabf11d3e5b9872cdd2bd835cc26d6cc2f7363f74d9c1833de479c8b`
The archive is the exact locally qualified preview.8; its packaged README was
written before public publication. Do not replace this version with different bytes.
Version-pinned installation and checksum
wget -qO- https://tools.lambogenius.com/lambogenius-integration-migration/0.0.4-microsoft-preview.8/install-cli.sh | sh
Invoke-WebRequest 'https://tools.lambogenius.com/lambogenius-integration-migration/0.0.4-microsoft-preview.8/install-cli.ps1' -OutFile install-cli.ps1
./install-cli.ps1
SHA-256: 7d3b397bdabf11d3e5b9872cdd2bd835cc26d6cc2f7363f74d9c1833de479c8b
0.0.3 · Latest
Published 2026-09-09
# CLI 0.0.3
- Animated activity status now works in direct commands such as `li convert`, as well as the interactive menu. Displays the current artifact/operation, retry attempt where applicable, provider status, and elapsed time.
- Shows waiting-for-output versus receiving-output status. Every 30 seconds, readable progress updates are written to the console and configured log file. Redirected/dumb terminals receive plain text without animation; completion, errors, and Ctrl+C stop the indicator cleanly.
- Adds deterministic nested solution/project dependency scanning across shared projects, project references, assembly candidates, imports, packages, explicit source items, and schema references. Full JSON/Markdown reports preserve unresolved and ambiguous findings.
- Adds `li dependencies --source <directory> --output <directory>`, with optional `--root`, `--include`, and `--exclude` source-relative paths. This inspection command does not invoke AI or require activation.
- Separates the complete source inventory from migration evidence. Unconnected nested projects are omitted from evidence; shared and ambiguous dependency candidates are retained for review. `migration.sourceSelection` and per-batch-entry overrides let users select roots and explicitly exclude unrelated files without deleting them.
- Retains application binding evidence and inventories MSI/DLL files. DLLs are not decompiled; nested MSI files are not extracted by the dependency scanner. Existing batch MSI-input extraction remains available. No dedicated BizTalk Deployment Framework parser or group-binding selector is included.
- Prevents reuse of an incompatible recorded discovery scope after source selection changes. Use a fresh generated workspace and rerun discovery/planning when requested; existing source and outputs remain intact.
- Handles interrupted and malformed Ollama response streams without leaving the activity indicator running.
The activity indicator means a request is pending, not that the CLI can prove server progress. Received character counts are not token counts or completion percentages. Existing stage-end token reports are unchanged.
Static dependency scanning is not MSBuild execution, runtime dependency verification, or binary reconstruction. Provide application-specific bindings, source implementations, dependencies, and rules. Dynamic references and assembly identity compatibility still require review.
Verification: 131 automated CLI tests, TypeScript compilation, lint, and production build pass. No real migration, provider purchase, activation, or usage-counter reset is performed by updating. Full clean-machine Windows/macOS/Linux qualification remains separate from these checks.
Version-pinned installation and checksum
wget -qO- https://tools.lambogenius.com/lambogenius-integration-migration/0.0.3/install-cli.sh | sh
Invoke-WebRequest 'https://tools.lambogenius.com/lambogenius-integration-migration/0.0.3/install-cli.ps1' -OutFile install-cli.ps1
./install-cli.ps1
SHA-256: 166484220a7e83c6179eeca3bfc1ddd3d924ad5d6fe3655d64d998bcc75f29b8
0.0.2
Published 2026-09-09
# CLI 0.0.2
- Scaffolded conversions now accept a starter with local edits and untracked files. The clean-starter Git precheck has been removed.
- Copies current starter files without root or nested `.git` directories, including worktree/submodule `.git` pointer files. The original starter and its Git history remain untouched.
- Initializes an independent Git repository in the generated copy when configured. Existing generated repositories still require the normal resume/recovery workflow.
- Retains build-directory exclusions and does not follow symbolic links. Files excluded only by `.gitignore` are part of the filesystem snapshot: keep credentials and unwanted local files outside the starter.
- Includes the Ubuntu 26.04 shell installer correction from installer revision 2026-09-09.1.
No changes to license activation, metering, usage counters, or expiry. Update the CLI before rerunning your conversion; existing CLI 0.0.1 downloads remain unchanged.
Verification: CLI compilation, lint, build, and 102 automated CLI tests pass, including dirty-starter copying, Git-metadata exclusion, and preservation of the original starter. This is not certification of a complete licensed migration on every OS.
Version-pinned installation and checksum
wget -qO- https://tools.lambogenius.com/lambogenius-integration-migration/0.0.2/install-cli.sh | sh
Invoke-WebRequest 'https://tools.lambogenius.com/lambogenius-integration-migration/0.0.2/install-cli.ps1' -OutFile install-cli.ps1
./install-cli.ps1
SHA-256: cb117d33030b6cb480fbd15ad37a36d64edbcb5936621ecd9df7a32a72f2fb13
0.0.1
Published 2026-09-08
# 0.0.1 — Initial public CLI distribution
- Public Windows PowerShell and Linux/macOS shell installers with optional dependency setup.
- Version-pinned packages and installer URLs, a latest alias, SHA-256 checksums, and a release catalog.
- The packaged li CLI provides the existing AIS-focused migration commands and license activation/refresh/deactivation.
- License certificates and server-side application/migration-unit metering protect licensed operations. Reinstallation or generating a new activation code does not reset usage or license expiry.
## Requirements and limitations
- Node.js 20 or later and npm are required. Full migration also requires Git, PowerShell 7, Azure CLI/Bicep, MSI/CAB tools where applicable, and a configured AI provider.
- Automatic dependency setup targets Windows with WinGet, macOS with Homebrew, Ubuntu 22.04/24.04, and Debian 12/13. Other Linux distributions require manual prerequisites and --skip-dependencies.
- AI provider sign-in, model downloads, and license activation are separate user steps.
- This release preserves the AIS compatibility implementation; it does not promise all planned integration-platform routes.
- Installer syntax and mocked safety checks are automated. Clean-machine dependency installation across all OS versions is not yet certified; report installer failures before using this in managed fleet rollouts.
Version-pinned installation and checksum
wget -qO- https://tools.lambogenius.com/lambogenius-integration-migration/0.0.1/install-cli.sh | sh
Invoke-WebRequest 'https://tools.lambogenius.com/lambogenius-integration-migration/0.0.1/install-cli.ps1' -OutFile install-cli.ps1
./install-cli.ps1
SHA-256: 586ecc663f8bcc0259246b7e36a7967a63ee5ea033f3a21baa2a3d08153d7d83
