@lerianstudio/matcher-mcp 5.0.0-beta.19 → 5.0.0-beta.20

package/dist/spec/openapi.yaml

@@ -638,6 +638,12 @@ components:
             - 0
           format: int64
           type: integer
+        fromSeq:
+          description: "Effective verification floor: the first tenant_seq eligible for inspection (1 when fromSeq was omitted). Resume a truncated run at fromSeq + verifiedCount"
+          examples:
+            - 1
+          format: int64
+          type: integer
         intact:
           description: True when every inspected record links to the previous one and matches its stored hash
           examples:
@@ -656,6 +662,7 @@ components:
           type: integer
       required:
         - intact
+        - fromSeq
         - verifiedCount
         - truncated
       type: object
@@ -13048,7 +13055,10 @@ paths:
         - Governance
   /v1/governance/audit-logs/verify:
     get:
-      description: "Re-verifies the calling tenant's tamper-evident audit hash chain and returns a structured verdict (intact, verified count, and the first broken tenant_seq when a break is found). The check is strictly read-only: it recomputes nothing into storage and never mutates an audit record. Use the optional maxRecords query parameter to bound how many records are inspected."
+      description: |-
+        Re-verifies the calling tenant's tamper-evident audit hash chain and returns a structured verdict (intact, verified count, and the first broken tenant_seq when a break is found). The check is strictly read-only: it recomputes nothing into storage and never mutates an audit record. Use the optional maxRecords query parameter to bound how many records are inspected.
+
+        Use the optional fromSeq query parameter to bind the verification floor: the first record inspected is the one with tenant_seq == fromSeq. A floor above 1 TRUSTS that record's stored prev_hash instead of validating it against the genesis hash, so tampering BELOW the floor is out of scope for that run and is not reported. Two uses follow from that: (1) resuming — when a verdict comes back truncated, re-run with fromSeq = fromSeq + verifiedCount to verify the remainder; (2) archived-partition tenants — once the archival worker has dropped the bottom partitions, verify from the current floor, because a run from seq 1 no longer has the records it would need. The verdict always echoes the effective fromSeq, so an empty range (verifiedCount 0 with a high fromSeq) is never mistaken for an intact chain verified from genesis.
       operationId: verifyAuditLogChain
       parameters:
         - description: Maximum number of records to inspect; clamped to the server bound. Omit to use the default bound.
@@ -13061,6 +13071,15 @@ paths:
             maximum: 10000
             minimum: 1
             type: integer
+        - description: "Verification floor: the first record inspected is the one with this tenant_seq. Omit to start at the chain start (seq 1)."
+          explode: false
+          in: query
+          name: fromSeq
+          schema:
+            description: "Verification floor: the first record inspected is the one with this tenant_seq. Omit to start at the chain start (seq 1)."
+            format: int64
+            minimum: 1
+            type: integer
       responses:
         "200":
           content:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lerianstudio/matcher-mcp",
-  "version": "5.0.0-beta.19",
+  "version": "5.0.0-beta.20",
   "type": "module",
   "description": "Model Context Protocol server for the Matcher reconciliation engine",
   "license": "Apache-2.0",