@skrr-ai/cli 0.1.23 → 0.1.24

package/dist/lib/work-sync.d.ts

@@ -0,0 +1,70 @@
+/**
+ * Work Sync's own telemetry, readable.
+ *
+ * Work Sync v1 is ON at 100% (owner decision, 2026-09-08) with two of its exit
+ * criteria knowingly overridden rather than satisfied: `shadow_mismatch` and
+ * `resume_error` rows from a one-user sample were unexplained, and
+ * revocation-to-purge latency had never been measured. Root `CLAUDE.md` records
+ * that an unexplained board divergence is therefore "a live hypothesis, not an
+ * impossibility, and is the first thing to suspect".
+ *
+ * The server has computed the verdict all along — `GET
+ * /api/work-sync/spaces/:spaceId/telemetry-summary` returns the per-event counts,
+ * the repair backlog, and a `ready`/`hold`/`insufficient_evidence` decision with
+ * its reasons. Nothing outside the API could read it, so checking the criteria
+ * meant a query against the production database. An exit criterion that can only
+ * be read by hand is one that does not get read.
+ *
+ * A domain lib rather than an inline `/api/...` in the command, per the repo's
+ * CLI rule: a command reaches the API through its domain lib or `dataService`,
+ * never by composing the URL at the call site.
+ */
+export type WorkSyncEventStats = {
+    count: number;
+    p50DurationMs: number | null;
+    p95DurationMs: number | null;
+    p50Bytes: number | null;
+    p95Bytes: number | null;
+    mismatchCount: number;
+};
+export type WorkSyncTelemetrySummary = {
+    sampledEvents: number;
+    events: Record<string, WorkSyncEventStats>;
+    repairBacklog: number;
+    rollout: {
+        verdict: 'ready' | 'hold' | 'insufficient_evidence';
+        reasons: string[];
+    };
+};
+/** What each `rollout.reasons` code means, in the reader's terms. */
+export declare const WORK_SYNC_HOLD_REASONS: Record<string, string>;
+export declare function fetchWorkSyncTelemetrySummary(spaceId: string, { limit }?: {
+    limit?: number;
+}): Promise<WorkSyncTelemetrySummary>;
+/**
+ * What `POST /reconcile` actually returns, field for field.
+ *
+ * This was typed `{repaired?: number; remaining?: number}` — two names the server
+ * has never sent. A wrong optional type is worse than none: every field reads as
+ * `undefined` at runtime and TypeScript agrees it might be, so a command printing
+ * `repaired` would have compiled, run, and reported nothing wrong.
+ *
+ * `upserts` is the one that answers the question a reader is asking: how many
+ * projection entries were found STALE against authoritative task truth. It is a
+ * divergence count, which is why this command exists — it is the same question the
+ * browser's shadow comparison answers, asked server-side and without a browser.
+ */
+export type WorkSyncReconciliation = {
+    /** Projection entries found stale against task truth and republished. */
+    upserts: number;
+    /** TaskCards published for tasks that no longer exist. */
+    removes: number;
+    summaryUpserts: number;
+    summaryRemoves: number;
+    /** Pending repair rows queued by earlier failures, before this run settled them. */
+    backlog: number;
+    /** A scope larger than the 1000-row read cap: the verdict covers only a prefix. */
+    truncated: boolean;
+    success?: boolean;
+};
+export declare function reconcileWorkSyncScope(spaceId: string): Promise<WorkSyncReconciliation>;

package/dist/lib/work-sync.js

@@ -0,0 +1,29 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.WORK_SYNC_HOLD_REASONS = void 0;
+exports.fetchWorkSyncTelemetrySummary = fetchWorkSyncTelemetrySummary;
+exports.reconcileWorkSyncScope = reconcileWorkSyncScope;
+const api_fetch_1 = require("./api-fetch");
+/** What each `rollout.reasons` code means, in the reader's terms. */
+exports.WORK_SYNC_HOLD_REASONS = {
+    no_snapshot_evidence: 'No board ever loaded a snapshot in this Space — nothing has been measured.',
+    no_shadow_comparison: 'The shadow comparison has not run in this Space, so a divergence between the ' +
+        'projection and an authoritative read would not have been seen. It runs once per ' +
+        'mounted scope from the Work Sync board hook, re-reading the snapshot endpoint and ' +
+        'comparing it against the live projection — so zero usually means no board has been ' +
+        'opened in this Space since it shipped. It also re-arms rather than counting itself ' +
+        'done when the cursor moves mid-check, which on a very busy Space can defer it. Until ' +
+        "2026-09-12 it could not run at all on the projection's own path: it needed the legacy " +
+        'collection as a baseline, and `resolveTaskReadPlan` stops fetching that exactly when ' +
+        'the projection is canonical (OSK-8492).',
+    shadow_mismatch: 'The projection disagreed with an authoritative read. This is the board-divergence hypothesis; it is the first thing to suspect behind an unexplained board.',
+    resume_errors: 'A client could not resume from its cursor and had to reset.',
+    repair_backlog: 'Change records are waiting in the reconciliation backlog — publishes were missed.',
+};
+async function fetchWorkSyncTelemetrySummary(spaceId, { limit } = {}) {
+    const query = limit ? `?limit=${encodeURIComponent(String(limit))}` : '';
+    return (0, api_fetch_1.apiFetch)(`/api/work-sync/spaces/${encodeURIComponent(spaceId)}/telemetry-summary${query}`);
+}
+async function reconcileWorkSyncScope(spaceId) {
+    return (0, api_fetch_1.apiFetch)(`/api/work-sync/spaces/${encodeURIComponent(spaceId)}/reconcile`, { method: 'POST', body: {} });
+}