@shipstatic/types 2.10.0 → 2.12.0-beta.1

package/dist/index.d.ts

@@ -1122,6 +1122,20 @@ export interface PingResponse {
  * already share the credential prefixes below.
  */
 export declare const AUTH_BASE_PATH = "/auth";
+/**
+ * The query marker a completed sign-in LANDS with.
+ *
+ * The API's magic-link verify leg stamps `?signing-in=1` onto its success
+ * redirect, and the console boots into its wait screen on seeing it — two
+ * repos, one spelling, which is why it lives here. Success is marked and the
+ * error leg deliberately is NOT: the console gives the marker precedence, so
+ * a marked error would render a wait that resolves to bare doors with the
+ * error's sentence lost. If the spellings ever diverged the failure would be
+ * invisible to every suite — email landings would flash the doors for one
+ * round trip instead of waiting — which is exactly the silent-drift class
+ * this constitution exists to delete.
+ */
+export declare const SIGN_IN_RETURN_PARAM = "signing-in";
 /**
  * How a request (or recorded activity) was authorized.
  *
@@ -1759,7 +1773,7 @@ export interface CheckoutSession {
  * All activity event types logged in the system.
  * Uses dot notation consistently: {resource}.{action}
  */
-export type ActivityEvent = 'account.create' | 'account.update' | 'account.delete' | 'account.key.generate' | 'account.plan.paid' | 'account.plan.transition' | 'account.suspended' | 'deployment.create' | 'deployment.update' | 'deployment.delete' | 'deployment.claim' | 'deployment.flagged' | 'domain.create' | 'domain.update' | 'domain.delete' | 'domain.verify' | 'token.create' | 'token.consume' | 'token.delete' | 'admin.account.plan.update' | 'admin.account.ref.update' | 'admin.account.billing.update' | 'admin.account.labels.update' | 'admin.deployment.delete' | 'admin.domain.delete' | 'admin.billing.sync' | 'admin.billing.terminated' | 'admin.impersonate' | 'billing.active' | 'billing.canceled' | 'billing.paused' | 'billing.expired' | 'billing.paid' | 'billing.trialing' | 'billing.scheduled_cancel' | 'billing.unpaid' | 'billing.update' | 'billing.past_due' | 'refund.created' | 'dispute.created' | 'billing.sync' | 'billing.stale' | 'billing.race';
+export type ActivityEvent = 'account.create' | 'account.update' | 'account.delete' | 'account.key.generate' | 'account.plan.paid' | 'account.plan.transition' | 'account.suspended' | 'deployment.create' | 'deployment.update' | 'deployment.delete' | 'deployment.claim' | 'deployment.flagged' | 'deployment.open' | 'domain.create' | 'domain.update' | 'domain.delete' | 'domain.verify' | 'token.create' | 'token.consume' | 'token.delete' | 'admin.account.plan.update' | 'admin.account.ref.update' | 'admin.account.billing.update' | 'admin.account.labels.update' | 'admin.deployment.delete' | 'admin.domain.delete' | 'admin.billing.sync' | 'admin.billing.terminated' | 'admin.impersonate' | 'billing.active' | 'billing.canceled' | 'billing.paused' | 'billing.expired' | 'billing.paid' | 'billing.trialing' | 'billing.scheduled_cancel' | 'billing.unpaid' | 'billing.update' | 'billing.past_due' | 'refund.created' | 'dispute.created' | 'billing.sync' | 'billing.stale' | 'billing.race';
 /**
  * Activity events visible to users in the dashboard
  */

package/dist/index.js

@@ -1110,6 +1110,20 @@ export function hasUnbuiltMarker(filePath) {
  * already share the credential prefixes below.
  */
 export const AUTH_BASE_PATH = '/auth';
+/**
+ * The query marker a completed sign-in LANDS with.
+ *
+ * The API's magic-link verify leg stamps `?signing-in=1` onto its success
+ * redirect, and the console boots into its wait screen on seeing it — two
+ * repos, one spelling, which is why it lives here. Success is marked and the
+ * error leg deliberately is NOT: the console gives the marker precedence, so
+ * a marked error would render a wait that resolves to bare doors with the
+ * error's sentence lost. If the spellings ever diverged the failure would be
+ * invisible to every suite — email landings would flash the doors for one
+ * round trip instead of waiting — which is exactly the silent-drift class
+ * this constitution exists to delete.
+ */
+export const SIGN_IN_RETURN_PARAM = 'signing-in';
 /**
  * How a request (or recorded activity) was authorized.
  *

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@shipstatic/types",
-  "version": "2.10.0",
+  "version": "2.12.0-beta.1",
   "description": "Shared types for ShipStatic platform",
   "type": "module",
   "main": "./dist/index.js",

package/src/index.ts

@@ -1797,6 +1797,21 @@ export interface PingResponse {
  */
 export const AUTH_BASE_PATH = '/auth';
 
+/**
+ * The query marker a completed sign-in LANDS with.
+ *
+ * The API's magic-link verify leg stamps `?signing-in=1` onto its success
+ * redirect, and the console boots into its wait screen on seeing it — two
+ * repos, one spelling, which is why it lives here. Success is marked and the
+ * error leg deliberately is NOT: the console gives the marker precedence, so
+ * a marked error would render a wait that resolves to bare doors with the
+ * error's sentence lost. If the spellings ever diverged the failure would be
+ * invisible to every suite — email landings would flash the doors for one
+ * round trip instead of waiting — which is exactly the silent-drift class
+ * this constitution exists to delete.
+ */
+export const SIGN_IN_RETURN_PARAM = 'signing-in';
+
 /**
  * How a request (or recorded activity) was authorized.
  *
@@ -2644,6 +2659,7 @@ export type ActivityEvent =
   | 'deployment.delete'
   | 'deployment.claim'
   | 'deployment.flagged' // Internal: HTML content matched a detection rule (not user-visible)
+  | 'deployment.open' // Internal: an operator opened hosted content for moderation (not user-visible)
   // Domain events
   | 'domain.create'
   | 'domain.update'