@open-mercato/cezar 0.9.2-pr710.1256 → 0.9.2-pr710.1265

package/dist/contract/github.d.ts

@@ -101,6 +101,94 @@ export declare const githubChecksDataSchema: z.ZodDiscriminatedUnion<[z.ZodObjec
     reason: z.ZodString;
 }, z.core.$strip>], "available">;
 export type GithubChecksData = z.infer<typeof githubChecksDataSchema>;
+/**
+ * Where a referenced PR or issue STANDS — the vocabulary a task's tracker chip paints.
+ *
+ * One flat enum rather than a per-kind union, because the chip renders one status and a union
+ * would make every consumer narrow on `kind` before it could pick a color. The kinds share no
+ * value on purpose: a closed PR (abandoned — red) and a closed issue (`completed` — done, violet)
+ * are opposite outcomes wearing the same English word, and collapsing them is how a merged-looking
+ * task turns out to have been dropped.
+ *
+ * PR values: `merged`, `closed` (closed WITHOUT merging), `draft`, `checks-pending`,
+ * `changes-requested`, `checks-failing`, `review-required`, `ready`. Issue values: `open`,
+ * `completed`, `not-planned`.
+ *
+ * Which one a PR gets is `derivePrReferenceStatus`'s ranking (server-side, and documented there):
+ * it answers "what is this waiting on right now", so it ranks by how FRESH a signal is rather
+ * than by how heavy a blocker it is — running checks mean a commit was just pushed, and a
+ * requested change the author has already pushed past is not what the PR is waiting on.
+ *
+ * `ready` is the honest reading of "nothing is blocking it here": open, not a draft, no failing or
+ * running checks, and no review the forge is still waiting on. It is NOT a mergeability probe —
+ * that is `githubPrMergeStateResponseSchema`, which costs a request per PR; this is one batched
+ * query for a whole table.
+ */
+export declare const referenceStatusSchema: z.ZodEnum<{
+    "changes-requested": "changes-requested";
+    "checks-failing": "checks-failing";
+    "checks-pending": "checks-pending";
+    closed: "closed";
+    completed: "completed";
+    draft: "draft";
+    merged: "merged";
+    "not-planned": "not-planned";
+    open: "open";
+    ready: "ready";
+    "review-required": "review-required";
+}>;
+export type ReferenceStatus = z.infer<typeof referenceStatusSchema>;
+/**
+ * `GET /api/v1/github/ref-status?prs=…&issues=…` — batched status for the PR/issue chips a task
+ * table is painting. The additive sibling of `/github/checks`: same cache-behind-the-route shape,
+ * same in-payload degrade, same "absent number = nothing known" rule (an unknown or unreachable
+ * number is simply missing from the map, and its chip stays neutral).
+ */
+/**
+ * How many numbers of ONE kind a single `/github/ref-status` request may name — the route 400s
+ * past it, and the cockpit caps its batches to match.
+ *
+ * It lives in the contract because it is one: a client that believed a larger number would send
+ * requests the server rejects outright, costing every chip in the batch its status rather than
+ * just the tail. Two constants that must agree, in two packages, with nothing making them, is the
+ * drift this export exists to prevent.
+ */
+export declare const REFERENCE_STATUS_MAX = 100;
+export declare const githubRefStatusDataSchema: z.ZodDiscriminatedUnion<[z.ZodObject<{
+    available: z.ZodLiteral<true>;
+    prs: z.ZodRecord<z.ZodNumber, z.ZodEnum<{
+        "changes-requested": "changes-requested";
+        "checks-failing": "checks-failing";
+        "checks-pending": "checks-pending";
+        closed: "closed";
+        completed: "completed";
+        draft: "draft";
+        merged: "merged";
+        "not-planned": "not-planned";
+        open: "open";
+        ready: "ready";
+        "review-required": "review-required";
+    }>>;
+    issues: z.ZodRecord<z.ZodNumber, z.ZodEnum<{
+        "changes-requested": "changes-requested";
+        "checks-failing": "checks-failing";
+        "checks-pending": "checks-pending";
+        closed: "closed";
+        completed: "completed";
+        draft: "draft";
+        merged: "merged";
+        "not-planned": "not-planned";
+        open: "open";
+        ready: "ready";
+        "review-required": "review-required";
+    }>>;
+    recheckAfterMs: z.ZodNullable<z.ZodNumber>;
+}, z.core.$strip>, z.ZodObject<{
+    available: z.ZodLiteral<false>;
+    reason: z.ZodString;
+    recheckAfterMs: z.ZodNullable<z.ZodNumber>;
+}, z.core.$strip>], "available">;
+export type GithubRefStatusData = z.infer<typeof githubRefStatusDataSchema>;
 /** One comment or PR review summary in an issue/PR thread (#499). */
 export declare const githubCommentSchema: z.ZodObject<{
     id: z.ZodNumber;