@sous-io/sous 0.2.31 → 0.2.32

package/docs/markdown/_sidebar.md

@@ -30,3 +30,4 @@
   - [0009: One whole build, everywhere](adrs/0009-whole-build-everywhere.md)
   - [0010: The index describes each version's dependencies and questions](adrs/0010-index-describes-recipes.md)
   - [0011: `sous update` updates sous through the package managers](adrs/0011-self-update.md)
+  - [0012: Recipes do not install Sous plugins](adrs/0012-recipes-and-plugins.md)

package/docs/markdown/repositories-file-formats.md

@@ -80,9 +80,9 @@ contents:                           # what a subscriber actually receives
 | `contents`, `variables` | no | Contents default to an empty list, which is what a curated bundle publishes; a duplicated variable name, or two definitions claiming one `env`, is an error |
 | `submissions` | no | Whether this recipe takes proposed changes, winning over the repository's block; see [The submissions block](#the-submissions-block) |
 
-`contents[].kind` is `skills`, `memories`, `prompts` or `config`. The first three are written to the
-destinations named by [`recipeOutputs`](#recipeoutputs-where-the-files-land); `config` entries become config
-layers instead. `include` needs at least one glob, and both lists are recipe-relative.
+`contents[].kind` is `skills`, `memories`, `prompts` or `config`; there is no kind for a sous plugin. The
+first three are written to the destinations named by [`recipeOutputs`](#recipeoutputs-where-the-files-land);
+`config` entries become config layers instead. `include` needs at least one glob, and both lists are recipe-relative.
 
 ### The submissions block
 

package/docs/markdown/repositories.md

@@ -47,7 +47,8 @@ $ sous namespace list
 
 A recipe is the unit you subscribe to and the only thing that carries a version. It may hold
 skills, memories, prompts, config layers and variable definitions in any mixture, and
-subscribing to it gets all of them.
+subscribing to it gets all of them. A recipe may ship a plugin for a coding tool (a Claude Code
+plugin, say), but never a plugin for sous itself; those come only with sous or as npm packages.
 
 ```yaml
 # recipes/workflow/task-files/sous.recipe.yaml
@@ -193,10 +194,10 @@ this machine.
 Subscribing decides what is switched on, and it is not a second security gate. A recipe is
 **active** when the project subscribes to it directly or through its namespace, or when an active
 recipe lists it under `subscribes`; only an active recipe registers entry points of its own, such as
-output files, skills and hooks. A recipe held only through `depends` is a library: an active recipe
-may include, call or import its files, but it registers nothing itself. Activation keeps a project
-from running what it has no use for and keeps unrelated recipes from colliding; everything in a
-trusted repository is already trusted.
+output files, skills, tool hooks and tool plugins. A recipe held only through `depends` is a library:
+an active recipe may include, call or import its files, but it registers nothing itself. Activation
+keeps a project from running what it has no use for and keeps unrelated recipes from colliding;
+everything in a trusted repository is already trusted.
 
 ## The official repository, and the built-in core
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sous-io/sous",
-  "version": "0.2.31",
+  "version": "0.2.32",
   "description": "Compiles AI coding agent configuration (CLAUDE.md, skills, memories) from LiquidJS templates",
   "type": "module",
   "license": "Apache-2.0",

package/recipes/core/sous-skills/skills/about-liquid-templates/SKILL.tpl.md

@@ -188,6 +188,13 @@ wins**; if none exist, the build errors listing every path tried:
 
 ## Custom Tags
 
+The tags below are built into sous. A recipe cannot add a tag or a filter, since that would be a
+Sous plugin; a Sous plugin comes only from sous's built-ins or an npm-style module.
+
+> "recipes will not be allowed to install _Sous_ plugins. All Sous plugins, besides any built-ins that ship with Sous, itself, will come from a NPM repo (or similar) as modules. Recipes _will_ be allowed to install tool plugins (e.g. Claude Code Plugins)."
+>
+>   -- **Luke Chavers** in an agent session (2026-09-29)
+
 **`showVars`**: dumps all variables currently in scope as a fenced JSON block.
 Useful during development to see exactly what variables are available at a given point
 in a template. Remove before finalizing.

package/recipes/core/sous-skills/skills/about-sous/SKILL.tpl.md

@@ -65,8 +65,14 @@ trust question reads only its index.
 Subscribing decides what is switched on, not what is safe. A recipe is active when the
 project subscribes to it, directly or through its namespace, or when an active recipe
 lists it under `subscribes`, and only an active recipe registers entry points of its own
-(output files, skills, hooks). A recipe held only through `depends` is a library: an active
-recipe may include, call or import its files, but it registers nothing itself.
+(output files, skills, tool hooks and tool plugins). A recipe held only through `depends` is a
+library: an active recipe may include, call or import its files, but it registers nothing
+itself. No recipe installs a Sous plugin; Sous plugins come only from sous's built-ins and from
+npm-style modules.
+
+> "recipes will not be allowed to install _Sous_ plugins. All Sous plugins, besides any built-ins that ship with Sous, itself, will come from a NPM repo (or similar) as modules. Recipes _will_ be allowed to install tool plugins (e.g. Claude Code Plugins)."
+>
+>   -- **Luke Chavers** in an agent session (2026-09-29)
 
 ## Sous's Own Documentation
 

package/recipes/core/sous-skills/skills/about-sous-recipes/SKILL.tpl.md

@@ -54,6 +54,14 @@ The fields in that example:
   it MUST be `.json`, `.jsonc`, `.yaml` or `.yml`, and every key outside `_aliases`, `_vars`,
   `compilation`, `recipeOutputs`, `runtimeContext`, `store` and `varMappings` is dropped with a
   warning. A recipe that only bundles others may leave `contents` out.
+- A recipe MAY install tool plugins (a plugin for a coding agent tool, such as a Claude Code
+  plugin) and MUST NOT install a Sous plugin (one that extends sous itself). Sous plugins come only
+  from the built-ins that ship with sous and from npm-style modules. A `config` file is
+  configuration, not a Sous plugin.
+
+  > "recipes will not be allowed to install _Sous_ plugins. All Sous plugins, besides any built-ins that ship with Sous, itself, will come from a NPM repo (or similar) as modules. Recipes _will_ be allowed to install tool plugins (e.g. Claude Code Plugins)."
+  >
+  >   -- **Luke Chavers** in an agent session (2026-09-29)
 - `depends`, `subscribes` and `variables` are described below; `submissions` is in
   `about-sous-repos`.
 

package/recipes/core/sous-skills/sous.recipe.yaml

@@ -11,7 +11,7 @@ formatVersion: 1
 
 namespace: core
 name: sous-skills
-version: 0.2.31
+version: 0.2.32
 
 description: >-
   The skills that teach an agent what sous is and how it works: which files sous