@mysten/docs 0.1.34 → 0.1.35

package/dist/sponsor/validators.md

@@ -4,14 +4,19 @@
 
 A validator is an analyzer used for policy checks. Create one with `createAnalyzer(...)`, return the
 issues it found, and pass it to `createSponsor({ validate })`. It declares the analyzers it reads
-through `dependencies` and reports one of three outcomes:
+through `dependencies` and reports these outcomes:
 
 - **pass**: `{ result: null }` (or `{ result: [] }`);
 - **reject**: `{ result: [{ code, message }] }`: the transaction is well-formed but violates policy
   (`POLICY_REJECTED`);
+- **partial**: `{ result: [{ code, message }], issues: [{ message }] }`: the validator found a
+  policy rejection but also hit an analysis issue, so sponsor validation reports both and treats the
+  overall reason as `ANALYSIS_FAILED`;
 - **couldn't analyze**: `{ issues: [{ message }] }` or `throw`: the analyzer itself couldn't decide
   (a failed lookup, an unreachable service), producing `ANALYSIS_FAILED`. This is the analyzer
-  framework's own channel, so it propagates, and dependents don't run.
+  framework's own channel, so it propagates through strict dependencies. Sponsor validation treats
+  each configured validator independently, so one validator's analysis failure doesn't suppress
+  policy rejections from other validators.
 
 Reporting findings as the `result` (rather than through `issues`) is what keeps "violates policy"
 distinct from "couldn't be checked". There's no built-in "the sponsor must be paid" rule, because
@@ -44,8 +49,10 @@ expiration), which most validators read. Alongside it: `balanceFlows` (signed va
 `transactionResponse` (the dry-run, including effects), `commands`, `moveFunctions`, `objects`,
 `coins`, `inputs`, and `bytes`, plus the sponsor's `currentEpoch`, and any others the analyzer
 package adds (see [`@mysten/wallet-sdk`](https://www.npmjs.com/package/@mysten/wallet-sdk) for the
-full set). All are re-exported as `analyzers` (with `currentEpoch` and `createAnalyzer` alongside).
-A failed analyzer never reaches your `analyze`: it short-circuits to an `ANALYSIS_FAILED` rejection.
+full set). All are re-exported as `analyzers` (with `currentEpoch`, `createAnalyzer`, and `optional`
+alongside). A failed required analyzer never reaches your validator's `analyze`: that validator
+contributes an `ANALYSIS_FAILED` issue while independent validators can still report policy
+rejections.
 
 ## Loading data, and sharing it across validators
 
@@ -117,7 +124,7 @@ await sponsor.signAndExecuteTransaction({
 
 ## How it runs
 
-`createSponsor` makes every validator a dependency of **`sponsor.analyzer`**, and validation is just
+`createSponsor` aggregates every validator through **`sponsor.analyzer`**, and validation is just
 `analyze({ check: sponsor.analyzer }, { transaction, client })`. The analyzer framework then
 handles:
 
@@ -127,13 +134,15 @@ handles:
   declare, because it falls out of the dependency graph.
 - **Deduped**: `data` and `balanceFlows` and so on resolve once even when many validators (and a
   host graph) depend on them.
-- **Propagated**: a failed analyzer becomes an `ANALYSIS_FAILED` rejection rather than reaching a
-  validator with a broken value.
+- **Independent failure reporting**: a failed validator becomes an `ANALYSIS_FAILED` entry in
+  `analysisIssues`, without suppressing policy rejections from validators that did run.
 
 When validation fails, the sponsor never signs and the method **returns**
-`{ $kind: 'Rejected', issues, reason }`, where `issues` lists every reason, and `reason` is
-`'POLICY_REJECTED'` or `'ANALYSIS_FAILED'`. To turn a rejection into a thrown error, the exported
-`SponsorValidationError` class takes `(issues, reason)`.
+`{ $kind: 'Rejected', issues, policyIssues, analysisIssues, reason }`. `issues` preserves the
+combined list for existing callers, while `policyIssues` and `analysisIssues` separate policy
+rejections from checks that could not run. `reason` is `'POLICY_REJECTED'` when every reported issue
+is policy-only and `'ANALYSIS_FAILED'` when any check could not run. To turn a rejection into a
+thrown error, the exported `SponsorValidationError` class takes `(issues, reason)`.
 
 **`sponsor.analyzer`** is also the composable handle: drop it into any other `analyze()` graph and
 it contributes `SponsorRejection | null`, deduping its analyzers with that graph.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mysten/docs",
-  "version": "0.1.34",
+  "version": "0.1.35",
   "description": "LLM-friendly documentation for the Sui TypeScript SDK ecosystem",
   "license": "Apache-2.0",
   "repository": {
@@ -28,28 +28,28 @@
     "next": "^16.2.9",
     "react": "^19.2.7",
     "react-dom": "^19.2.7",
-    "@mysten/aws-kms-signer": "0.3.0",
-    "@mysten/dapp-kit-react": "2.1.5",
+    "@mysten/aws-kms-signer": "0.3.1",
+    "@mysten/dapp-kit-core": "1.6.4",
     "@mysten/bcs": "2.1.0",
-    "@mysten/dapp-kit-core": "1.6.3",
-    "@mysten/dapp-kit": "1.1.3",
-    "@mysten/deepbook-v3": "1.5.3",
-    "@mysten/enoki": "1.2.1",
-    "@mysten/kiosk": "1.3.3",
-    "@mysten/enoki-connect": "1.1.3",
-    "@mysten/gcp-kms-signer": "0.2.3",
-    "@mysten/ledger-signer": "0.2.3",
-    "@mysten/payment-kit": "0.2.3",
-    "@mysten/seal": "1.2.3",
-    "@mysten/signers": "1.1.3",
-    "@mysten/slush-wallet": "1.1.3",
+    "@mysten/dapp-kit": "1.1.4",
+    "@mysten/dapp-kit-react": "2.1.6",
+    "@mysten/enoki": "1.2.2",
+    "@mysten/enoki-connect": "1.1.4",
+    "@mysten/kiosk": "1.3.4",
+    "@mysten/gcp-kms-signer": "0.2.4",
+    "@mysten/deepbook-v3": "1.5.4",
+    "@mysten/ledger-signer": "0.2.4",
+    "@mysten/signers": "1.1.4",
+    "@mysten/slush-wallet": "1.1.4",
+    "@mysten/suins": "1.2.4",
+    "@mysten/sui": "2.20.2",
     "@mysten/utils": "0.4.0",
-    "@mysten/wallet-standard": "0.21.3",
-    "@mysten/webcrypto-signer": "0.2.3",
-    "@mysten/walrus": "1.2.3",
-    "@mysten/zksend": "1.2.3",
-    "@mysten/suins": "1.2.3",
-    "@mysten/sui": "2.20.1"
+    "@mysten/wallet-standard": "0.21.4",
+    "@mysten/seal": "1.2.4",
+    "@mysten/payment-kit": "0.2.4",
+    "@mysten/walrus": "1.2.4",
+    "@mysten/webcrypto-signer": "0.2.4",
+    "@mysten/zksend": "1.2.4"
   },
   "devDependencies": {
     "@tailwindcss/postcss": "^4.3.1",