# 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.