@lerianstudio/matcher-mcp 6.0.0-rc.2 → 6.0.0-rc.3

package/LICENSE

@@ -1,93 +1,24 @@
-Elastic License 2.0
-
-URL: https://www.elastic.co/licensing/elastic-license
-
-## Acceptance
-
-By using the software, you agree to all of the terms and conditions below.
-
-## Copyright License
-
-The licensor grants you a non-exclusive, royalty-free, worldwide,
-non-sublicensable, non-transferable license to use, copy, distribute, make
-available, and prepare derivative works of the software, in each case subject to
-the limitations and conditions below.
-
-## Limitations
-
-You may not provide the software to third parties as a hosted or managed
-service, where the service provides users with access to any substantial set of
-the features or functionality of the software.
-
-You may not move, change, disable, or circumvent the license key functionality
-in the software, and you may not remove or obscure any functionality in the
-software that is protected by the license key.
-
-You may not alter, remove, or obscure any licensing, copyright, or other notices
-of the licensor in the software. Any use of the licensor's trademarks is subject
-to applicable law.
-
-## Patents
-
-The licensor grants you a license, under any patent claims the licensor can
-license, or becomes able to license, to make, have made, use, sell, offer for
-sale, import and have imported the software, in each case subject to the
-limitations and conditions in this license. This license does not cover any
-patent claims that you cause to be infringed by modifications or additions to
-the software. If you or your company make any written claim that the software
-infringes or contributes to infringement of any patent, your patent license for
-the software granted under these terms ends immediately. If your company makes
-such a claim, your patent license ends immediately for work on behalf of your
-company.
-
-## Notices
-
-You must ensure that anyone who gets a copy of any part of the software from you
-also gets a copy of these terms.
-
-If you modify the software, you must include in any modified copies of the
-software prominent notices stating that you have modified the software.
-
-## No Other Rights
-
-These terms do not imply any licenses other than those expressly granted in
-these terms.
-
-## Termination
-
-If you use the software in violation of these terms, such use is not licensed,
-and your licenses will automatically terminate. If the licensor provides you
-with a notice of your violation, and you cease all violation of this license no
-later than 30 days after you receive that notice, your licenses will be
-reinstated retroactively. However, if you violate these terms after such
-reinstatement, any additional violation of these terms will cause your licenses
-to terminate automatically and permanently.
-
-## No Liability
-
-*As far as the law allows, the software comes as is, without any warranty or
-condition, and the licensor will not be liable to you for any damages arising
-out of these terms or the use or nature of the software, under any kind of
-legal claim.*
-
-## Definitions
-
-The **licensor** is the entity offering these terms, and the **software** is the
-software the licensor makes available under these terms, including any portion
-of it.
-
-**you** refers to the individual or entity agreeing to these terms.
-
-**your company** is any legal entity, sole proprietorship, or other kind of
-organization that you work for, plus all organizations that have control over,
-are under the control of, or are under common control with that
-organization. **control** means ownership of substantially all the assets of an
-entity, or the power to direct its management and policies by vote, contract, or
-otherwise. Control can be direct or indirect.
-
-**your licenses** are all the licenses granted to you for the software under
-these terms.
-
-**use** means anything you do with the software requiring one of your licenses.
-
-**trademark** means trademarks, service marks, and similar rights.
+Lerian Studio General License
+
+Copyright (c) 2026 Lerian Studio Ltd. All rights reserved.
+
+NOTICE: All information contained herein is, and remains the property of
+Lerian Studio Ltd. and its suppliers, if any. The intellectual and technical
+concepts contained herein are proprietary to Lerian Studio Ltd. and its
+suppliers and are protected by trade secret or copyright law.
+
+Dissemination of this information or reproduction of this material is strictly
+forbidden unless prior written permission is obtained from Lerian Studio Ltd.
+
+This software is provided by the copyright holders and contributors "as is"
+and any express or implied warranties, including, but not limited to, the
+implied warranties of merchantability and fitness for a particular purpose are
+disclaimed. In no event shall the copyright holder or contributors be liable
+for any direct, indirect, incidental, special, exemplary, or consequential
+damages (including, but not limited to, procurement of substitute goods or
+services; loss of use, data, or profits; or business interruption) however
+caused and on any theory of liability, whether in contract, strict liability,
+or tort (including negligence or otherwise) arising in any way out of the use
+of this software, even if advised of the possibility of such damage.
+
+For licensing inquiries, contact: legal@lerian.studio

package/README.md

@@ -80,7 +80,7 @@ Three options for `<mcp-url>`:
   the host relay with `MATCHER_API_URL=http://localhost:4018`; the Compose relay
   targets the Docker-only name `app:4018`. See [`../docs/development.md`](../docs/development.md).
 - **Run it standalone with `npx`.** `@lerianstudio/matcher-mcp` is a **public**
-  package (ELv2) — no registry auth needed. Start the relay (binds `:4019`)
+  package — no registry auth needed. Start the relay (binds `:4019`)
   pointed at your Matcher API:
 
   ```bash

package/dist/spec/openapi.yaml

@@ -2984,12 +2984,13 @@ components:
             - BUSINESS_DECISION
           type: string
         resolutionType:
-          description: "How the exception was resolved: FORCE_MATCH (override match), ADJUST_ENTRY (monetary correction), MANUAL_MATCH (the manual match that paired it), AUTO_CONSUME (closed automatically when a run settled its transaction against a carried open item) or UNMATCH_WITHDRAWN (withdrawn by an un-match: the match that raised it, or the manual match that resolved it, was undone)"
+          description: "How the exception was resolved: FORCE_MATCH (override match), ADJUST_ENTRY (monetary correction), MANUAL_MATCH (the manual match that paired it), AUTO_CONSUME (closed automatically when a run settled its transaction against a carried open item), AUTO_MATCH (closed automatically when a run matched its transaction, for a break whose reason only said its counterpart was missing or unusable: UNMATCHED, FX_RATE_UNAVAILABLE, MISSING_BASE_AMOUNT, MISSING_BASE_CURRENCY or SPLIT_INCOMPLETE) or UNMATCH_WITHDRAWN (withdrawn by an un-match: the match that raised it, or the match that resolved it, was undone)"
           enum:
             - FORCE_MATCH
             - ADJUST_ENTRY
             - MANUAL_MATCH
             - AUTO_CONSUME
+            - AUTO_MATCH
             - UNMATCH_WITHDRAWN
           examples:
             - FORCE_MATCH
@@ -8932,6 +8933,10 @@ info:
     Two bounds close the contract. A response larger than about 1 MB is delivered to its caller in full, but it is not stored for replay: a duplicate under the same key is answered 409 `MTCH-0022` instead of replayed. And an over-sized body is refused with 413 and spends nothing. On every route but one the service-wide request body limit refuses it before the key is read. The streaming upload (`POST /v1/imports/contexts/{contextId}/sources/{sourceId}/upload`) is exempt from that limit: the key is read first and ingestion enforces its own upload limit inside the handler, so its 413 is a third answer that releases the key, and a smaller file may be re-sent under it.
 
     Secret mints are another, sharper exception. `POST /v1/discovery/aggregator-connections/{id}/connect-token`, `POST /v1/discovery/webhooks/tokens`, `POST /v1/exceptions/callbacks/credentials` and `POST /v1/exceptions/callbacks/credentials/{credentialId}/rotate` each return a raw credential exactly ONCE, and storing that answer would keep the secret re-readable for the life of the key — so those four routes IGNORE the idempotency header entirely. Nothing is stored, nothing is replayed, and `X-Idempotency-Replayed` is never sent on them. A retry under the same key MINTS AGAIN and leaves a second live credential behind, so treat a mint as non-idempotent: read the first attempt's response rather than resending it. A surplus callback credential or aggregator webhook token shows in its list operation (metadata only, never the secret) and is revoked through its own operation.
+
+    ## Refusals
+
+    An authorization refusal is answered with an `application/problem+json` document carrying a code, title and sentence. On every `/v1` route Matcher first checks a token that parses: on a multi-tenant deployment a token with no tenant claim is refused 403 `MTCH-0004`, and a malformed tenant claim or a missing `sub` is refused 401 `MTCH-0003`. The authorization layer then answers with its own codes: 401 `AUT-0006` (no bearer token) or `AUT-0007` (token expired, invalid or malformed); 401 `AUT-1009` or `AUT-1010` (the credential's partner is suspended or outside its validity period); 403 `AUT-1020` (the credential may not perform the `resource:action` the detail names); 403 `AUT-1016`, `AUT-1017`, `AUT-1018` or `AUT-1019` (the partner the request was made on behalf of belongs to another tenant, is suspended, is no longer valid, or may not perform it); 503 `AUT-0033` (the Access Manager did not decide the request) and 504 `AUT-1021` (it did not answer in time). Nothing ran on either 5xx: retry the same request, under the same idempotency key. A code the Access Manager answered itself, such as 403 `AUT-0021` (caller address not on the tenant allowlist), is relayed as code, title and detail at its status.
   license:
     name: Lerian Studio General License
   title: Matcher Reconciliation API

package/package.json

@@ -1,9 +1,9 @@
 {
   "name": "@lerianstudio/matcher-mcp",
-  "version": "6.0.0-rc.2",
+  "version": "6.0.0-rc.3",
   "type": "module",
   "description": "Model Context Protocol server for the Matcher reconciliation engine",
-  "license": "Elastic-2.0",
+  "license": "LicenseRef-Lerian-Proprietary",
   "author": "Lerian Studio",
   "keywords": [
     "model-context-protocol",