@mcp-abap-adt/adt-clients 18.0.1 → 18.0.2

package/dist/runtime/atc/types.d.ts

@@ -44,10 +44,12 @@ export type IAtcRunResult = {
      * `FINDING_STATS` as the server sent it — a comma-separated triple, for
      * example `"0,0,1"`.
      *
-     * Not parsed into named counts. Which position is which severity has been
-     * seen once, in a worklist with a single finding at priority 3, which fits
-     * several orderings; inventing `{ errors, warnings, infos }` would publish
-     * two guesses to save a caller one `split(',')`.
+     * Not parsed into named counts, though the ordering is now measured
+     * twice: one priority-3 finding read `"0,0,1"`, one priority-2 finding
+     * read `"0,1,0"` (BTP trial, 2026-09-08 — see the ATC integration test).
+     * Both fit `(priority 1, priority 2, priority 3)` and nothing else fits
+     * both. What is still unseen is a non-zero first position, so naming the
+     * fields would publish one guess to save a caller one `split(',')`.
      */
     findingStats: string;
 };

package/dist/runtime/atc/types.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"types.d.ts","sourceRoot":"","sources":["../../../src/runtime/atc/types.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;GAWG;AAEH;;;;;;;GAOG;AACH,MAAM,MAAM,aAAa,GACrB;IACE;;;;;OAKG;IACH,MAAM,EAAE,KAAK,CAAC;IACd,gDAAgD;IAChD,UAAU,EAAE,MAAM,CAAC;IACnB;;;;;OAKG;IACH,KAAK,EAAE,MAAM,CAAC;CACf,GACD;IACE,8DAA8D;IAC9D,MAAM,EAAE,IAAI,CAAC;IACb,wCAAwC;IACxC,UAAU,EAAE,MAAM,CAAC;IACnB;;;;;;;;OAQG;IACH,YAAY,EAAE,MAAM,CAAC;CACtB,CAAC;AAEN,kEAAkE;AAClE,MAAM,WAAW,aAAa;IAC5B;;;;;;OAMG;IACH,MAAM,EAAE,MAAM,CAAC;IAEf;;;;;;;;;;;;OAYG;IACH,UAAU,EAAE,OAAO,CAAC;IAEpB,sEAAsE;IACtE,UAAU,CAAC,EAAE,MAAM,CAAC;IAEpB,8EAA8E;IAC9E,QAAQ,CAAC,EAAE,MAAM,CAAC;CACnB"}
+{"version":3,"file":"types.d.ts","sourceRoot":"","sources":["../../../src/runtime/atc/types.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;GAWG;AAEH;;;;;;;GAOG;AACH,MAAM,MAAM,aAAa,GACrB;IACE;;;;;OAKG;IACH,MAAM,EAAE,KAAK,CAAC;IACd,gDAAgD;IAChD,UAAU,EAAE,MAAM,CAAC;IACnB;;;;;OAKG;IACH,KAAK,EAAE,MAAM,CAAC;CACf,GACD;IACE,8DAA8D;IAC9D,MAAM,EAAE,IAAI,CAAC;IACb,wCAAwC;IACxC,UAAU,EAAE,MAAM,CAAC;IACnB;;;;;;;;;;OAUG;IACH,YAAY,EAAE,MAAM,CAAC;CACtB,CAAC;AAEN,kEAAkE;AAClE,MAAM,WAAW,aAAa;IAC5B;;;;;;OAMG;IACH,MAAM,EAAE,MAAM,CAAC;IAEf;;;;;;;;;;;;OAYG;IACH,UAAU,EAAE,OAAO,CAAC;IAEpB,sEAAsE;IACtE,UAAU,CAAC,EAAE,MAAM,CAAC;IAEpB,8EAA8E;IAC9E,QAAQ,CAAC,EAAE,MAAM,CAAC;CACnB"}

package/docs/usage/CLIENT_API_REFERENCE.md

@@ -1168,9 +1168,14 @@ if (done.waited) {
 ```
 
 `findingStats` is the server's `FINDING_STATS` triple verbatim, for example
-`"0,0,1"`. It is not parsed into named counts: which position is which severity
-has been observed once, in a worklist with a single priority-3 finding, which
-fits several orderings.
+`"0,0,1"`. It is still not parsed into named counts, but the ordering is no
+longer a single observation: a worklist with one priority-3 finding read
+`"0,0,1"`, and a worklist with one priority-2 finding read `"0,1,0"` (BTP
+trial, 2026-09-08, `ZAC_SHR_ATC_DIRTY` under `ABAP_CLOUD_DEVELOPMENT_DEFAULT`).
+Two points fitting `(priority 1, priority 2, priority 3)` and no other ordering
+that survives both. Position one has still never been seen non-zero, which is
+why this stays a string: `{ errors, warnings, infos }` would name a severity
+nobody here has watched the server count.
 
 **Polling under a bound you choose.** There is no `waitForRun` helper, and its
 absence is the design: waiting needs a stopping condition for a run that does

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mcp-abap-adt/adt-clients",
-  "version": "18.0.1",
+  "version": "18.0.2",
   "description": "ADT clients for SAP ABAP systems - AdtClient and AdtRuntimeClient",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",