deepline 0.3.106 → 0.3.107

package/dist/bundling-sources/sdk/src/release.ts

@@ -200,7 +200,7 @@ export const SDK_RELEASE = {
   // getters keep their established compatibility behavior.
   // 0.3.1 deprecated the legacy `deepline enrich` command in favor of Plays.
   // 0.3.90 is the first deliberately versioned SDK release for API v3.
-  version: '0.3.106',
+  version: '0.3.107',
   updateSummary:
     'Play grep now returns concise results with the matched fields and terms. Automatic CLI updates are enabled by default; use `deepline settings autoupdate off` to opt out, `deepline settings autoupdate on` to re-enable updates, or `deepline settings autoupdate pin <version>` to hold an exact release.',
   packageCapabilities: {

package/dist/bundling-sources/shared_libs/observability/scheduled-jobs.json

@@ -525,24 +525,6 @@
     "failureAlert": "vercel_route_wrapper",
     "domainReportRequired": true
   },
-  {
-    "id": "vercel.provider-monitor-direct-billing-suspension",
-    "name": "Provider monitor direct billing suspension",
-    "scheduler": "vercel_cron",
-    "cadence": "*/5 * * * *",
-    "timezone": "UTC",
-    "source": "apps/deepline-api/vercel.json",
-    "locator": "/api/v2/cron/provider-monitor-direct-billing-suspension",
-    "owner": "monitors",
-    "criticality": "critical",
-    "purpose": "Apply direct billing-suspension decisions to provider monitors after billing state changes.",
-    "successDefinition": "Every due target is evaluated and desired state is persisted; no targets is a valid no-op.",
-    "failureDefinition": "A target cannot be evaluated or desired suspension state fails to persist.",
-    "startGraceMs": 300000,
-    "runTimeoutMs": 1800000,
-    "failureAlert": "vercel_route_wrapper",
-    "domainReportRequired": true
-  },
   {
     "id": "vercel.provider-monitor-batch-operation-sweep",
     "name": "Provider monitor batch operation recovery sweep",

package/dist/cli/index.js

@@ -1298,7 +1298,7 @@ var SDK_RELEASE = {
   // getters keep their established compatibility behavior.
   // 0.3.1 deprecated the legacy `deepline enrich` command in favor of Plays.
   // 0.3.90 is the first deliberately versioned SDK release for API v3.
-  version: "0.3.106",
+  version: "0.3.107",
   updateSummary: "Play grep now returns concise results with the matched fields and terms. Automatic CLI updates are enabled by default; use `deepline settings autoupdate off` to opt out, `deepline settings autoupdate on` to re-enable updates, or `deepline settings autoupdate pin <version>` to hold an exact release.",
   packageCapabilities: {
     updatePreferences: 1
@@ -33788,9 +33788,15 @@ function renderMonitorDeletePlan(payload, fallbackKey) {
 function renderMonitorReactivatePlan(payload, key) {
   const estimate = asRecord2(payload.cost_estimate);
   const credits = estimate ? asFiniteNumber(estimate.credits) : void 0;
+  const monitor = asRecord2(payload.monitor);
+  const tool = monitor ? asString(monitor.tool) : void 0;
+  const hasTamradarHistoricalCatchup = tool === "deepline_native.company_radar" || tool === "deepline_native.contact_radar" || tool === "deepline_native.industry_radar";
   const lines = [
     "DRY RUN \u2014 nothing was reactivated.",
     credits !== void 0 ? `Reactivate cost: would cost ${credits} Deepline credits.` : "Reactivate cost: estimate unavailable from this server.",
+    ...hasTamradarHistoricalCatchup ? [
+      "Source boundary: ordinary reactivation starts at provider creation. Saved updates_since values are not forwarded during reactivation."
+    ] : [],
     "",
     `Reactivate for real: deepline monitors reactivate ${key}`
   ];
@@ -35919,10 +35925,13 @@ Notes:
   no separate repair command or retry queue: rerun the same deploy/update.
   Scheduled reconciliation can also finish that exact saved cleanup; it never
   creates another monitor.
-  For TamRadar, deliberately changing payload.updates_since is an explicit
-  historical replay request, including when redeploying a disabled monitor.
-  Deepline preserves that selected boundary; filter-only deploys and ordinary
-  reactivation start from a fresh future-only source boundary instead.
+  For TamRadar, deliberately changing payload.updates_since on an initial or
+  active definition is an explicit historical replay request. A disabled
+  monitor cannot stage this change; Deepline rejects that update. Filter-only
+  deploys and ordinary reactivation omit the field and start the provider
+  resource at creation instead.
+  New Hire and Promotion source dates use calendar-month precision upstream,
+  so Deepline rejects current-month updates_since values for those radar types.
   Operational controls are Deepline-managed. A monitor writes rows; downstream
   automation belongs in a Play with sqlListeners.
 
@@ -35950,11 +35959,13 @@ positionally, via --file <path>, or from stdin with --file -.
 When <patch> includes payload, its top-level fields are merged with the stored
 payload before validation. This lets you change one filter without resending
 domain or radar_type; nested values and arrays replace atomically.
-For TamRadar, changing payload.updates_since is an explicit historical replay
-request. Deepline passes that requested boundary upstream, but previously
+For TamRadar, changing payload.updates_since on an initial or active definition
+is an explicit historical replay request. Deepline passes that requested boundary upstream, but previously
 delivered canonical findings are deduplicated before dispatch and billing; only
 previously unseen historical findings are chargeable. Filter-only updates,
-repair, and reactivation instead use a fresh future-only source boundary.
+repair, and reactivation instead omit the field and start the provider resource
+at creation. New Hire and Promotion source dates use calendar-month precision,
+so current-month updates_since values are rejected for those radar types.
 
 Examples:
   deepline monitors update my-monitor '{"name":"Interested replies"}' --json
@@ -35995,6 +36006,11 @@ Notes:
   Mutates workspace state and may spend Deepline credits.
   --dry-run shows the reactivation cost (in Deepline credits) without changing
   anything.
+  Deepline Native radars create a replacement upstream radar from the saved
+  filters. Reactivation always omits updates_since and starts at provider
+  creation; a disabled monitor cannot stage an updates_since change. New Hire
+  and Promotion source dates use calendar-month precision upstream, so
+  current-month updates_since values are rejected for those radar types.
 
 Examples:
   deepline monitors reactivate my-monitor --dry-run

package/dist/cli/index.mjs

@@ -1271,7 +1271,7 @@ var SDK_RELEASE = {
   // getters keep their established compatibility behavior.
   // 0.3.1 deprecated the legacy `deepline enrich` command in favor of Plays.
   // 0.3.90 is the first deliberately versioned SDK release for API v3.
-  version: "0.3.106",
+  version: "0.3.107",
   updateSummary: "Play grep now returns concise results with the matched fields and terms. Automatic CLI updates are enabled by default; use `deepline settings autoupdate off` to opt out, `deepline settings autoupdate on` to re-enable updates, or `deepline settings autoupdate pin <version>` to hold an exact release.",
   packageCapabilities: {
     updatePreferences: 1
@@ -33845,9 +33845,15 @@ function renderMonitorDeletePlan(payload, fallbackKey) {
 function renderMonitorReactivatePlan(payload, key) {
   const estimate = asRecord2(payload.cost_estimate);
   const credits = estimate ? asFiniteNumber(estimate.credits) : void 0;
+  const monitor = asRecord2(payload.monitor);
+  const tool = monitor ? asString(monitor.tool) : void 0;
+  const hasTamradarHistoricalCatchup = tool === "deepline_native.company_radar" || tool === "deepline_native.contact_radar" || tool === "deepline_native.industry_radar";
   const lines = [
     "DRY RUN \u2014 nothing was reactivated.",
     credits !== void 0 ? `Reactivate cost: would cost ${credits} Deepline credits.` : "Reactivate cost: estimate unavailable from this server.",
+    ...hasTamradarHistoricalCatchup ? [
+      "Source boundary: ordinary reactivation starts at provider creation. Saved updates_since values are not forwarded during reactivation."
+    ] : [],
     "",
     `Reactivate for real: deepline monitors reactivate ${key}`
   ];
@@ -35976,10 +35982,13 @@ Notes:
   no separate repair command or retry queue: rerun the same deploy/update.
   Scheduled reconciliation can also finish that exact saved cleanup; it never
   creates another monitor.
-  For TamRadar, deliberately changing payload.updates_since is an explicit
-  historical replay request, including when redeploying a disabled monitor.
-  Deepline preserves that selected boundary; filter-only deploys and ordinary
-  reactivation start from a fresh future-only source boundary instead.
+  For TamRadar, deliberately changing payload.updates_since on an initial or
+  active definition is an explicit historical replay request. A disabled
+  monitor cannot stage this change; Deepline rejects that update. Filter-only
+  deploys and ordinary reactivation omit the field and start the provider
+  resource at creation instead.
+  New Hire and Promotion source dates use calendar-month precision upstream,
+  so Deepline rejects current-month updates_since values for those radar types.
   Operational controls are Deepline-managed. A monitor writes rows; downstream
   automation belongs in a Play with sqlListeners.
 
@@ -36007,11 +36016,13 @@ positionally, via --file <path>, or from stdin with --file -.
 When <patch> includes payload, its top-level fields are merged with the stored
 payload before validation. This lets you change one filter without resending
 domain or radar_type; nested values and arrays replace atomically.
-For TamRadar, changing payload.updates_since is an explicit historical replay
-request. Deepline passes that requested boundary upstream, but previously
+For TamRadar, changing payload.updates_since on an initial or active definition
+is an explicit historical replay request. Deepline passes that requested boundary upstream, but previously
 delivered canonical findings are deduplicated before dispatch and billing; only
 previously unseen historical findings are chargeable. Filter-only updates,
-repair, and reactivation instead use a fresh future-only source boundary.
+repair, and reactivation instead omit the field and start the provider resource
+at creation. New Hire and Promotion source dates use calendar-month precision,
+so current-month updates_since values are rejected for those radar types.
 
 Examples:
   deepline monitors update my-monitor '{"name":"Interested replies"}' --json
@@ -36052,6 +36063,11 @@ Notes:
   Mutates workspace state and may spend Deepline credits.
   --dry-run shows the reactivation cost (in Deepline credits) without changing
   anything.
+  Deepline Native radars create a replacement upstream radar from the saved
+  filters. Reactivation always omits updates_since and starts at provider
+  creation; a disabled monitor cannot stage an updates_since change. New Hire
+  and Promotion source dates use calendar-month precision upstream, so
+  current-month updates_since values are rejected for those radar types.
 
 Examples:
   deepline monitors reactivate my-monitor --dry-run

package/dist/index.js

@@ -860,7 +860,7 @@ var SDK_RELEASE = {
   // getters keep their established compatibility behavior.
   // 0.3.1 deprecated the legacy `deepline enrich` command in favor of Plays.
   // 0.3.90 is the first deliberately versioned SDK release for API v3.
-  version: "0.3.106",
+  version: "0.3.107",
   updateSummary: "Play grep now returns concise results with the matched fields and terms. Automatic CLI updates are enabled by default; use `deepline settings autoupdate off` to opt out, `deepline settings autoupdate on` to re-enable updates, or `deepline settings autoupdate pin <version>` to hold an exact release.",
   packageCapabilities: {
     updatePreferences: 1

package/dist/index.mjs

@@ -768,7 +768,7 @@ var SDK_RELEASE = {
   // getters keep their established compatibility behavior.
   // 0.3.1 deprecated the legacy `deepline enrich` command in favor of Plays.
   // 0.3.90 is the first deliberately versioned SDK release for API v3.
-  version: "0.3.106",
+  version: "0.3.107",
   updateSummary: "Play grep now returns concise results with the matched fields and terms. Automatic CLI updates are enabled by default; use `deepline settings autoupdate off` to opt out, `deepline settings autoupdate on` to re-enable updates, or `deepline settings autoupdate pin <version>` to hold an exact release.",
   packageCapabilities: {
     updatePreferences: 1

package/dist/release.d.mts

@@ -149,7 +149,7 @@ type SdkRelease = {
     supportPolicy: SdkSupportPolicy;
 };
 declare const SDK_RELEASE: {
-    readonly version: "0.3.106";
+    readonly version: "0.3.107";
     readonly updateSummary: "Play grep now returns concise results with the matched fields and terms. Automatic CLI updates are enabled by default; use `deepline settings autoupdate off` to opt out, `deepline settings autoupdate on` to re-enable updates, or `deepline settings autoupdate pin <version>` to hold an exact release.";
     readonly packageCapabilities: {
         readonly updatePreferences: 1;

package/dist/release.d.ts

@@ -149,7 +149,7 @@ type SdkRelease = {
     supportPolicy: SdkSupportPolicy;
 };
 declare const SDK_RELEASE: {
-    readonly version: "0.3.106";
+    readonly version: "0.3.107";
     readonly updateSummary: "Play grep now returns concise results with the matched fields and terms. Automatic CLI updates are enabled by default; use `deepline settings autoupdate off` to opt out, `deepline settings autoupdate on` to re-enable updates, or `deepline settings autoupdate pin <version>` to hold an exact release.";
     readonly packageCapabilities: {
         readonly updatePreferences: 1;

package/dist/release.js

@@ -74,7 +74,7 @@ var SDK_RELEASE = {
   // getters keep their established compatibility behavior.
   // 0.3.1 deprecated the legacy `deepline enrich` command in favor of Plays.
   // 0.3.90 is the first deliberately versioned SDK release for API v3.
-  version: "0.3.106",
+  version: "0.3.107",
   updateSummary: "Play grep now returns concise results with the matched fields and terms. Automatic CLI updates are enabled by default; use `deepline settings autoupdate off` to opt out, `deepline settings autoupdate on` to re-enable updates, or `deepline settings autoupdate pin <version>` to hold an exact release.",
   packageCapabilities: {
     updatePreferences: 1

package/dist/release.mjs

@@ -48,7 +48,7 @@ var SDK_RELEASE = {
   // getters keep their established compatibility behavior.
   // 0.3.1 deprecated the legacy `deepline enrich` command in favor of Plays.
   // 0.3.90 is the first deliberately versioned SDK release for API v3.
-  version: "0.3.106",
+  version: "0.3.107",
   updateSummary: "Play grep now returns concise results with the matched fields and terms. Automatic CLI updates are enabled by default; use `deepline settings autoupdate off` to opt out, `deepline settings autoupdate on` to re-enable updates, or `deepline settings autoupdate pin <version>` to hold an exact release.",
   packageCapabilities: {
     updatePreferences: 1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "deepline",
-  "version": "0.3.106",
+  "version": "0.3.107",
   "description": "GTM data CLI and TypeScript SDK for coding agents",
   "license": "MIT",
   "homepage": "https://code.deepline.com",