@shipstatic/ship 2.9.4-beta.2 → 2.9.4-beta.3

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -5,7 +5,7 @@ Their copyright notices travel with that copy, and are reproduced here in
5
5
  full. This file is GENERATED from the build's own metafile — edit the
6
6
  bundle, not this list.
7
7
 
8
- ## @shipstatic/types 2.26.0-beta.2
8
+ ## @shipstatic/types 2.26.0-beta.3
9
9
 
10
10
  License: MIT
11
11
 
package/dist/browser.d.ts CHANGED
@@ -479,13 +479,28 @@ interface SetupInstructionsResponse {
479
479
  * one key cannot mean both. See {@link DeploymentDeleteResponse} for the law.
480
480
  */
481
481
  interface DomainValidateResponse {
482
- /** Whether the domain is valid */
482
+ /** Whether the domain's SHAPE is usable: format, and the caller's own rules. */
483
483
  valid: boolean;
484
484
  /** Normalized domain name, null when invalid */
485
485
  normalized: string | null;
486
- /** Whether the domain is available, null when invalid */
486
+ /**
487
+ * Whether nobody has registered the name yet; null when invalid.
488
+ *
489
+ * It answers "would creating this be new", not "would a write succeed": `PUT
490
+ * /domains/:domain` is an upsert, which is how a domain is re-pointed, so a
491
+ * caller's OWN domain is unavailable here and writable there. Availability
492
+ * does not depend on the kind of name; a custom domain answered `true`
493
+ * whoever owned it until 2026-09-17.
494
+ */
487
495
  available: boolean | null;
488
- /** Why the name is unusable, null when valid — displayed verbatim. */
496
+ /**
497
+ * Why the name is unusable, null when it IS usable — displayed verbatim.
498
+ *
499
+ * A name is unusable when it is invalid OR unavailable, and both carry a
500
+ * reason. This said "null when valid" until 2026-09-17, which was already
501
+ * untrue of the endpoint it described: a registered name is valid, is
502
+ * unusable, and had no reason at all, which is why every client invented one.
503
+ */
489
504
  reason: string | null;
490
505
  }
491
506
  /**