refactor!: ADR-0112 batch 2 — sweep the lowercase error-code emitters (#4003) (#4021)

* refactor(spec)!: connector-side error enums get Connector* names (ADR-0112 D9a)

packages/spec exported two mutually incompatible ErrorCategory types and two
RetryStrategy types — api/errors.zod.ts (HTTP error responses) and
integration/connector.zod.ts (connector normalisation). Separate subpath
exports kept TypeScript quiet, but the doc/schema generators key on the
stripped name, so a cross-reference to 'ErrorCategory' resolved to whichever
was scanned last.

Rename the connector-side pair to ConnectorErrorCategory / ConnectorRetryStrategy
and say in each docblock why the name is prefixed. Both are spec-internal (only
connector.zod.ts and its test referenced them), so no downstream break.

The json-schema ratchet caught the rename as an unpublish; the two manifest keys
are renamed alongside, per its instructions.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MaSQn77TT5fUgHK9CesaDK

* refactor(cloud-connection,plugin-auth,hono)!: sweep the two largest lowercase code clusters (ADR-0112 batch 2)

Converts 105 lowercase snake_case error codes to the declared vocabulary and
registers the service-specific ones in ERROR_CODE_LEDGER.

Generic conditions collapse onto the standard catalog rather than keeping a
synonym: 'unauthorized'/'unauthenticated' -> UNAUTHENTICATED, 'forbidden' ->
PERMISSION_DENIED, 'not_found' -> RESOURCE_NOT_FOUND, 'internal' ->
INTERNAL_ERROR, 'unavailable' -> SERVICE_UNAVAILABLE, 'not_supported' ->
NOT_IMPLEMENTED, and 'bad_request' -> INVALID_REQUEST (a status name is not a
semantic code). Domain conditions get registered codes, prefixed where the bare
name wouldn't carry meaning (MARKETPLACE_STORAGE_FAILED, PLUGIN_MANIFEST_INVALID,
ENVIRONMENT_BIND_FAILED, RESEED_SKIPPED, ...). New ledger entries:
@objectstack/cloud-connection and @objectstack/hono.

Also closes an unbounded code source found while sweeping: the OAuth client
registration route put better-auth's arbitrary `body.error` string straight into
`error.code`, so any upstream string became a code and the closed set could not
hold. The code is now ours (OAUTH_REGISTER_FAILED) and the upstream
discriminator moves to `details.upstreamError`.

Per-package consumer check (ADR-0112 batch-2 precondition): no reader outside
either package branches on the swept spellings; the in-package test assertions
move with the emitters.

Refs #4003, #3841.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MaSQn77TT5fUgHK9CesaDK

* refactor(metadata-protocol,service-automation,spec)!: sweep the thrown-error codes; keep the audit column out (ADR-0112 batch 2)

Three clusters, all of which reach `error.code` on the wire — a thrown error's
`.code` is copied straight into the response body (rest-server.ts:268), so these
were never merely internal.

- metadata-protocol: 24 thrown codes (ITEM_LOCKED, NOT_OVERRIDABLE,
  METADATA_CONFLICT, DESTRUCTIVE_CHANGE, ...) registered under the package, plus
  the two `evaluateLockFor*` helpers in spec that feed them.
- service-automation resume refusals: 'forbidden' -> PERMISSION_DENIED,
  'invalid_signal' -> INVALID_SIGNAL, together with the runtime branch that
  reads them and the contract docstring that documents them.

Two decisions worth keeping:

`sys_metadata_audit.code` is deliberately NOT swept. It spells its denial
reasons identically to the codes the protocol throws, so a naive sweep renames
it too — but the column is persisted audit history (rows predating ADR-0112 keep
their spelling forever) and it also holds non-error outcomes ('ok',
'lock_override'). Following the catalog would buy a data migration or one column
with two vocabularies mixed by write date. It stays lowercase and self-contained;
the divergence is recorded at both sites and as ADR-0112 D6b, so it reads as a
decision rather than a missed rename.

The ADR's "no consumer branches on the lowercase dialect" claim was wrong: the
per-service re-verification it mandated found three, each renamed atomically
here. The ADR now records the correction plus a sweep checklist of the six
literal forms a `code: '...'` grep misses (comparisons, property assignment,
computed ternaries, regex assertions, toBe assertions, docstrings) — every one
of them cost a red suite in this batch.

Refs #4003, #3841.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MaSQn77TT5fUgHK9CesaDK

* refactor(rest,service-messaging,plugin-webhooks)!: sweep the last top-level codes and un-nest three flat envelopes (ADR-0112 batch 2)

- rest: OBJECT_NOT_FOUND, UNAUTHENTICATED (it sat in the same if/else as an
  already-SCREAMING PERMISSION_DENIED), INVALID_REQUEST.
- service-messaging redeliver: RESOURCE_NOT_FOUND / DELIVERY_NOT_ELIGIBLE, with
  the plugin-webhooks route that branches on them.

Three routes also had a bare code string in the `error:` slot with a real
`message:` beside it, so `error` was a code and the declared object envelope was
nowhere. They now emit `error: { code, message }` — a rename alone would have
left them unvalidated, which is how the lowercase dialect survived the first
place.

`mapDataError`'s downcasing is inverted, not just renamed. It deliberately
translated the internal SCREAMING OBJECT_NOT_FOUND down to `object_not_found` on
the way out, and a test pinned exactly that ("does not let the generic 4xx
passthrough ship the internal SCREAMING_CASE code") — correct when the data
routes were believed to speak their own dialect, backwards once there is one
vocabulary. The translation is gone and the test is rewritten to pin what still
matters: no per-route dialect translation, what the gate threw is what ships.
Two comments that still taught the lowercase wire code are updated with it.

Field-level codes in `import-coerce.ts` are deliberately untouched (ADR-0112 D6,
#3977).

Refs #4003, #3841.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MaSQn77TT5fUgHK9CesaDK

* docs: add batch-2 changeset; webhook redeliver doc follows the new envelope

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MaSQn77TT5fUgHK9CesaDK

* refactor(trigger-api,spec)!: trigger-api answers in the declared envelope; draw the catalog's boundary (ADR-0112 batch 2)

The API-trigger webhook endpoint returned `{ error: '<code>' }` — a bare code in
the message slot, six times, three of them with no message at all. It now answers
`{ success: false, error: { code, message } }` with catalog codes
(RESOURCE_NOT_FOUND, INVALID_REQUEST, SERVICE_UNAVAILABLE) plus two registered
ones (INVALID_SIGNATURE, ENQUEUE_FAILED). Every branch gains the message it was
missing.

Also records what batch 2 decided NOT to sweep, as ADR-0112 D6c, because three
lowercase clusters look like stragglers and are not:

- Diagnostics records (`build-probes.ts` RuntimeBuildIssue,
  `metadata-diagnostics.ts`) ship as the payload of a 200, describe an artifact
  rather than the request, and carry a severity that can be 'warning'.
- Param/field-addressed issues (`ActionParamIssue`, plugin-sharing's `fields[]`)
  are D6 territory; plugin-sharing's own top-level code is already
  VALIDATION_FAILED.
- CLI `emitJson({ error: '...' })` output is a terminal contract read by shell
  scripts, not a request response — renaming it would break users' pipelines
  with neither a schema nor this ADR asking for it.

The line, now written down once: the catalog governs the code a failing REQUEST
answers with. Field-addressed (D6), persisted (D6b), or shipped inside a
successful response (D6c) means a different vocabulary with different consumers.

Refs #4003, #3841.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MaSQn77TT5fUgHK9CesaDK

* fix(spec)!: the automation resume contract's code type follows the rename

The resume result's `code` is a literal-union TYPE in the service contract, not
just a value, and batch 2 renamed only the values plus the docstring beside it.
Nothing in spec failed: `tsc --noEmit` on the declaring package is happy with a
narrower union than its callers emit. The break surfaced two packages away — the
dts build of every consumer of @objectstack/spec/integration, which is what took
Build Core, Test Core and the dogfood shards red at once.

Added to the ADR's sweep checklist as its own row, since it is the one form whose
error appears in a package the sweep never touched.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MaSQn77TT5fUgHK9CesaDK

* fix(runtime,plugin-approvals,metadata-protocol): the last four readers of the automation and publish codes

Four more consumers of codes batch 2 renamed, found by running the full suite
rather than grepping harder:

- plugin-approvals asserts the resume refusal code (its approval node IS the
  service-gated case), a package the sweep never touched.
- http-dispatcher.test mocks the automation service's result, so its two
  literals are the emitter's contract restated in a mock.
- batch_aborted -> BATCH_ABORTED: it rides in the same failed[] array as the
  causal item's catalog code, so leaving it lowercase made one array carry two
  vocabularies.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MaSQn77TT5fUgHK9CesaDK

* fix(qa): the dogfood package-first authoring assertion follows the rename

Sixth consumer found, and the one my local verification could not have caught:
the full-suite run I used as the safety net excludes @objectstack/dogfood by
design, so the dogfood shards were the one gate I had not actually run.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MaSQn77TT5fUgHK9CesaDK

* feat(ci): guard against new lowercase error codes (ADR-0112, #4003)

The ledger's admission test enforces casing on every code someone REGISTERS.
Nothing enforced the ones nobody registers — and an unregistered lowercase
literal in a code position is invisible twice: to the ledger, which has nothing
to check, and to the schema, on any route that never parses its own response.
That is how 208 lowercase literals accumulated across 10 packages. Without a
guard, number 209 lands the same way.

`scripts/check-error-code-casing.mjs` scans packages/ for four code positions —
emission, property assignment, comparison, and literal-union type — which are
the forms batch 2 actually got bitten by, comparison and union-type being the two
that fail silently or two packages away.

The design problem is that `code` is also an ordinary domain field name: a
license plan code, a seed industry code, a locale. A guard that flags those gets
switched off within a week, so a hit only counts when an error-shaped neighbour
(error/message/throw/status/issues/...) appears within a few lines, and the
D6 families are recognised structurally — a `field`/`param`/`path`/`target` key
in the same record, checked over a window because `{ code, field, message }` is
routinely spread across three lines.

Three escape hatches, in descending preference:
  - structural: the D6 shapes above, no annotation needed;
  - `// adr0112-ok: <reason>` at the site, for a file that legitimately holds
    both vocabularies (protocol.ts throws a catalog code and writes an audit row
    beside it) — the reason is required, a bare marker does not count;
  - EXEMPT_FILES, for a file that OWNS a non-catalog vocabulary (a diagnostics
    producer, OData's foreign error vocabulary), each line carrying its reason.

`--self-test` runs 17 cases (each violating form, each exemption route, each
known false-positive shape) before the scan, so a green run means the matcher
was checked, not just quiet. End-to-end verified by reintroducing
`code: 'object_not_found'` in rest-server.ts: the guard fails, and passes again
when reverted.

Two real fixes fell out of turning it on: the `'locked'` fixtures in two
publish tests now spell what the protocol actually throws (ITEM_LOCKED), and the
audit-row sites carry their D6b marker so the divergence reads as a decision.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MaSQn77TT5fUgHK9CesaDK

* docs: the batch-2 changeset covers trigger-api, plugin-approvals and the new guard

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MaSQn77TT5fUgHK9CesaDK

---------

Co-authored-by: Claude <noreply@anthropic.com>

Author: os-zhuang

.changeset/adr-0112-batch-2-lowercase-sweep.md

@@ -0,0 +1,66 @@
+---
+"@objectstack/spec": minor
+"@objectstack/rest": minor
+"@objectstack/runtime": minor
+"@objectstack/cloud-connection": minor
+"@objectstack/plugin-auth": minor
+"@objectstack/plugin-approvals": minor
+"@objectstack/plugin-webhooks": minor
+"@objectstack/service-messaging": minor
+"@objectstack/service-automation": minor
+"@objectstack/metadata-protocol": minor
+"@objectstack/metadata-core": minor
+"@objectstack/trigger-api": minor
+"@objectstack/hono": minor
+---
+
+refactor!: ADR-0112 batch 2 — sweep the lowercase error-code emitters (#4003)
+
+Continues #3841 per ADR-0112. Batch 1 (#3988) settled the vocabulary and closed
+the set; this batch moves the emitters that still spoke lowercase `snake_case`
+onto it.
+
+**Wire-visible change.** Error codes on these surfaces change spelling. Generic
+conditions collapse onto the standard catalog rather than keeping a synonym:
+`unauthorized`/`unauthenticated` → `UNAUTHENTICATED`, `forbidden` →
+`PERMISSION_DENIED`, `not_found` → `RESOURCE_NOT_FOUND`, `internal` →
+`INTERNAL_ERROR`, `unavailable` → `SERVICE_UNAVAILABLE`, `not_supported` →
+`NOT_IMPLEMENTED`, `bad_request` → `INVALID_REQUEST`. Domain conditions get codes
+registered in `ERROR_CODE_LEDGER` (`MARKETPLACE_STORAGE_FAILED`,
+`PLUGIN_MANIFEST_INVALID`, `ITEM_LOCKED`, `DELIVERY_NOT_ELIGIBLE`, …). Swept:
+`cloud-connection`, `plugin-auth`, `hono`, `metadata-protocol`, `rest`,
+`service-messaging`, `service-automation`, `trigger-api`.
+
+Branch on `error.code` values rather than pattern-matching their case: the
+console's fix for the same rename (objectui#2977) reads codes case-insensitively
+for exactly this reason, and that is the pattern to copy in your own consumers if
+you support servers on both sides of the change.
+
+**Four routes stop putting a code in the message slot.** The webhook redeliver
+route, the API-trigger webhook, and two `rest` routes answered
+`{ success: false, error: '<code>', message }` — the code occupying `error`, the
+declared object envelope nowhere. They now emit `error: { code, message }`, and
+three API-trigger branches gained a message they never had. Clients reading
+`body.error` as a string on those routes must read `body.error.code`.
+
+**`ConnectorErrorCategory` / `ConnectorRetryStrategy`** (ADR-0112 D9a):
+`@objectstack/spec` exported two mutually incompatible `ErrorCategory` types and
+two `RetryStrategy` types. The connector-side pair is renamed; importers of the
+`integration` subpath update the name. Side effect: the api-side `ErrorCategory`
+and `RetryStrategy` now appear in the generated API reference at all — the name
+collision had been silently dropping them.
+
+**`OAUTH_REGISTER_FAILED` replaces an unbounded code source.** The OAuth client
+registration route put better-auth's arbitrary `body.error` string straight into
+`error.code`. The code is now ours and the upstream discriminator moved to
+`details.upstreamError`.
+
+**Not swept, deliberately.** `sys_metadata_audit.code` keeps its lowercase values
+(ADR-0112 D6b): it is persisted audit history, and the same column holds
+non-error outcomes (`ok`, `lock_override`). Diagnostics records that ship inside a
+200 keep theirs (D6c), as do field-level codes (D6, #3977) and the CLI's
+`--json` output contract.
+
+A `check:error-code-casing` CI guard now fails on a new lowercase literal in a
+code position, since the ledger's casing rule can only police codes that someone
+registers.

.github/workflows/lint.yml

@@ -114,6 +114,15 @@ jobs:
       - name: Response-envelope guard
         run: pnpm check:route-envelope
 
+      # Error-code casing guard (ADR-0112, #4003). The ledger's admission test
+      # enforces casing on every code someone REGISTERS; this catches the ones
+      # nobody registers — an unregistered lowercase literal in a code position
+      # is invisible to both the ledger and to the schema on any route that does
+      # not parse its own response. That is how 208 of them accumulated across
+      # 10 packages before batch 2. Runs its own --self-test first.
+      - name: Error-code casing guard
+        run: pnpm check:error-code-casing
+
       # Release-notes drift guard: the platform is one version-locked train, so
       # every released @objectstack/spec major must have a curated, navigable
       # release page at content/docs/releases/v<major>.mdx. Catches the gap that

content/docs/automation/webhooks.mdx

@@ -399,10 +399,11 @@ The plugin mounts exactly **one** custom endpoint:
 | POST   | `/api/v1/webhooks/redeliver` | `{ deliveryId }`  | Re-queue a previously failed/dead delivery.      |
 
 It delegates to `messaging.redeliverHttp(deliveryId)` and is guarded by the
-better-auth session (any authenticated user). Responses: `200` on success,
-`401` unauthenticated, `400` missing/invalid body, `404` `not_found`, `409`
-`not_eligible`. There are no `/webhooks/:id/test`, `/rotate`,
-`/deliveries`, or per-delivery redeliver routes.
+better-auth session (any authenticated user). Failures answer in the declared
+envelope — `{ success: false, error: { code, message } }` — with `401`
+`UNAUTHENTICATED`, `400` `INVALID_REQUEST` or `MISSING_REQUIRED_FIELD`, `404`
+`RESOURCE_NOT_FOUND`, `409` `DELIVERY_NOT_ELIGIBLE` (ADR-0112). There are no
+`/webhooks/:id/test`, `/rotate`, `/deliveries`, or per-delivery redeliver routes.
 
 ## 9. Concurrency & rate-limiting
 

content/docs/references/api/analytics.mdx

@@ -12,42 +12,13 @@ description: Connector protocol schemas
 ## TypeScript Usage
 
 ```typescript
-import { ErrorCategory, RetryStrategy, WebhookConfig, WebhookEvent } from '@objectstack/spec/api';
-import type { ErrorCategory, RetryStrategy, WebhookConfig, WebhookEvent } from '@objectstack/spec/api';
+import { WebhookConfig, WebhookEvent } from '@objectstack/spec/api';
+import type { WebhookConfig, WebhookEvent } from '@objectstack/spec/api';
 
 // Validate data
-const result = ErrorCategory.parse(data);
+const result = WebhookConfig.parse(data);
 ```
 
----
-
-## ErrorCategory
-
-### Allowed Values
-
-* `validation`
-* `authentication`
-* `authorization`
-* `not_found`
-* `conflict`
-* `rate_limit`
-* `server`
-* `external`
-* `maintenance`
-
-
----
-
-## RetryStrategy
-
-### Allowed Values
-
-* `no_retry`
-* `retry_immediate`
-* `retry_backoff`
-* `retry_after`
-
-
 ---
 
 ## WebhookConfig

content/docs/references/api/auth.mdx

@@ -137,13 +137,18 @@ const result = ErrorCode.parse(data);
 * `ATTACHMENT_DOWNLOAD_DENIED`
 * `ATTACHMENT_PARENT_ACCESS`
 * `AUDIENCE_NOT_ALLOWED`
+* `AUTH_CONFIG_ERROR`
 * `AUTH_REQUIRED`
 * `AUTOMATION_UNSCOPED_RUN_DATA_ACCESS`
+* `BATCH_ABORTED`
 * `BATCH_NOT_ATOMIC`
 * `BATCH_TOO_LARGE`
 * `BATCH_UNRESOLVED_REF`
 * `BLANK_MATCH_KEY`
 * `CLONE_DISABLED`
+* `CLOUD_FETCH_FAILED`
+* `CLOUD_UNCONFIGURED`
+* `COMMIT_NOT_FOUND`
 * `CONCURRENT_UPDATE`
 * `CONFLICTING_MAPPING`
 * `CONNECTOR_UPSTREAM_UNAVAILABLE`
@@ -152,10 +157,18 @@ const result = ErrorCode.parse(data);
 * `DATASET_INVALID`
 * `DATASOURCE_ADMIN_ERROR`
 * `DELEGABLE_SCOPE_FAILED`
+* `DELIVERY_NOT_ELIGIBLE`
+* `DESTRUCTIVE_CHANGE`
+* `DEVICE_CODE_FAILED`
+* `DOMAIN_VERIFICATION_DISABLED`
 * `DOMAIN_VERIFICATION_FAILED`
+* `DRIVER_UNAVAILABLE`
 * `DUPLICATE_REQUEST`
 * `EMAIL_SEND_FAILED`
 * `EMAIL_SERVICE_REQUIRED`
+* `ENQUEUE_FAILED`
+* `ENVIRONMENT_BIND_FAILED`
+* `ENVIRONMENT_NOT_FOUND`
 * `ENV_ACCESS_DENIED`
 * `ERR_BULK_RESULT_MISMATCH`
 * `ERR_DATASOURCE_UNAVAILABLE`
@@ -187,22 +200,30 @@ const result = ErrorCode.parse(data);
 * `INTERNAL`
 * `INVALID_EMAIL`
 * `INVALID_EXPIRY`
+* `INVALID_METADATA`
 * `INVALID_OR_EXPIRED`
 * `INVALID_PHONE`
 * `INVALID_REQUEST`
 * `INVALID_RESUME_TOKEN`
+* `INVALID_SIGNAL`
+* `INVALID_SIGNATURE`
 * `INVALID_STATE`
 * `INVITE_EMAIL_FAILED`
 * `INVITE_REQUIRES_EMAIL`
 * `INVITE_SMS_FAILED`
 * `IP_NOT_ALLOWED`
+* `ITEM_LOCKED`
 * `LAST_LOCAL_CREDENTIAL`
 * `LOOKUP_NOT_PUBLIC`
 * `LOOKUP_TARGET_MISSING`
+* `MANIFEST_CONFLICT`
 * `MAPPING_FORMAT_MISMATCH`
 * `MAPPING_FORMAT_UNSUPPORTED`
 * `MAPPING_NOT_FOUND`
 * `MAPPING_TARGET_MISMATCH`
+* `MARKETPLACE_PROXY_FAILED`
+* `MARKETPLACE_STORAGE_FAILED`
+* `MARKETPLACE_UNAVAILABLE`
 * `METADATA_BRANCH`
 * `METADATA_CONFLICT`
 * `METADATA_NOT_FOUND`
@@ -211,15 +232,22 @@ const result = ErrorCode.parse(data);
 * `NAMESPACE_PREFIX`
 * `NEEDS_PASSWORD`
 * `NODE_FAILURE`
+* `NOTHING_TO_PURGE`
+* `NOT_CREATABLE`
 * `NOT_FOUND`
+* `NOT_OVERRIDABLE`
 * `NOT_UNDOABLE`
+* `NO_DRAFT`
 * `NO_EXECUTOR`
 * `NO_IDENTITY`
 * `NO_MATCH`
 * `NO_PENDING_VERIFICATION`
+* `OAUTH_REGISTER_FAILED`
 * `OBJECT_API_DISABLED`
 * `OBJECT_API_METHOD_NOT_ALLOWED`
+* `OPENAPI_UNAVAILABLE`
 * `OS_PROTOCOL_INCOMPATIBLE`
+* `OVERLAY_PERSISTENCE_FAILED`
 * `PACKAGE_DELETE_FAILED`
 * `PACKAGE_DELETE_PARTIAL`
 * `PACKAGE_MANIFEST_INVALID`
@@ -231,6 +259,9 @@ const result = ErrorCode.parse(data);
 * `PAYLOAD_TOO_LARGE`
 * `PERMISSION_NOT_ALLOWED`
 * `PHONE_NOT_ENABLED`
+* `PLUGIN_INSTALL_FAILED`
+* `PLUGIN_MANIFEST_INVALID`
+* `PLUGIN_REGISTER_FAILED`
 * `PROJECT_MEMBERSHIP_REQUIRED`
 * `PROJECT_NOT_FOUND`
 * `PROJECT_PROVISIONING`
@@ -246,13 +277,16 @@ const result = ErrorCode.parse(data);
 * `REPORT_SAVE_FAILED`
 * `REPORT_SCHEDULE_FAILED`
 * `REQUEST_NOT_FOUND`
+* `RESEED_NO_ROWS`
+* `RESEED_SKIPPED`
 * `ROUTE_NOT_FOUND`
 * `RULE_DEFINE_FAILED`
 * `RULE_DELETE_FAILED`
 * `RULE_EVALUATE_FAILED`
 * `RULE_GET_FAILED`
 * `RULE_LIST_FAILED`
 * `RULE_NOT_FOUND`
+* `SAML_REGISTER_FAILED`
 * `SCHEDULES_LIST_FAILED`
 * `SCHEDULE_DELETE_FAILED`
 * `SETTINGS_ACTION_FAILED`
@@ -266,6 +300,7 @@ const result = ErrorCode.parse(data);
 * `SHARE_REVOKE_FAILED`
 * `SHARING_NOT_ENABLED`
 * `SIGN_IN_REQUIRED`
+* `SSO_REGISTER_FAILED`
 * `SSO_REGISTER_FORBIDDEN`
 * `SUGGESTION_CONFIRM_FAILED`
 * `SUGGESTION_DISMISS_FAILED`
@@ -283,6 +318,9 @@ const result = ErrorCode.parse(data);
 * `UPLOAD_SESSION_NOT_FOUND`
 * `USER_ALREADY_EXISTS`
 * `VALIDATION_FAILED`
+* `VERSION_NOT_FOUND`
+* `VERSION_NOT_RESTORABLE`
+* `WRITABLE_PACKAGE_REQUIRED`
 * `WRONG_PASSWORD`