@uipath/codedapp-convert-sdk 0.1.0-beta.1

package/dist/roslyn-bridge/roslyn-bridge.deps.json

@@ -0,0 +1,157 @@
+{
+  "runtimeTarget": {
+    "name": ".NETCoreApp,Version=v10.0",
+    "signature": ""
+  },
+  "compilationOptions": {},
+  "targets": {
+    ".NETCoreApp,Version=v10.0": {
+      "roslyn-bridge/1.0.0": {
+        "dependencies": {
+          "Microsoft.CodeAnalysis.VisualBasic": "5.6.0",
+          "Newtonsoft.Json": "13.0.3"
+        },
+        "runtime": {
+          "roslyn-bridge.dll": {}
+        }
+      },
+      "Microsoft.CodeAnalysis.Common/5.6.0": {
+        "runtime": {
+          "lib/net10.0/Microsoft.CodeAnalysis.dll": {
+            "assemblyVersion": "5.6.0.0",
+            "fileVersion": "5.600.26.26310"
+          }
+        },
+        "resources": {
+          "lib/net10.0/cs/Microsoft.CodeAnalysis.resources.dll": {
+            "locale": "cs"
+          },
+          "lib/net10.0/de/Microsoft.CodeAnalysis.resources.dll": {
+            "locale": "de"
+          },
+          "lib/net10.0/es/Microsoft.CodeAnalysis.resources.dll": {
+            "locale": "es"
+          },
+          "lib/net10.0/fr/Microsoft.CodeAnalysis.resources.dll": {
+            "locale": "fr"
+          },
+          "lib/net10.0/it/Microsoft.CodeAnalysis.resources.dll": {
+            "locale": "it"
+          },
+          "lib/net10.0/ja/Microsoft.CodeAnalysis.resources.dll": {
+            "locale": "ja"
+          },
+          "lib/net10.0/ko/Microsoft.CodeAnalysis.resources.dll": {
+            "locale": "ko"
+          },
+          "lib/net10.0/pl/Microsoft.CodeAnalysis.resources.dll": {
+            "locale": "pl"
+          },
+          "lib/net10.0/pt-BR/Microsoft.CodeAnalysis.resources.dll": {
+            "locale": "pt-BR"
+          },
+          "lib/net10.0/ru/Microsoft.CodeAnalysis.resources.dll": {
+            "locale": "ru"
+          },
+          "lib/net10.0/tr/Microsoft.CodeAnalysis.resources.dll": {
+            "locale": "tr"
+          },
+          "lib/net10.0/zh-Hans/Microsoft.CodeAnalysis.resources.dll": {
+            "locale": "zh-Hans"
+          },
+          "lib/net10.0/zh-Hant/Microsoft.CodeAnalysis.resources.dll": {
+            "locale": "zh-Hant"
+          }
+        }
+      },
+      "Microsoft.CodeAnalysis.VisualBasic/5.6.0": {
+        "dependencies": {
+          "Microsoft.CodeAnalysis.Common": "5.6.0"
+        },
+        "runtime": {
+          "lib/net10.0/Microsoft.CodeAnalysis.VisualBasic.dll": {
+            "assemblyVersion": "5.6.0.0",
+            "fileVersion": "5.600.26.26310"
+          }
+        },
+        "resources": {
+          "lib/net10.0/cs/Microsoft.CodeAnalysis.VisualBasic.resources.dll": {
+            "locale": "cs"
+          },
+          "lib/net10.0/de/Microsoft.CodeAnalysis.VisualBasic.resources.dll": {
+            "locale": "de"
+          },
+          "lib/net10.0/es/Microsoft.CodeAnalysis.VisualBasic.resources.dll": {
+            "locale": "es"
+          },
+          "lib/net10.0/fr/Microsoft.CodeAnalysis.VisualBasic.resources.dll": {
+            "locale": "fr"
+          },
+          "lib/net10.0/it/Microsoft.CodeAnalysis.VisualBasic.resources.dll": {
+            "locale": "it"
+          },
+          "lib/net10.0/ja/Microsoft.CodeAnalysis.VisualBasic.resources.dll": {
+            "locale": "ja"
+          },
+          "lib/net10.0/ko/Microsoft.CodeAnalysis.VisualBasic.resources.dll": {
+            "locale": "ko"
+          },
+          "lib/net10.0/pl/Microsoft.CodeAnalysis.VisualBasic.resources.dll": {
+            "locale": "pl"
+          },
+          "lib/net10.0/pt-BR/Microsoft.CodeAnalysis.VisualBasic.resources.dll": {
+            "locale": "pt-BR"
+          },
+          "lib/net10.0/ru/Microsoft.CodeAnalysis.VisualBasic.resources.dll": {
+            "locale": "ru"
+          },
+          "lib/net10.0/tr/Microsoft.CodeAnalysis.VisualBasic.resources.dll": {
+            "locale": "tr"
+          },
+          "lib/net10.0/zh-Hans/Microsoft.CodeAnalysis.VisualBasic.resources.dll": {
+            "locale": "zh-Hans"
+          },
+          "lib/net10.0/zh-Hant/Microsoft.CodeAnalysis.VisualBasic.resources.dll": {
+            "locale": "zh-Hant"
+          }
+        }
+      },
+      "Newtonsoft.Json/13.0.3": {
+        "runtime": {
+          "lib/net6.0/Newtonsoft.Json.dll": {
+            "assemblyVersion": "13.0.0.0",
+            "fileVersion": "13.0.3.27908"
+          }
+        }
+      }
+    }
+  },
+  "libraries": {
+    "roslyn-bridge/1.0.0": {
+      "type": "project",
+      "serviceable": false,
+      "sha512": ""
+    },
+    "Microsoft.CodeAnalysis.Common/5.6.0": {
+      "type": "package",
+      "serviceable": true,
+      "sha512": "sha512-eWYNB5e92PSdkQ0xcmy2aLtrvBXNydnVi0Hj/VjaAely6XBqA3By+ClGAJaj4d16pzQmrXPLLK9RDVuS1Ec9xQ==",
+      "path": "microsoft.codeanalysis.common/5.6.0",
+      "hashPath": "microsoft.codeanalysis.common.5.6.0.nupkg.sha512"
+    },
+    "Microsoft.CodeAnalysis.VisualBasic/5.6.0": {
+      "type": "package",
+      "serviceable": true,
+      "sha512": "sha512-biaSTpVc2aVkqg1fQsVmKGqxLnckzdJEOV0aUVPqpV9GczuwtxONyVrlQ2AzZNE6741FkO75tyj0VS6qlxJ/PA==",
+      "path": "microsoft.codeanalysis.visualbasic/5.6.0",
+      "hashPath": "microsoft.codeanalysis.visualbasic.5.6.0.nupkg.sha512"
+    },
+    "Newtonsoft.Json/13.0.3": {
+      "type": "package",
+      "serviceable": true,
+      "sha512": "sha512-HrC5BXdl00IP9zeV+0Z848QWPAoCr9P3bDEZguI+gkLcBKAOxix/tLEAAHC+UvDNPv4a2d18lOReHMOagPa+zQ==",
+      "path": "newtonsoft.json/13.0.3",
+      "hashPath": "newtonsoft.json.13.0.3.nupkg.sha512"
+    }
+  }
+}

package/dist/roslyn-bridge/roslyn-bridge.runtimeconfig.json

@@ -0,0 +1,14 @@
+{
+  "runtimeOptions": {
+    "tfm": "net10.0",
+    "framework": {
+      "name": "Microsoft.NETCore.App",
+      "version": "10.0.0"
+    },
+    "configProperties": {
+      "System.Globalization.Invariant": false,
+      "System.Reflection.Metadata.MetadataUpdater.IsSupported": false,
+      "System.Runtime.Serialization.EnableUnsafeBinaryFormatterSerialization": false
+    }
+  }
+}

package/dist/skills/fix-converted-app/SKILL.md

@@ -0,0 +1,333 @@
+---
+name: fix-converted-app
+description: Finish a converted Apps project — the generated React code in an output directory. Fixes what `conversion-report.json` reports, anything the developer found by testing the app by hand, and anything a screenshot of the original next to the converted app shows. Fixes it in the generated code whether the fault is this app's or the converter's, and writes the systemic ones up so they can be fixed at the source. Use after `npm run convert`.
+argument-hint: <output directory, e.g. out/MyApp or .> [what is wrong, in your own words, or a screenshot of the original]
+---
+
+# Fix a converted app
+
+The converter wrote a React + TypeScript project into the output directory and a
+`conversion-report.json` beside it. Your job is to make that app behave and look like the Apps
+app it came from: what the report already knows about, what the developer found by using the
+app, and what a screenshot of the two side by side shows.
+
+The output directory is the first part of `$ARGUMENTS` (`.` means the current directory).
+Anything else in `$ARGUMENTS` is the developer telling you what is wrong. Pick the path that
+matches what you were given, and more than one can apply:
+
+- nothing but a directory → **Path A**, work the report;
+- a description of something that misbehaves → **Path B**;
+- a screenshot of the original app, or "it does not look right" → **Path C**.
+
+## Hard rules
+
+1. **Edit only files inside the output directory.** Never edit the converter itself
+   (`packages/`, `tools/`), even when the real defect is there — you are almost certainly not
+   in that repository anyway. Fix it in the generated code and write it up (rules 5 and 6).
+2. **Never modify `conversion-report.json` or `conversion-log.ndjson`.** They are the record
+   handed back to the converter team. The report is read-only on disk; leave its permissions.
+3. **Never edit `node_modules`, `dist`, `uipath.json` or `.env*`.**
+4. **The original app is the specification.** Translate what it does; do not improve it, and
+   do not invent behaviour you have not checked. If you cannot establish what Apps does, say
+   so in the log rather than guessing.
+5. **Fix everything you can in this project, whoever is at fault.** A defect the converter
+   would repeat on every app is still fixed HERE, in the generated code, because that is what
+   unblocks the developer today. The difference the blame makes is only what you write down.
+6. **Write `conversion-fixes.md`** in the output directory, with three parts: what you changed
+   and why; what you could not fix; and a section headed `## For the converter team` listing
+   every defect that is systemic, each with the file and symbol you patched, the VB or the
+   Apps behaviour it should match, and a minimal example. That section is what the developer
+   sends back to us, and it is also what they will need when a future conversion overwrites
+   your patch — so write it even when the fix here was easy.
+
+## Path A — the report
+
+1. Read `<out>/conversion-report.json` and work through `issues` where `blame` is
+   `"converter"`. `blame: "source-app"` is the only kind you do NOT fix — not out of
+   deference, but because the app itself is broken (an expression naming a control that does
+   not exist) and only its author knows what it was meant to say; report those and move on.
+   `by-design` needs nothing. `expressionRows` lists deliberate, measured approximations —
+   read them for context, act on them only if asked.
+2. Some reports also carry `runtime`-scoped issues and a `runtime` block: those come from the
+   converter team driving both apps through the same steps, and they are the most concrete
+   issues in the file because each one states what Apps did and what this app did. Treat them
+   like any other converter issue. Neither you nor the developer can re-run that comparison —
+   it is internal tooling — so note in the log that the fix is unconfirmed by it.
+3. Fix, then `npm run build` in the output directory (it typechecks and bundles). A freshly
+   converted project has no `node_modules` — the converter does not install anything — so run
+   `npm install` there first if the directory is absent. If installing is not possible
+   (offline), skip the build and say in the log that the fix is unverified. A generated app is
+   expected to compile with zero errors; if it does not, that is a defect worth writing up
+   even when it is not what you were asked to fix.
+4. Write the log and report back.
+
+### Where each issue lives
+
+| issue code | what you will find | what to do |
+|---|---|---|
+| `expression-no-rule`, `expression-unbound` (property) | In `src/pages/<Page>.tsx` the prop reads `notConvertedValue("<VB>")` or `notConvertedFlag("<VB>", <default>)`; `where` and `location` name page, control and prop. | Replace the marker with TypeScript computing the VB's value. Read state through the accessors already imported in that page. |
+| `expression-no-rule` (source binding, column, page, tab) | `src/pages/<Page>.bindings.ts` has a `TODO` block returning empty rows or `undefined`. | Implement the binding with the helpers in `src/lib/data.ts` and `src/lib/compat.ts`. |
+| `rule-unimplemented`, `rule-expression-unconverted` | In `<Page>.bindings.ts`, the handler `<control>_<event>` holds a `// TODO` or a `notConvertedInput("<VB>")`. | Implement the statement the rule describes (`method` names the Apps rule kind, e.g. `vb-set-value`). |
+| `rule-bad-target` | Same handler; the assignment target was not understood. | Write the assignment the VB intends. |
+| `event-undeliverable` | The handler exists but the component never calls it. | Wire the prop the message names, in `src/components/ui/`. |
+| `property-unmapped` | An authored property reached no component prop. | Add the prop to the component and pass it from the page — unless Apps' own control ignores that property too, in which case log it and change nothing. |
+| `style-unmapped` | An authored style produced no CSS. | Add the rule to the control's class in `src/pages/<Page>.module.css`. |
+| `control-unsupported` | An inert placeholder. | Implement it only if the message gives enough to go on; otherwise leave it and say why. |
+| `emit-inconsistent` | Described in the message. | Fix as described. |
+| `runtime-*` | The app was driven beside the low-code app: `step` is what was done, `expected` what Apps showed or sent, `actual` what this app did. | Make the code produce `expected`. For `runtime-request-differs` compare the bodies field by field. For `runtime-text-differs` find the binding behind the control. For `runtime-request-missing`/`-extra` look at the control's source hook and its handler. |
+
+### Resolving what an unconverted expression REFERS to
+
+Rewriting a refused expression needs more than its VB text: what an identifier in it
+denotes, and what that thing holds. Most of it is already in the output directory.
+
+| you need to know | read |
+|---|---|
+| an entity's fields and what each holds | `src/types/entities.ts` — the doc comment on each interface lists every field with its declared type (`Guid`, `Decimal`, `DateTimeOffset`, `file attachment`, `list of number`, or a related entity). The shape is open, so the compiler will not tell you; this table will. |
+| which entity a control's rows came from | the control's `entity` prop in `src/pages/<Page>.tsx`, and `src/lib/entity-ids.ts` |
+| a process's real key, a bucket's real name, the folder any resource was authored in | `src/lib/resource-folders.ts` |
+| what a media name resolves to | `src/lib/app-media.ts` |
+| a control's authored literal defaults | `src/store/defaults.ts`, keyed `<Page>/<Control>` |
+| a control's id in the original app | `src/components/ui/provenance.ts` |
+| an action app's arguments and outcomes | `src/lib/action-schema.ts` |
+| the VB that failed, and where it sat | the issue's `vb`, `where` and `location`; `expressionRows` for expressions that converted with a measured approximation |
+
+**The `.uiapp` is NOT in the output directory.** The report's `generatedFrom` names the
+file; ask the developer for it when the tables above are not enough — a rule's nesting, a
+property you cannot find, or an expression whose identifiers resolve to nothing you can
+see. It is JSON, and the parts worth knowing are:
+
+- `models[]` — one per page (`type: "form"`) and one container per Data Service
+  connection (`type: "entity"`). A page carries `controls`, keyed by control id, each with
+  `name`, `component`, `config`, `properties` and `ruleInstances`.
+- `models[].instances[]` on an entity container — the entities themselves, each with typed
+  `fields[]`. This is where `src/types/entities.ts` gets its table, so you rarely need it.
+- `models[].expressions` — the VB. Every scope holds
+  `expressions: { "<expressionId>": { "expression": "<VB text>" } }`.
+- A bound property is `properties.<name> = { valueType: "vb-expression", value: {
+  expressionId } }`. Follow the id into the expression map to read what was authored.
+
+**An expression id with no text is a slot the designer never filled in.** Apps writes an
+id for every bindable property whether or not anything was authored there, so the presence
+of an id proves nothing — only text does. That distinction is load-bearing and easy to get
+backwards: an image control with no `url` text renders nothing in Apps, while one whose
+`url` was authored but evaluates to nothing renders its "unable to render" placeholder.
+Where the emitted code omits a prop entirely, the slot was blank; where it passes one that
+happens to be undefined at run time, it was authored.
+
+
+## Path B — a bug the developer found by hand
+
+This is the common case once the app runs, and the report will not mention it. Work in this
+order; skipping step 2 is how a wrong "fix" gets written.
+
+1. **Get the evidence, from the developer's browser.** You can start the app
+   (`npm run dev` in the output directory, `npm install` first if there is no
+   `node_modules`) but you cannot see it; they can. Ask for the three things that decide
+   most of these: the browser console output while the problem happens, the control's name
+   from the inspector — every control carries `data-uiapp-name="<authored name>"`, which is
+   exactly the name to search for in `src/pages/` — and a screenshot. A control that threw
+   while rendering leaves a marked placeholder instead of disappearing, and names itself in
+   the console, so that alone often identifies it. If the app says it is not configured, the
+   dev server was started BEFORE the project was written or re-written: restart it, because
+   the platform settings are injected into the page at startup.
+2. **Establish what the original does** before changing anything. In order of authority: the
+   low-code app itself, if the developer can open it or screenshot it; the `.uiapp` export
+   (the report's `generatedFrom` names the file) — its `models[].controls` hold each control's
+   authored properties and expressions under the same names; the report's `expressionRows`.
+   A difference is not automatically a converter bug: Apps has its own quirks, and a converted
+   app that is *more* correct than Apps is still a difference worth recording rather than
+   "fixing".
+3. **Locate the code.** The map is in the next section.
+4. **Fix it here either way, and say which kind it is.** Wrong for THIS app only — a value, a
+   binding, a missing wire — is a local fix and a line in the log. Wrong for EVERY app — a
+   helper in `src/lib/`, a component that never accepts a property, a rule that mistranslates
+   — is fixed in this project exactly the same way, and additionally written under
+   `## For the converter team` so it can be fixed at the source. Never leave the developer
+   with a broken app because the real defect is upstream.
+5. **Fix the smallest thing that makes it behave like the original.**
+6. **Verify what you can, and be honest about the rest.** `npm run build` is yours to run and
+   proves the code compiles; it proves nothing about behaviour. For that, ask the developer
+   to repeat their steps and send the console output or a screenshot. Never report a
+   behavioural fix as confirmed on the strength of having written it.
+7. **Log it**, including what you verified, how, and what is still unconfirmed.
+
+## Path C — two screenshots, side by side
+
+The developer gives you a picture of the low-code app and a picture of the converted one, and
+you find the differences by LOOKING at them. There is no harness and no browser automation
+here: those are internal tools the developer does not have. Everything below works from two
+images and, when a measurement is needed, one line they paste into their browser.
+
+Use this whenever the complaint is about how a page looks, and whenever you are about to tell
+someone a page "looks right".
+
+1. **Check the two pictures are comparable.** Same page, same data, same window width. If
+   they are not, ask for a matching pair rather than reading meaning into the mismatch — a
+   narrower window re-wraps a layout and invents differences that are not there. If you were
+   given only the low-code picture, ask for the converted one; you cannot take it yourself.
+2. **Read both in the same order, top to bottom and left to right, and write every
+   difference down before explaining any of them.** Explaining as you go makes you stop at
+   the first one. Work the list: is every control present, and in the same order; is each
+   one's text identical, character for character; are heading and label colour, weight and
+   size the same; do the fields have the same frame; is spacing and alignment the same; is
+   anything cut off, overlapping or missing a scrollbar; do empty states match ("No data" on
+   one side against real rows on the other); are images shown or placeholdered.
+3. **Turn each difference into a hypothesis before touching code.** Text present on one side
+   and absent on the other is usually invisible rather than missing — an authored colour that
+   matches the background. Text at a different size or weight is usually a named heading or
+   label style overriding the authored typography. A different STRING is an expression or a
+   format helper, not CSS. A missing row is a data call. A control in the wrong place is
+   layout; a control that is not there at all is the component.
+4. **Measure rather than squint, without any tooling.** The eye cannot separate 28px from
+   32px, and white text on a white page looks exactly like a control that failed to render.
+   Ask the developer to open each app, press F12, paste this into the Console and send you
+   both answers — it works in the low-code app and the converted one alike:
+
+   ```js
+   (function (text) {
+     const all = [...document.querySelectorAll('*')].filter(
+       (e) => e.children.length === 0 && (e.textContent || '').trim() === text);
+     const el = all[all.length - 1];
+     if (!el) return 'no element with exactly that text';
+     const c = getComputedStyle(el);
+     const p = el.parentElement ? getComputedStyle(el.parentElement) : c;
+     return { text, color: c.color, fontWeight: c.fontWeight, fontSize: c.fontSize,
+       fontFamily: c.fontFamily, background: c.backgroundColor, behind: p.backgroundColor,
+       textAlign: c.textAlign, box: el.getBoundingClientRect().toJSON() };
+   })('the exact text you can see')
+   ```
+
+   Two answers side by side settle colour, weight, size, font, the background behind the
+   text and the box, in seconds. That is how a heading that looked "missing" turned out to be
+   the authored white being applied where Apps ignores it and renders 32px.
+5. **Fix in the generated code, then ask for one more screenshot of that page.** A visual fix
+   is not finished until the second pair agrees. List in the log the differences that remain
+   and why, and put anything systemic under `## For the converter team`.
+
+Things this comparison catches that nothing else does: invisible text, a heading at the wrong
+size or weight, a control that rendered off-screen, a grid whose columns do not line up, a
+page that cannot scroll, an image placeholder where the original shows a picture, and text
+that is right but formatted differently. Every one of those has happened on a real app.
+
+### Symptom → where to look
+
+| What the developer sees | Look at | Usually |
+|---|---|---|
+| A page is blank, or blank until a refresh | the console; `src/routes.tsx` | something threw while rendering OR while unmounting the previous page; each route is wrapped in a boundary, so read which one it names |
+| A control renders but shows nothing / "No data" | the `use…Source` hook in `<Page>.bindings.ts`, then `src/lib/data.ts` | the query's filter or expansion fields, entity-id resolution, the folder id, or a list source handed on where an array was expected |
+| A dropdown or grid editor has no options | the column's `options` in the page, `dropdownValues` in the grid component | a `{ data, totalRecords }` list source where an array was expected |
+| A button does nothing, or only part of what it should | `<control>_<event>` in `<Page>.bindings.ts` | the handler is a TODO, its guard is false (an unset variable), one rule in the chain threw and stopped the rest, or the component never calls it |
+| Typing behaves differently: a mask, decimals, a prefix, separators | the control in `src/components/ui/`, then the authored property in `<Page>.tsx` | an authored input property that reaches no component prop — the page shows what was authored, the component decides whether it is honoured |
+| An image or document does not appear | `src/lib/app-media.ts` and `assetUrl` in `src/lib/runtime.ts`; the Network tab | a media asset resolved by title, an entity attachment that has to be downloaded before it can be shown, or an external URL the host refuses |
+| A value set on one page is not there on another | `src/store/` and the `setAppVar` call in the first page's handler | an app variable written to the wrong name, or a page that re-runs its load rules and overwrites it |
+| The value is right but reads wrong | `src/lib/compat.ts` | a VB-vs-JavaScript formatting difference — see the idioms below |
+| Fonts, colour, weight or size differ | `src/pages/<Page>.module.css` | a control with a NAMED heading or label style takes its typography from Apps' preset, not from the authored properties; only `customized` uses what the designer set |
+| The page does not scroll, or is cut off | `src/styles/tokens.css` | the page host scrolls and the page is as tall as its content |
+| A backend call fails (400/403/404) | the Network tab, then `src/lib/data.ts` and `src/lib/resource-folders.ts` | a process needs its RELEASE key rather than the package id, a bucket its real Orchestrator name rather than the VB identifier, a choice set the tenant-wide flag — or `uipath.json` is missing a scope |
+| Session values are empty (`CurrentUser.*`) | `src/lib/sdk.ts` | the claims the token actually carries |
+| A validation message differs | `useControlValidation` in `src/lib/runtime.ts` | Apps checks by control KIND, only once a value is filled, and a pattern rule outranks a length rule on the same field |
+| A popup, toast or spinner behaves differently | `src/lib/rules.ts`, `src/lib/overlays.tsx` | the rule's own options (modal, position, seconds) |
+
+### Differences that are not bugs
+
+Measured on real apps. Reporting one of these as fixed, or "fixing" it, makes the converted
+app wrong:
+
+- A control with a named heading or label style shows Apps' preset, not the authored font,
+  size, weight or colour. Only `customized` uses what the designer set.
+- Apps' own button ignores an authored `url`, and its image an authored `icon`.
+- A label authored white on a white page is invisible in BOTH apps. That is the app's own
+  styling, not a conversion fault.
+- Apps' grid shows an unexpanded relationship cell as `[object Object`; the converted grid
+  shows the related record's name. Ours is better; leave it.
+- Apps does not always re-render a label after a load rule changes what it reads, so the
+  low-code app can show a stale value where the converted app shows the current one.
+- Apps' Preview can fail to render the lower part of a long page, and can fail to fetch
+  documents. An empty area on the Apps side is not proof the converted side is wrong.
+- Apps does not draw what is below the fold until the page is scrolled to it, and it shows
+  "Loading your app" for several seconds first. A screenshot of the Apps side is only
+  evidence once it has been scrolled to the bottom and back and the page has settled —
+  otherwise a whole section reads as something the converter invented.
+- Apps wraps every control in a panel named after it (`forms-host-table-panel` around
+  `forms-host-table-control`); the converted app has no such wrapper. Extra elements in the
+  Apps DOM are not missing elements in ours.
+
+### Defects already found and fixed at least once
+
+Every row happened on a real app. If what the developer describes matches one, check that
+first — and if this project still has it, fix it here and put it under
+`## For the converter team`, because it means the version that converted this app predates
+the fix.
+
+| Area | What it looked like | Where it was | What it needed |
+|---|---|---|---|
+| Data | Starting a process fails, 400 "Undefined process" | `src/lib/data.ts` | the SDK's `processKey` is the RELEASE key, not the package id — list the folder's releases, match the package id, start with the match's `key` |
+| Data | A bucket upload or download says the bucket does not exist | `src/lib/data.ts`, `resource-folders.ts` | send the bucket's real Orchestrator name, not the VB identifier the expressions use |
+| Data | A choice set is "not found" once deployed | `src/lib/data.ts` | list with the tenant-wide flag, not scoped to the app's install folder |
+| Data | An entity query is refused for "not supplying expansion fields" | `src/lib/data.ts` | every fetch has to pass expansion fields |
+| Data | A dropdown or grid shows only the first page of rows | `src/lib/data.ts` | follow the cursor to the end; Apps asks for everything |
+| Data | `FetchOne` pulls the whole table | the page's binding | ask for one record, and express the authored start as a page |
+| Data | A failed read leaves a silent "No data" | `src/store/controls.ts` | Apps shows an error toast; say what failed |
+| Session | `CurrentUser.*` is empty | `src/lib/sdk.ts` | read the signed-in user from the access token's claims |
+| Session | Signing in loses the page the user opened | `src/lib/sdk.ts` | stash the path before initialising, restore it after the callback |
+| Session | Data calls fail right after sign-in, then recover | `src/lib/sdk.ts` | hold the first render until the SDK is authenticated |
+| Expressions | A date renders as `Sun Mar 01 2026 00:00:00 GMT…` | `src/lib/compat.ts` | .NET's default, which is the invariant `MM/dd/yyyy` |
+| Expressions | A date or number looks different on another machine | `src/lib/compat.ts` | Apps is invariant-culture; never `toLocaleString` |
+| Expressions | A page is blank and the console says "unsupported .NET format specifier" | `formatDate` / `formatNumber` | implement the standard specifiers (`C`, `D3`, `E`, `G`, `N2`, `P1`, `X`, `s`, `u`, `o`…) |
+| Expressions | `42 + 19.99` shows `61.989999999999995` | `src/lib/compat.ts` | decimal arithmetic through the `dec*` helpers |
+| Expressions | `"…" & True` shows `true` | the concatenation | VB renders a Boolean as `True`/`False` |
+| Expressions | A grid cell shows `True` where Apps shows `true` | the grid's cell text | a grid cell is not a text field |
+| Expressions | `.join` or a spread throws on an unset list variable | the store default | an unset list variable is an empty list |
+| Components | A mask, prefix, decimals or separators are ignored while typing | `src/components/ui/` | the authored property reached no component prop |
+| Components | A grid's dropdown editor has no options | the grid component | unwrap the `{ data }` list source |
+| Components | A bold button renders regular | `src/styles/tokens.css` | a zero-specificity reset, so the authored weight wins |
+| Components | A heading is invisible, or the wrong font or size | the page's CSS module | a named heading or label style overrides the authored typography |
+| Components | Leaving a page with a document viewer blanks the app | the viewer component, `src/routes.tsx` | guard the unmount cleanup, and keep every route in its own boundary |
+| Components | An entity attachment shows no image | the image component | download the attachment and show it through an object URL |
+| Layout | A long page cannot scroll | `src/styles/tokens.css` | the page host scrolls; the page is as tall as its content |
+| Components | An icon draws at 24px whatever size the author set | `src/styles/tokens.css` | Material Icons pins `font-size` on its own class; the glyph must inherit from the control, and everything under a mis-sized icon sits too high |
+| Components | An open dropdown has no blue ring | `src/styles/tokens.css` | Apps draws 2px `#0067DF` on the trigger while its panel is open, and 1px on the grid's search box |
+| Components | A grid's row icons grey out while another row is being edited | the edit grid component | Apps keeps them lit; only a disabled grid dims them |
+| Components | A grid's rows stop short of the right edge | the edit grid component | a column with no authored width takes `flex: 1` and shares the free space, as Apps' grid does |
+| Components | A dropdown, multi-select or uploader is invisible to an end-to-end selector | the component registry | Apps tags both the dropdown and the multi-select `forms-host-combo-box-control`, and its uploader `upload-file-input` on the file input — there is no `forms-host-file-picker-control` in its vocabulary |
+| Project | The whole app is blank and the console shows an unresolved import | the emitted imports | an import naming a file the project does not contain |
+| Project | The app runs but `npm run build` fails | the pages and components | a prop passed to a component that never declared it, or a name used without importing it |
+
+## The generated project
+
+| Path | What it is |
+|---|---|
+| `src/pages/<Page>.tsx` | the page's JSX: one element per control, `ctl` is the authored name |
+| `src/pages/<Page>.bindings.ts` | that page's event handlers and source hooks — where rules live |
+| `src/pages/<Page>.module.css` | that page's authored styles, one class per control |
+| `src/components/ui/` | the control components, plus `ui-base.tsx` (shared props, `Guarded`) |
+| `src/lib/runtime.ts` | the accessors expressions call: `getAppVar`/`setAppVar`, control props, validation |
+| `src/lib/rules.ts` | navigation, toasts, spinners, confirmations |
+| `src/lib/data.ts` | every backend call: entities, choice sets, processes, queues, buckets, tasks |
+| `src/lib/compat.ts` | the VB-vs-JavaScript behaviour differences. Read this before writing a formatting fix |
+| `src/lib/resource-folders.ts` | which folder each backend resource lives in, and the keys to reach it |
+| `src/store/` | app variables, control state and data sources (Redux Toolkit) |
+| `src/styles/tokens.css` | every colour and font, plus the app-wide layout rules |
+
+## VB → TypeScript, as the generated code does it
+
+- `&` concatenates with `Nothing` as `""`; a Boolean in a concatenation is `True`/`False`
+  (`boolText`), a date is the invariant `MM/dd/yyyy` (`formatDate`).
+- Apps' VB engine runs under the invariant culture: dates and numbers render the same for
+  every viewer. Never reach for `toLocaleString`.
+- A grid CELL prints a boolean as `true`/`false`; a text field prints `True`/`False`.
+- `.ToString(format)` on a date or number goes through `formatDate` / `formatNumber`, which
+  implement the .NET format strings; `String.Format` goes through `formatString`.
+- Decimals are exact: `dec`, `decAdd`, `decMul`, `decRound` from `src/lib/compat.ts`.
+- `If(c, a, b)` is `c ? a : b`; `Nothing` is `null`; an unset list variable reads as `[]`.
+- LINQ maps onto array methods: `Where`→`filter`, `Select`→`map`, `First`→`firstOrThrow`,
+  `Any`→`some`, `Sum`→`reduce`. `ThisRow` inside a list template is the `row` parameter.
+
+## What you must not do
+
+- Do not change the report, the log, or the converter.
+- Do not rename generated symbols, reorder files, or reformat code you did not need to touch.
+- Do not remove a `notConverted…` marker without replacing it with a real implementation.
+- Do not fix `source-app` or `by-design` issues.
+- Do not claim a fix works because it should. Say what you ran and what you saw.

package/package.json

@@ -0,0 +1,39 @@
+{
+  "name": "@uipath/codedapp-convert-sdk",
+  "version": "0.1.0-beta.1",
+  "description": "Convert a UiPath Apps export (.uiapp) into a React + TypeScript coded app. The SDK behind `uip codedapp convert`.",
+  "license": "SEE LICENSE IN LICENSE.txt",
+  "author": "UiPath",
+  "type": "module",
+  "main": "./dist/index.js",
+  "types": "./dist/index.d.ts",
+  "exports": {
+    ".": {
+      "types": "./dist/index.d.ts",
+      "default": "./dist/index.js"
+    }
+  },
+  "files": [
+    "dist"
+  ],
+  "engines": {
+    "node": ">=20"
+  },
+  "repository": {
+    "type": "git",
+    "url": "https://github.com/UiPath/apps-dev-tools.git",
+    "directory": "lowcode-to-procode-migration/packages/sdk"
+  },
+  "publishConfig": {
+    "registry": "https://registry.npmjs.org/",
+    "access": "public"
+  },
+  "scripts": {
+    "build": "tsx build.mts",
+    "smoke": "node -e \"import('./dist/index.js').then((m) => console.log(Object.keys(m).sort().join(', ')))\""
+  },
+  "dependencies": {
+    "decimal.js": "10.6.0",
+    "typescript": "^5.4.0"
+  }
+}