@theholocron/cli 5.0.0-alpha.187 → 5.0.0-alpha.188

package/dist/plugin/capabilities.d.mts

@@ -740,6 +740,8 @@ interface Tooling extends ProviderIdentity {
 interface EnsuredResource {
   id: string;
   created: boolean;
+  /** For something that already existed: the settings that disagreed with the layout and were changed. */
+  updated?: string[];
 }
 /** A webhook (or equivalent inbound URL) for a channel. */
 interface EnsureWebhookResult {
@@ -774,6 +776,15 @@ interface NotificationsLayout {
   roles?: Array<{
     name: string;
     mentionable?: boolean;
+    /** `#rrggbb`. Omit to leave the colour alone. */
+    color?: string;
+    /** Show the role's members as their own group in the member list. */
+    hoist?: boolean;
+    /**
+     * The permissions the role holds, by the provider's own names (for Discord, `ViewChannel`,
+     * `SendMessages`, …). The list is exact: a permission not named is not granted.
+     */
+    permissions?: string[];
     /**
      * Store the role's id in this secret, so a workflow can ping the role
      * without anyone copying the id by hand. The id is not sensitive; a secret
@@ -785,7 +796,7 @@ interface NotificationsLayout {
 }
 /**
  * What a provider found on the server, limited to what a {@link NotificationsLayout}
- * asks about. Read-only: this is what `holocron notifications verify` compares the
+ * asks about. Read-only: this is what `holocron doctor notifications` compares the
  * layout against.
  */
 interface ServerInspection {
@@ -804,6 +815,10 @@ interface ServerInspection {
     name: string;
     id: string;
     mentionable: boolean;
+    /** `#rrggbb`, or absent for the default colour. */
+    color?: string;
+    hoist?: boolean;
+    permissions?: string[];
   }>;
   /** Set when reading the roles failed; `roles` is then empty and means nothing. Not read at all when the layout declares none. */
   rolesError?: string;
@@ -839,7 +854,16 @@ interface Notifications extends ProviderIdentity {
   ensureRole?(input: {
     name: string;
     mentionable?: boolean;
+    color?: string;
+    hoist?: boolean;
+    permissions?: string[];
   }): Promise<EnsuredResource>;
+  /**
+   * Check the provider-specific parts of the layout (colours, permission names, …) without
+   * touching the server, so `setup` can refuse a bad layout before it creates anything.
+   * Returns the first problem, or `undefined` when the layout is fine.
+   */
+  validateLayout?(layout: NotificationsLayout): string | undefined;
   /**
    * Smoke check for `holocron doctor`: prove the provisioning credentials work
    * and name what they reach. Returns `null` when there is nothing to check (a
@@ -852,7 +876,7 @@ interface Notifications extends ProviderIdentity {
   } | null>;
   /**
    * Read what exists on the server, for the parts the layout cares about, without
-   * changing anything. Backs `holocron notifications verify`.
+   * changing anything. Backs `holocron doctor notifications`.
    */
   inspect?(layout: NotificationsLayout): Promise<ServerInspection>;
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@theholocron/cli",
-  "version": "5.0.0-alpha.187",
+  "version": "5.0.0-alpha.188",
   "description": "The Holocron CLI - a pluggable, capability-based orchestrator for spinning up and operating software projects.",
   "keywords": [
     "cli",
@@ -63,8 +63,8 @@
     "pino-pretty": "^13.1.3",
     "posthog-node": "^5.51.6",
     "yargs": "^18.1.0",
-    "@theholocron/astromech": "5.0.0-alpha.187",
-    "@theholocron/datapad": "5.0.0-alpha.187"
+    "@theholocron/astromech": "5.0.0-alpha.188",
+    "@theholocron/datapad": "5.0.0-alpha.188"
   },
   "devDependencies": {
     "@theholocron/eslint-config": "^8.8.2",