@openbrf/plugin-sdk 1.0.0 → 1.4.0

package/src/findings.ts

@@ -45,6 +45,24 @@ export const PLUGIN_FINDING_REASONS = [
   "actions-widened",
   /** An action the manifest declares could not be registered. */
   "action-refused",
+  /**
+   * The installed version says otherwise than the board consented to about
+   * whether it is an AI package, in either direction.
+   */
+  "ai-changed",
+  /**
+   * The installed version reads another entitlement than the board consented
+   * to, may present the licence to a service the board was not told of, or
+   * declares a key of its issuer's the board has not consented to.
+   */
+  "licence-widened",
+  /**
+   * The installed version names another issuer of its licence than the board
+   * consented to, or no longer declares a key the board consented to.
+   */
+  "licence-issuer-changed",
+  /** It registered a website block its manifest does not declare. */
+  "block-refused",
   /** One of its providers reaches for a core service a plugin may not hold. */
   "forbidden-injection",
   /**
@@ -53,6 +71,54 @@ export const PLUGIN_FINDING_REASONS = [
    * audience every issued token carries, so moving it would strand them all.
    */
   "oauth-resource-conflict",
+  /**
+   * A plugin it extends is not installed, not loaded, or switched off. The
+   * detail names it. An addon does not serve while its host plugin does not.
+   */
+  "extension-host-missing",
+  /** A plugin it extends declares no such extension point. */
+  "extension-point-unknown",
+  /**
+   * A point it extends is at another major version than the one it was
+   * written for.
+   */
+  "extension-version-unsupported",
+  /** It hands over a category of personal data the point does not accept. */
+  "extension-personal-data-refused",
+  /**
+   * Of it and a plugin it extends, one puts blocks on the website and the
+   * other holds a permission that reads the register. The detail names
+   * those permissions.
+   */
+  "extension-permission-refused",
+  /**
+   * It puts blocks on the website, and a plugin it extends handles personal
+   * data. The detail names those categories.
+   */
+  "extension-host-personal-data-refused",
+  /**
+   * The plugins joined to it by extensions, through one host plugin or
+   * several, hold one that puts blocks on the website and one that reads the
+   * address book. The detail names both.
+   */
+  "extension-group-refused",
+  /**
+   * It declares an extension point, or extends one, in a way the board has not
+   * consented to.
+   */
+  "extensions-widened",
+  /** A definition or contribution it registered could not be accepted. */
+  "extension-refused",
+  /**
+   * The installed version declares a recipient the board did not consent to:
+   * a new one, one at another origin, or one receiving more personal data.
+   */
+  "recipients-widened",
+  /**
+   * The installed version declares a device route the board has not consented
+   * to, or moves one (ADR 0031).
+   */
+  "device-routes-widened",
 ] as const;
 
 export type PluginFindingReason = (typeof PLUGIN_FINDING_REASONS)[number];
@@ -69,3 +135,31 @@ export type PluginFindingReason = (typeof PLUGIN_FINDING_REASONS)[number];
 export type PluginFindingDetail = Readonly<
   Record<string, string | number | readonly string[]>
 >;
+
+/**
+ * The manifest rules whose refusal a board reads in its own language.
+ *
+ * A manifest that fails validation is reported as `manifest-invalid`, and
+ * what Zod says about a field is English for the plugin's author. The rules
+ * below are not about one field: they hold two declarations against each
+ * other, and a board reading why a package was skipped needs to be told which
+ * in a sentence of its own. So the refusal carries the code with the English
+ * line, and the interface translates the code. Any other problem stays the
+ * English line, which is what an author fixes the package from.
+ */
+export const PLUGIN_MANIFEST_RULES = [
+  /** A device route overlaps the OAuth protected resource. */
+  "device-route-overlaps-oauth-resource",
+  /** A plugin with a device route also reads the register or the finances. */
+  "device-route-reads-register",
+  /** A plugin with a website block also reads the register or the finances. */
+  "blocks-read-register",
+  /** A plugin with a device route also proposes imports. */
+  "device-route-proposes-import",
+  /** A plugin with a website block also proposes imports. */
+  "blocks-propose-import",
+  /** A plugin with a device route offers an extension point accepting contact details. */
+  "device-route-extension-point-contact",
+] as const;
+
+export type PluginManifestRule = (typeof PLUGIN_MANIFEST_RULES)[number];