@mcp-abap-adt/interfaces-adt 1.2.0 → 2.0.0

package/CHANGELOG.md

@@ -5,6 +5,64 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [2.0.0] - 2026-09-21
+
+### Changed
+
+- **BREAKING: `IAdtTransportObjectActions` takes a fifth type parameter**,
+  `TObjects`, for the reading added below. Every implementation and every
+  declared use names it.
+
+- **BREAKING: `removeObject` requires `object.position`.** It took
+  `IAbapObjectEntry` whole, where the field is optional, and the member took
+  the whole type because nothing said the server needed it. It does. Measured
+  against an on-premise system, 2026-09-21: 22 objects asked for by
+  `pgmid`/`type`/`name` alone each answered `200` with the usual echo
+  document, and re-reading the task found all 22 still on it. The same
+  documents carrying `tm:position` — nothing else added — removed every one,
+  22 down to 0, each confirmed by a re-read.
+
+  The parameter is `IAbapObjectEntry & { position: string }` rather than a new
+  type: the field belongs to the entry, and what changes is that this member
+  insists on it. `addObject` still does not, because an entry that does not
+  exist yet has no position.
+
+- **BREAKING: `createTask` requires `targetUser`**, and the options argument
+  with it. This shipped saying the server would decide whose task it is when
+  `tm:targetuser` was absent. It does not: the call without the attribute was
+  refused with `400 SCTS_ADT_MSG 009`, *"User  does not exist in the system
+  (or locked)"* — two spaces, an empty name — and the same call carrying it
+  answered 200 and a task number. Measured on the same run.
+
+  Nothing below the caller can fill it in: `IAbapConnection` does not expose
+  who is authenticated, and finding out costs a second request.
+
+### Added
+
+- **`readObjects`** — the objects a request or task holds, each with the
+  `tm:position` that `removeObject` now needs.
+
+  It is a separate member because it is a separate representation. The
+  transport resource answers differently depending on the `Accept` the request
+  carries, and measured on the same run, a `GET` naming none comes back
+  without a single `tm:abap_object` in it. A reader that sends no `Accept` —
+  the usual one — therefore cannot answer this however its result is parsed;
+  `application/vnd.sap.adt.transportorganizer.v1+xml` is the media type that
+  carries the list.
+
+  Without it `removeObject` would require a value the package offers no way to
+  obtain, leaving a caller to assemble the request themselves — the layering
+  this package exists to prevent.
+
+### Why a major so soon after 1.2.0
+
+1.2.0 declared these members from captures of Eclipse and unit tests over the
+documents it sent. Eclipse sends both attributes on every call, so nothing in
+a capture could show that either was load-bearing. The first run against a
+server found both. The contract is what was wrong, and a contract that permits
+a call which cannot work is worse than one that forbids it: the old signatures
+type-check today and fail — `createTask` at runtime, `removeObject` silently.
+
 ## [1.2.0] - 2026-09-21
 
 ### Added

package/README.md

@@ -24,7 +24,52 @@ npm install @mcp-abap-adt/interfaces-adt
 | `token/`, `session/`, `serviceKey/`, `store/` | token providers and refreshers, stores and their error codes |
 | `validation/`, `Headers.ts` | header validation; `HEADER_SAP_*`, `HEADER_UAA_*`, `HEADER_BTP_DESTINATION`, `HEADER_MCP_DESTINATION`, `HEADER_MCP_URL`, `AUTH_TYPES`, `AuthType` |
 
-The contract rules — what a member answers, how a strategy is supplied, how a contract is built — are in [`docs/architecture/ARCHITECTURE.md`](../../docs/architecture/ARCHITECTURE.md). Domain-by-domain documentation with examples stays in the [`@mcp-abap-adt/interfaces` README](../interfaces/README.md); the contracts it describes are these. Contracts added after the split are documented here only — the facade is frozen at its 44.0.0 surface and does not export them.
+The contract rules — what a member answers, how a strategy is supplied, how a contract is built — are in [`docs/architecture/ARCHITECTURE.md`](../../docs/architecture/ARCHITECTURE.md). Domain-by-domain documentation with examples stays in the [`@mcp-abap-adt/interfaces` README](../interfaces/README.md); the contracts it describes are these.
+
+**The facade is pinned to its 44.0.0 surface, not frozen against additions.** This said the opposite until 2.0.0, and 45.1.0 had already disproved it: `IAbapObjectEntry` and `IAdtTransportObjectActions` were added here and re-exported there. `tools/check-surface.js` compares the built facade against `surface-44.0.0.txt` in both directions — nothing from 44.0.0 may disappear and nothing may appear — and an addition is made deliberate rather than impossible by being written into `tools/surface-added.txt`, one `<name> <kind>` per line. A symbol added here and not written there fails the check; a line written there for a symbol the facade does not export fails too.
+
+## The transport request's object list
+
+`IAdtTransportObjectActions` and `IAbapObjectEntry` (`adt/IAdtTransport.ts`, since 1.2.0) declare what can be done to a request's object list and to its tasks: `removeObject`, `addObject`, `createTask`, `readActionLog`, `readObjects`.
+
+They exist because deleting an ABAP object does not free its name. The CTS object-directory entry stays on the request that carried it, and until it is detached a create of the same name is refused with `CTS_WBO_API 019` — **even when that same request is passed as `corrNr`**. Without a way to detach one, the ways out are releasing the whole request, shipping everything else in it, or SE09 by hand.
+
+Two of the signatures say things a capture cannot. 1.2.0 was declared from captures of Eclipse ADT, and Eclipse sends every attribute on every call, so nothing in a capture could show which of them the server needs. The first run against an on-premise system, 2026-09-21, found two that it does:
+
+| call | what the server does |
+|---|---|
+| `createTask` without `tm:targetuser` | refused — `400 SCTS_ADT_MSG 009`, *"User&nbsp;&nbsp;does not exist in the system (or locked)"*: two spaces, because the owner resolved to an empty name |
+| `removeObject` without `tm:position` | `200` with the usual echo document and **nothing removed** — 22 entries asked for by `pgmid`/`type`/`name` alone, 22 still on the task afterwards |
+
+So `createTask` requires `targetUser` and `removeObject` requires `position`, and `readObjects` was added because otherwise the second would require a value this package offers no way to obtain. It is its own member rather than an option on a reader because it is its own representation: a `GET` naming no `Accept` comes back without a single `tm:abap_object` in it, and `application/vnd.sap.adt.transportorganizer.v1+xml` is the media type that carries the list.
+
+`addObject` still takes an entry without a position — one that does not exist yet has none.
+
+## Migrating to 2.0.0
+
+Three changes, all of them in `IAdtTransportObjectActions`. An implementation or a caller on 1.2.0 does this:
+
+```ts
+// 1. Name the fifth type parameter: what readObjects answers.
+type Actions = IAdtTransportObjectActions<
+  string, string, { number: string }, string[],
+  MyEntry[]                      // ← new
+>;
+
+// 2. Read the position rather than leaving it out.
+const listed = await actions.readObjects(task);      // ← new member
+const entry = listed.ok
+  ? listed.getResult().value.find((o) => o.name === 'ZCL_X')
+  : undefined;
+if (entry) await actions.removeObject(task, { ...entry });
+
+// 3. Name the user the task is for.
+await actions.createTask(request, { targetUser: 'DEVELOPER' });
+```
+
+Both old call shapes compile against 1.2.0 and cannot work: `createTask(n)` throws where an implementation reads `options.targetUser`, and `removeObject(n, { name, type })` answers a success while removing nothing. That is why this is a major rather than a deprecation — there is no window in which the old shape does something useful.
+
+`src/__typechecks__/transportObjectActions.ts` holds both wrong shapes as `@ts-expect-error`, so a future loosening stops compiling instead of shipping.
 
 ## Coming from `@mcp-abap-adt/interfaces`
 

package/dist/adt/IAdtTransport.d.ts

@@ -132,7 +132,15 @@ export interface IAbapObjectEntry {
     pgmid?: string;
     /** `tm:obj_desc` — the description ADT shows beside the entry. */
     description?: string;
-    /** `tm:position` — the entry's position in the task, e.g. `000025`. */
+    /**
+     * `tm:position` — the entry's position in the task, e.g. `000025`.
+     *
+     * Optional here because an entry being described is not always an entry
+     * being addressed: {@link IAdtTransportObjectActions.addObject} has no
+     * position to give, since the entry does not exist yet.
+     * {@link IAdtTransportObjectActions.removeObject} requires one, and says in
+     * its own words what happens without it.
+     */
     position?: string;
 }
 /**
@@ -152,19 +160,40 @@ export interface IAbapObjectEntry {
  * `removeObject` the ways out are releasing the whole request, shipping
  * everything else in it, or SE09.
  *
- * Four members and no composite: the order a caller uses them in, and what
- * they do when `addObject` is refused, is theirs.
+ * Five members and no composite: the order a caller uses them in, and what
+ * they do when `addObject` is refused, is theirs. One of them,
+ * {@link IAdtTransportObjectActions.readObjects}, is there because
+ * {@link IAdtTransportObjectActions.removeObject} needs a value nothing else
+ * here answers — which is a dependency between readings, not a composite.
  */
-export interface IAdtTransportObjectActions<TRemoved, TAdded, TTask, TActionLog> {
+export interface IAdtTransportObjectActions<TRemoved, TAdded, TTask, TActionLog, TObjects> {
     /**
      * Detach one object from a request or task.
      *
      * Addressed at the **task** that holds the object: a request's objects live
-     * on its tasks. The answer echoes the object it was asked about and says
-     * nothing else, so {@link IAdtTransportObjectActions.readActionLog} is what
-     * confirms the removal happened.
+     * on its tasks.
+     *
+     * **`position` is what identifies the entry, and the call does nothing
+     * without it.** This took `IAbapObjectEntry` whole when it shipped, which
+     * made the field optional. Measured against an on-premise system,
+     * 2026-09-21: 22 objects asked for by `pgmid`/`type`/`name` alone each
+     * answered `200` with the usual echo document, and a re-read of the task
+     * found all 22 still on it. The same documents carrying `tm:position` — and
+     * nothing else added — removed every one, 22 down to 0, each confirmed by a
+     * re-read.
+     *
+     * The number comes from
+     * {@link IAdtTransportObjectActions.readObjects}, which is the reading that
+     * carries it.
+     *
+     * The answer echoes the object it was asked about and says nothing else, so
+     * a `200` here is not evidence:
+     * {@link IAdtTransportObjectActions.readActionLog}, or a re-read of the
+     * object list, is what confirms the removal happened.
      */
-    removeObject<E extends IAdtError = IAdtError>(transportNumber: string, object: IAbapObjectEntry, options?: IAdtOperationOptions<E>): Promise<IAdtResponse<TRemoved, E>>;
+    removeObject<E extends IAdtError = IAdtError>(transportNumber: string, object: IAbapObjectEntry & {
+        position: string;
+    }, options?: IAdtOperationOptions<E>): Promise<IAdtResponse<TRemoved, E>>;
     /**
      * Attach one object to a request or task.
      *
@@ -179,15 +208,46 @@ export interface IAdtTransportObjectActions<TRemoved, TAdded, TTask, TActionLog>
      *
      * The new task is itself a request resource: it reads, writes and releases
      * like one, and {@link IAdtTransportObjectActions.removeObject} addresses it
-     * directly. With no `targetUser` the server decides whose task it is.
+     * directly.
+     *
+     * **`targetUser` is required, and that is measured.** This shipped saying
+     * the server would decide whose task it is when the attribute was absent.
+     * It does not: sent without `tm:targetuser` against an on-premise system,
+     * 2026-09-21, the owner resolved to an empty name and the call was refused
+     * with `400 SCTS_ADT_MSG 009`, *"User  does not exist in the system (or
+     * locked)"* — two spaces, because the name was empty. The same call carrying
+     * the attribute answered 200 and a task number.
+     *
+     * No implementation can fill it in either. `IAbapConnection` does not say
+     * who is authenticated, and finding out costs a second request — which is
+     * what a member of this size does not do. So it is the caller's to name.
      */
-    createTask<E extends IAdtError = IAdtError>(transportNumber: string, options?: {
-        targetUser?: string;
+    createTask<E extends IAdtError = IAdtError>(transportNumber: string, options: {
+        targetUser: string;
     } & IAdtOperationOptions<E>): Promise<IAdtResponse<TTask, E>>;
     /**
      * What has happened to this request: created, object added, object deleted,
      * owner changed — one entry per event.
      */
     readActionLog<E extends IAdtError = IAdtError>(transportNumber: string, options?: IAdtOperationOptions<E>): Promise<IAdtResponse<TActionLog, E>>;
+    /**
+     * The objects a request or task holds, each with the `tm:position` that
+     * {@link IAdtTransportObjectActions.removeObject} needs.
+     *
+     * **A separate reading, not the metadata one.** The transport resource has
+     * more than one representation, and which one arrives depends on the
+     * `Accept` the request carries. Measured against an on-premise system,
+     * 2026-09-21: a `GET` that names none at all comes back without a single
+     * `tm:abap_object` in it, so an implementation whose reader sends no
+     * `Accept` — the usual one — cannot answer this no matter how its result is
+     * parsed. `application/vnd.sap.adt.transportorganizer.v1+xml` is the media
+     * type that carries the list.
+     *
+     * This exists because `removeObject` requires a position and nothing else
+     * here hands one back: without it a caller has to go around the
+     * implementation and assemble the request themselves, which is the layering
+     * this package exists to prevent.
+     */
+    readObjects<E extends IAdtError = IAdtError>(transportNumber: string, options?: IAdtOperationOptions<E>): Promise<IAdtResponse<TObjects, E>>;
 }
 //# sourceMappingURL=IAdtTransport.d.ts.map

package/dist/adt/IAdtTransport.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"IAdtTransport.d.ts","sourceRoot":"","sources":["../../src/adt/IAdtTransport.ts"],"names":[],"mappings":"AAAA;;GAEG;AAEH,OAAO,KAAK,EAAE,oBAAoB,EAAE,MAAM,cAAc,CAAC;AACzD,OAAO,KAAK,EAAE,SAAS,EAAE,YAAY,EAAE,MAAM,gBAAgB,CAAC;AAE9D,MAAM,WAAW,sBAAsB;IACrC,cAAc,CAAC,EAAE,MAAM,CAAC;IACxB,WAAW,EAAE,MAAM,CAAC;IACpB,aAAa,CAAC,EAAE,MAAM,CAAC;IACvB,KAAK,CAAC,EAAE,MAAM,CAAC;CAChB;AAED;;;;;;;;;GASG;AACH,MAAM,WAAW,qBAAqB;IACpC,uFAAuF;IACvF,SAAS,EAAE,MAAM,CAAC;CACnB;AAED,sFAAsF;AACtF,MAAM,WAAW,sBAAsB;IACrC,SAAS,CAAC,EAAE,MAAM,CAAC;CACpB;AAED;;;;;;;GAOG;AACH,MAAM,WAAW,6BAA6B;IAC5C,4EAA4E;IAC5E,GAAG,EAAE,MAAM,CAAC;IACZ,6CAA6C;IAC7C,IAAI,CAAC,EAAE,MAAM,CAAC;IACd,kFAAkF;IAClF,UAAU,EAAE,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,CAAC;CACpC;AAED,mFAAmF;AACnF,eAAO,MAAM,mCAAmC,yEACwB,CAAC;AAGzE,MAAM,WAAW,gBAAgB;IAC/B;;;;;;;;;;;;;;;OAeG;IACH,QAAQ,CAAC,EAAE,MAAM,CAAC;IAElB,WAAW,EAAE,MAAM,CAAC;IACpB,aAAa,CAAC,EAAE,WAAW,GAAG,aAAa,CAAC;IAC5C,YAAY,CAAC,EAAE,MAAM,CAAC;IACtB,KAAK,CAAC,EAAE,MAAM,CAAC;IACf,eAAe,CAAC,EAAE,MAAM,CAAC;CAC1B;AAGD;;;;;;;;;;;;GAYG;AACH,MAAM,WAAW,WAAW,CAAC,KAAK;IAChC;;;;;;;;;;;;;;;;OAgBG;IACH,IAAI,CAAC,OAAO,CAAC,EAAE,sBAAsB,GAAG,OAAO,CAAC,YAAY,CAAC,KAAK,CAAC,CAAC,CAAC;CACtE;AAED;;;;;;;;;;;;;;;GAeG;AACH,MAAM,WAAW,gBAAgB;IAC/B,0DAA0D;IAC1D,IAAI,EAAE,MAAM,CAAC;IACb,0EAA0E;IAC1E,IAAI,EAAE,MAAM,CAAC;IACb;;;;;OAKG;IACH,KAAK,CAAC,EAAE,MAAM,CAAC;IACf,kEAAkE;IAClE,WAAW,CAAC,EAAE,MAAM,CAAC;IACrB,uEAAuE;IACvE,QAAQ,CAAC,EAAE,MAAM,CAAC;CACnB;AAED;;;;;;;;;;;;;;;;;;;GAmBG;AACH,MAAM,WAAW,0BAA0B,CACzC,QAAQ,EACR,MAAM,EACN,KAAK,EACL,UAAU;IAEV;;;;;;;OAOG;IACH,YAAY,CAAC,CAAC,SAAS,SAAS,GAAG,SAAS,EAC1C,eAAe,EAAE,MAAM,EACvB,MAAM,EAAE,gBAAgB,EACxB,OAAO,CAAC,EAAE,oBAAoB,CAAC,CAAC,CAAC,GAChC,OAAO,CAAC,YAAY,CAAC,QAAQ,EAAE,CAAC,CAAC,CAAC,CAAC;IACtC;;;;;;;OAOG;IACH,SAAS,CAAC,CAAC,SAAS,SAAS,GAAG,SAAS,EACvC,eAAe,EAAE,MAAM,EACvB,MAAM,EAAE,gBAAgB,EACxB,OAAO,CAAC,EAAE,oBAAoB,CAAC,CAAC,CAAC,GAChC,OAAO,CAAC,YAAY,CAAC,MAAM,EAAE,CAAC,CAAC,CAAC,CAAC;IACpC;;;;;;OAMG;IACH,UAAU,CAAC,CAAC,SAAS,SAAS,GAAG,SAAS,EACxC,eAAe,EAAE,MAAM,EACvB,OAAO,CAAC,EAAE;QAAE,UAAU,CAAC,EAAE,MAAM,CAAA;KAAE,GAAG,oBAAoB,CAAC,CAAC,CAAC,GAC1D,OAAO,CAAC,YAAY,CAAC,KAAK,EAAE,CAAC,CAAC,CAAC,CAAC;IACnC;;;OAGG;IACH,aAAa,CAAC,CAAC,SAAS,SAAS,GAAG,SAAS,EAC3C,eAAe,EAAE,MAAM,EACvB,OAAO,CAAC,EAAE,oBAAoB,CAAC,CAAC,CAAC,GAChC,OAAO,CAAC,YAAY,CAAC,UAAU,EAAE,CAAC,CAAC,CAAC,CAAC;CACzC"}
+{"version":3,"file":"IAdtTransport.d.ts","sourceRoot":"","sources":["../../src/adt/IAdtTransport.ts"],"names":[],"mappings":"AAAA;;GAEG;AAEH,OAAO,KAAK,EAAE,oBAAoB,EAAE,MAAM,cAAc,CAAC;AACzD,OAAO,KAAK,EAAE,SAAS,EAAE,YAAY,EAAE,MAAM,gBAAgB,CAAC;AAE9D,MAAM,WAAW,sBAAsB;IACrC,cAAc,CAAC,EAAE,MAAM,CAAC;IACxB,WAAW,EAAE,MAAM,CAAC;IACpB,aAAa,CAAC,EAAE,MAAM,CAAC;IACvB,KAAK,CAAC,EAAE,MAAM,CAAC;CAChB;AAED;;;;;;;;;GASG;AACH,MAAM,WAAW,qBAAqB;IACpC,uFAAuF;IACvF,SAAS,EAAE,MAAM,CAAC;CACnB;AAED,sFAAsF;AACtF,MAAM,WAAW,sBAAsB;IACrC,SAAS,CAAC,EAAE,MAAM,CAAC;CACpB;AAED;;;;;;;GAOG;AACH,MAAM,WAAW,6BAA6B;IAC5C,4EAA4E;IAC5E,GAAG,EAAE,MAAM,CAAC;IACZ,6CAA6C;IAC7C,IAAI,CAAC,EAAE,MAAM,CAAC;IACd,kFAAkF;IAClF,UAAU,EAAE,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,CAAC;CACpC;AAED,mFAAmF;AACnF,eAAO,MAAM,mCAAmC,yEACwB,CAAC;AAGzE,MAAM,WAAW,gBAAgB;IAC/B;;;;;;;;;;;;;;;OAeG;IACH,QAAQ,CAAC,EAAE,MAAM,CAAC;IAElB,WAAW,EAAE,MAAM,CAAC;IACpB,aAAa,CAAC,EAAE,WAAW,GAAG,aAAa,CAAC;IAC5C,YAAY,CAAC,EAAE,MAAM,CAAC;IACtB,KAAK,CAAC,EAAE,MAAM,CAAC;IACf,eAAe,CAAC,EAAE,MAAM,CAAC;CAC1B;AAGD;;;;;;;;;;;;GAYG;AACH,MAAM,WAAW,WAAW,CAAC,KAAK;IAChC;;;;;;;;;;;;;;;;OAgBG;IACH,IAAI,CAAC,OAAO,CAAC,EAAE,sBAAsB,GAAG,OAAO,CAAC,YAAY,CAAC,KAAK,CAAC,CAAC,CAAC;CACtE;AAED;;;;;;;;;;;;;;;GAeG;AACH,MAAM,WAAW,gBAAgB;IAC/B,0DAA0D;IAC1D,IAAI,EAAE,MAAM,CAAC;IACb,0EAA0E;IAC1E,IAAI,EAAE,MAAM,CAAC;IACb;;;;;OAKG;IACH,KAAK,CAAC,EAAE,MAAM,CAAC;IACf,kEAAkE;IAClE,WAAW,CAAC,EAAE,MAAM,CAAC;IACrB;;;;;;;;OAQG;IACH,QAAQ,CAAC,EAAE,MAAM,CAAC;CACnB;AAED;;;;;;;;;;;;;;;;;;;;;;GAsBG;AACH,MAAM,WAAW,0BAA0B,CACzC,QAAQ,EACR,MAAM,EACN,KAAK,EACL,UAAU,EACV,QAAQ;IAER;;;;;;;;;;;;;;;;;;;;;;;OAuBG;IACH,YAAY,CAAC,CAAC,SAAS,SAAS,GAAG,SAAS,EAC1C,eAAe,EAAE,MAAM,EACvB,MAAM,EAAE,gBAAgB,GAAG;QAAE,QAAQ,EAAE,MAAM,CAAA;KAAE,EAC/C,OAAO,CAAC,EAAE,oBAAoB,CAAC,CAAC,CAAC,GAChC,OAAO,CAAC,YAAY,CAAC,QAAQ,EAAE,CAAC,CAAC,CAAC,CAAC;IACtC;;;;;;;OAOG;IACH,SAAS,CAAC,CAAC,SAAS,SAAS,GAAG,SAAS,EACvC,eAAe,EAAE,MAAM,EACvB,MAAM,EAAE,gBAAgB,EACxB,OAAO,CAAC,EAAE,oBAAoB,CAAC,CAAC,CAAC,GAChC,OAAO,CAAC,YAAY,CAAC,MAAM,EAAE,CAAC,CAAC,CAAC,CAAC;IACpC;;;;;;;;;;;;;;;;;;OAkBG;IACH,UAAU,CAAC,CAAC,SAAS,SAAS,GAAG,SAAS,EACxC,eAAe,EAAE,MAAM,EACvB,OAAO,EAAE;QAAE,UAAU,EAAE,MAAM,CAAA;KAAE,GAAG,oBAAoB,CAAC,CAAC,CAAC,GACxD,OAAO,CAAC,YAAY,CAAC,KAAK,EAAE,CAAC,CAAC,CAAC,CAAC;IACnC;;;OAGG;IACH,aAAa,CAAC,CAAC,SAAS,SAAS,GAAG,SAAS,EAC3C,eAAe,EAAE,MAAM,EACvB,OAAO,CAAC,EAAE,oBAAoB,CAAC,CAAC,CAAC,GAChC,OAAO,CAAC,YAAY,CAAC,UAAU,EAAE,CAAC,CAAC,CAAC,CAAC;IACxC;;;;;;;;;;;;;;;;;OAiBG;IACH,WAAW,CAAC,CAAC,SAAS,SAAS,GAAG,SAAS,EACzC,eAAe,EAAE,MAAM,EACvB,OAAO,CAAC,EAAE,oBAAoB,CAAC,CAAC,CAAC,GAChC,OAAO,CAAC,YAAY,CAAC,QAAQ,EAAE,CAAC,CAAC,CAAC,CAAC;CACvC"}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mcp-abap-adt/interfaces-adt",
-  "version": "1.2.0",
+  "version": "2.0.0",
   "description": "ADT contracts, the ABAP and Cloud ALM connections, and SAP/BTP configuration and authentication contracts",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",