@shipstatic/types 2.9.0 → 2.11.0-beta.1

package/dist/index.d.ts

@@ -73,12 +73,14 @@ export declare const DeploymentVia: {
      * A deploy that reached the REST API naming no origin at all — the
      * platform-wide fallback, one altitude below `mcp`'s family fallback.
      *
-     * **Declared ahead of its emitter, deliberately.** Nothing sends it yet and
-     * the server still records an unattributed deploy as `null`. Vocabulary must
-     * exist before a consumer can adopt it, and adding a member costs a full
-     * constellation convoy — so the word ships first and the API adopts it as a
-     * default whenever that decision is taken, with no convoy standing between
-     * the decision and the deploy.
+     * **The API stamps it, since 2026-08-15.** A deploy that names no origin —
+     * or names one this vocabulary does not know — is stored as `api`, so a
+     * stored `null` now means only that the row predates attribution.
+     *
+     * It was declared one wave ahead of that decision, deliberately: vocabulary
+     * must exist before a consumer can adopt it, and adding a member costs a
+     * full constellation convoy, so the word shipped first and the server
+     * adopted it with no convoy standing between the decision and the deploy.
      */
     readonly API: "api";
 };
@@ -104,7 +106,10 @@ export interface Deployment {
     /** Labels for categorization and filtering (lowercase, alphanumeric with separators). Always present, empty array when none. */
     labels: string[];
     /**
-     * The client/tool that created this deployment, null if unknown.
+     * The client/tool that created this deployment. Every deployment created
+     * today names one — {@link DeploymentVia.API} when the caller named nothing
+     * the vocabulary knows — so `null` is historical: the row predates
+     * attribution.
      *
      * Deliberately wider than {@link DeploymentViaType}: this is stored data,
      * and rows predate the vocabulary being closed. Narrowing the ENTITY would
@@ -622,6 +627,20 @@ export interface AccountKeyResponse {
     /** The raw API key (shown once at mint, then never again) */
     readonly secret: string;
 }
+/**
+ * What `GET /account/claim` answers — the render half of the claim door: the
+ * deployment a claim code names, and whether it is still there for THIS
+ * caller to take. Claimability is a fact of code-plus-caller only the API can
+ * compute; consumers must never infer it from `expires`, an entitlement
+ * detail that is free to diverge. (The POST — the intent half — answers the
+ * bare {@link Deployment} it moved.)
+ */
+export interface ClaimResolveResponse {
+    /** The deployment the code names, as the caller may see it. */
+    readonly deployment: Deployment;
+    /** Still the public account's to take — false once it is the caller's own. */
+    readonly claimable: boolean;
+}
 /**
  * Account-specific configuration overrides
  * Allows per-account customization of limits without changing plan
@@ -1117,6 +1136,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.
  *
@@ -1754,7 +1787,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
  */
@@ -1793,6 +1826,17 @@ export interface ActivityMeta {
     hasConfig?: boolean;
     /** Whether deployment has a password set */
     hasPassword?: boolean;
+    /**
+     * The client/tool that created the deployment.
+     *
+     * Narrower than {@link Deployment.via}, deliberately: the entity is
+     * `string | null` because stored rows predate the vocabulary, while an
+     * activity is only ever written by code that names one. It is here rather
+     * than read off the deployment because the deployment row is deleted at
+     * expiry or on request and the activity is not — this is where a deploy's
+     * origin stays answerable afterwards.
+     */
+    via?: DeploymentViaType;
     /** Whether this was an update (vs create) */
     isUpdate?: boolean;
     /** Whether domain was already verified */

package/dist/index.js

@@ -75,12 +75,14 @@ export const DeploymentVia = {
      * A deploy that reached the REST API naming no origin at all — the
      * platform-wide fallback, one altitude below `mcp`'s family fallback.
      *
-     * **Declared ahead of its emitter, deliberately.** Nothing sends it yet and
-     * the server still records an unattributed deploy as `null`. Vocabulary must
-     * exist before a consumer can adopt it, and adding a member costs a full
-     * constellation convoy — so the word ships first and the API adopts it as a
-     * default whenever that decision is taken, with no convoy standing between
-     * the decision and the deploy.
+     * **The API stamps it, since 2026-08-15.** A deploy that names no origin —
+     * or names one this vocabulary does not know — is stored as `api`, so a
+     * stored `null` now means only that the row predates attribution.
+     *
+     * It was declared one wave ahead of that decision, deliberately: vocabulary
+     * must exist before a consumer can adopt it, and adding a member costs a
+     * full constellation convoy, so the word shipped first and the server
+     * adopted it with no convoy standing between the decision and the deploy.
      */
     API: 'api',
 };
@@ -1108,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.9.0",
+  "version": "2.11.0-beta.1",
   "description": "Shared types for ShipStatic platform",
   "type": "module",
   "main": "./dist/index.js",

package/src/index.ts

@@ -80,12 +80,14 @@ export const DeploymentVia = {
    * A deploy that reached the REST API naming no origin at all — the
    * platform-wide fallback, one altitude below `mcp`'s family fallback.
    *
-   * **Declared ahead of its emitter, deliberately.** Nothing sends it yet and
-   * the server still records an unattributed deploy as `null`. Vocabulary must
-   * exist before a consumer can adopt it, and adding a member costs a full
-   * constellation convoy — so the word ships first and the API adopts it as a
-   * default whenever that decision is taken, with no convoy standing between
-   * the decision and the deploy.
+   * **The API stamps it, since 2026-08-15.** A deploy that names no origin —
+   * or names one this vocabulary does not know — is stored as `api`, so a
+   * stored `null` now means only that the row predates attribution.
+   *
+   * It was declared one wave ahead of that decision, deliberately: vocabulary
+   * must exist before a consumer can adopt it, and adding a member costs a
+   * full constellation convoy, so the word shipped first and the server
+   * adopted it with no convoy standing between the decision and the deploy.
    */
   API: 'api',
 } as const;
@@ -113,7 +115,10 @@ export interface Deployment {
   /** Labels for categorization and filtering (lowercase, alphanumeric with separators). Always present, empty array when none. */
   labels: string[];
   /**
-   * The client/tool that created this deployment, null if unknown.
+   * The client/tool that created this deployment. Every deployment created
+   * today names one — {@link DeploymentVia.API} when the caller named nothing
+   * the vocabulary knows — so `null` is historical: the row predates
+   * attribution.
    *
    * Deliberately wider than {@link DeploymentViaType}: this is stored data,
    * and rows predate the vocabulary being closed. Narrowing the ENTITY would
@@ -701,6 +706,21 @@ export interface AccountKeyResponse {
   readonly secret: string;
 }
 
+/**
+ * What `GET /account/claim` answers — the render half of the claim door: the
+ * deployment a claim code names, and whether it is still there for THIS
+ * caller to take. Claimability is a fact of code-plus-caller only the API can
+ * compute; consumers must never infer it from `expires`, an entitlement
+ * detail that is free to diverge. (The POST — the intent half — answers the
+ * bare {@link Deployment} it moved.)
+ */
+export interface ClaimResolveResponse {
+  /** The deployment the code names, as the caller may see it. */
+  readonly deployment: Deployment;
+  /** Still the public account's to take — false once it is the caller's own. */
+  readonly claimable: boolean;
+}
+
 /**
  * Account-specific configuration overrides
  * Allows per-account customization of limits without changing plan
@@ -1792,6 +1812,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.
  *
@@ -2639,6 +2674,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'
@@ -2733,6 +2769,17 @@ export interface ActivityMeta {
   hasConfig?: boolean;
   /** Whether deployment has a password set */
   hasPassword?: boolean;
+  /**
+   * The client/tool that created the deployment.
+   *
+   * Narrower than {@link Deployment.via}, deliberately: the entity is
+   * `string | null` because stored rows predate the vocabulary, while an
+   * activity is only ever written by code that names one. It is here rather
+   * than read off the deployment because the deployment row is deleted at
+   * expiry or on request and the activity is not — this is where a deploy's
+   * origin stays answerable afterwards.
+   */
+  via?: DeploymentViaType;
 
   // Domain events
   /** Whether this was an update (vs create) */