@thinkai/tai-api-contract 2.84.0 → 2.85.0

package/openapi/openapi.yaml

@@ -1,7 +1,7 @@
 openapi: 3.0.3
 info:
   title: ThinkAI API
-  version: 2.84.0
+  version: 2.85.0
   description: >
     Contract surface for the AI Driven SDLC backend used by ThinkAI.
     Workspace-scoped routes use `/workspaces/{workspaceId}/...`.
@@ -5484,10 +5484,11 @@ paths:
         (issues plus optional remediation from `criteriaDetails`).
 
         The Markdown is grouped **by readiness dimension** (catalog order). Each dimension section
-        lists matching issues sorted by severity. Default filter is outstanding issues
-        (`open` + `pr-pending`). Optional query params narrow the set. When `includeCriteria` is
-        true (default), each issue includes a Remediation section from the matching criterion when
-        available.
+        lists matching issues sorted by severity. Issue sections include severity in the heading
+        and do not emit per-issue `Fix status` / `Fix tier` lines. Default filter is outstanding
+        issues (`open` + `pr-pending`). Optional query params narrow the set. When `includeCriteria`
+        is true (default), each issue includes a Remediation section from the matching criterion when
+        available. Timestamps use the optional `timeZone` query (IANA; default `UTC`).
 
         The response sets `Content-Disposition: attachment` with filename
         `readiness-issues-{providerSlug}-{date}.md`.
@@ -5522,6 +5523,16 @@ paths:
           schema:
             type: boolean
             default: true
+        - name: timeZone
+          in: query
+          required: false
+          description: >
+            IANA time zone for human-readable `Last analyzed` / `Exported` timestamps and the
+            calendar date in the attachment filename (e.g. `Europe/Berlin`). Defaults to `UTC`.
+          schema:
+            type: string
+            maxLength: 64
+            example: Europe/Berlin
       responses:
         "200":
           description: Markdown file of readiness issues

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@thinkai/tai-api-contract",
-  "version": "2.84.0",
+  "version": "2.85.0",
   "private": false,
   "type": "module",
   "main": "dist/index.js",

package/src/generated/openapi.ts

@@ -2133,7 +2133,7 @@ export interface paths {
         /**
          * Export repository readiness issues as Markdown
          * @description Download outstanding readiness issues for one repository as a Markdown (`.md`) attachment for local IDE workflows. Reuses the same scorecard as `GET .../readiness/repos/{repoId}` (issues plus optional remediation from `criteriaDetails`).
-         *     The Markdown is grouped **by readiness dimension** (catalog order). Each dimension section lists matching issues sorted by severity. Default filter is outstanding issues (`open` + `pr-pending`). Optional query params narrow the set. When `includeCriteria` is true (default), each issue includes a Remediation section from the matching criterion when available.
+         *     The Markdown is grouped **by readiness dimension** (catalog order). Each dimension section lists matching issues sorted by severity. Issue sections include severity in the heading and do not emit per-issue `Fix status` / `Fix tier` lines. Default filter is outstanding issues (`open` + `pr-pending`). Optional query params narrow the set. When `includeCriteria` is true (default), each issue includes a Remediation section from the matching criterion when available. Timestamps use the optional `timeZone` query (IANA; default `UTC`).
          *     The response sets `Content-Disposition: attachment` with filename `readiness-issues-{providerSlug}-{date}.md`.
          */
         get: operations["exportReadinessRepoIssuesMarkdown"];
@@ -13925,6 +13925,8 @@ export interface operations {
                 severity?: "critical" | "high" | "medium" | "low";
                 /** @description Include remediation from criteriaDetails (default true). */
                 includeCriteria?: boolean;
+                /** @description IANA time zone for human-readable `Last analyzed` / `Exported` timestamps and the calendar date in the attachment filename (e.g. `Europe/Berlin`). Defaults to `UTC`. */
+                timeZone?: string;
             };
             header?: never;
             path: {