@chainpatrol/mcp 1.10.0 → 1.10.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -1,5 +1,32 @@
1
1
  # @chainpatrol/mcp
2
2
 
3
+ ## 1.10.1
4
+
5
+ ### Patch Changes
6
+
7
+ - a6ffc93: The `attachmentUrls` argument on `report_create` is no longer described as images only.
8
+ It has always accepted a URL to any file, but the description read "URLs of images to
9
+ attach to the report", which led API clients to believe evidence files such as `.eml`
10
+ messages were out of scope and had to be left out or hosted elsewhere.
11
+
12
+ It now says that any file type is accepted and points at `POST /attachment/upload` for
13
+ callers who want to send us the bytes rather than host the file themselves. No behaviour
14
+ changes — the schema still accepts the same array of URLs. The wording comes from
15
+ @chainpatrol/validation, a private package, and reaches the manifest and the published
16
+ OpenAPI spec through the external API router.
17
+
18
+ - 4481e9c: Filtering reports by `reviewStatuses: ["ESCALATE"]` now matches proposals escalated to
19
+ the customer. The filter previously read `Proposal.isEscalated`, which is only written
20
+ for team escalations, so customer escalations were invisible to it. It now also matches
21
+ a live `ESCALATE` review, the way `SKIP` already reads review history.
22
+
23
+ Expect larger result sets and higher report counts for organizations that use customer
24
+ escalations. The same fix applies to the report list, the per-status counts, and the CSV
25
+ export, backed by changes in the private packages @chainpatrol/core, @chainpatrol/trpc,
26
+ and @chainpatrol/external-trpc. The generated MCP tool manifest picks up a new
27
+ description for the `reviewStatuses` argument spelling out which options read current
28
+ status and which read review history.
29
+
3
30
  ## 1.10.0
4
31
 
5
32
  ### Minor Changes
@@ -3016,7 +3016,8 @@ var tools_default = {
3016
3016
  "SKIP",
3017
3017
  "ESCALATE"
3018
3018
  ]
3019
- }
3019
+ },
3020
+ description: "Filter to reports with at least one proposal matching any of these review outcomes. `APPROVE` and `REJECT` match the proposal's current review status. `SKIP` and `ESCALATE` match the review history, so a proposal that was escalated still matches after the escalation is answered."
3020
3021
  },
3021
3022
  assetTypes: {
3022
3023
  type: "array",
@@ -3111,7 +3112,7 @@ var tools_default = {
3111
3112
  type: "string",
3112
3113
  format: "uri"
3113
3114
  },
3114
- description: "URLs of images to attach to the report"
3115
+ description: "URLs of files to attach to the report as evidence. Any file type, not only images: .eml/.msg messages, PDFs, and documents are all supported. Upload a file to POST /attachment/upload to get a URL, or pass a publicly reachable URL you host yourself."
3115
3116
  },
3116
3117
  externalSubmissionLink: {
3117
3118
  type: "string",
@@ -4465,4 +4466,4 @@ export {
4465
4466
  toolsFromEnvironment,
4466
4467
  PACKAGE_VERSION
4467
4468
  };
4468
- //# sourceMappingURL=chunk-AHMNJBKL.js.map
4469
+ //# sourceMappingURL=chunk-DXVC4YVX.js.map