incitaciones 0.11.0 → 0.11.1

package/README.md

@@ -1,5 +1,10 @@
 # Incitaciones 🤖
 
+> **Why:** agent prompts rot — they accumulate metadata sections, stale claims,
+> and untraceable provenance. incitaciones keeps every prompt twice: a full
+> source (frontmatter, tags, status, provenance) and a structurally validated
+> distilled runtime file, gated end-to-end by `just ci`.
+> **Status:** [experimental](docs/src/status.md) · corpus + export tooling evolving · [Motivation & design](docs/src/index.md) · [charly-vibes Tool Ecosystem](https://charly-vibes.github.io/dulce-de-leche/ecosystem-map.html)
 [![npm](https://img.shields.io/npm/v/incitaciones)](https://www.npmjs.com/package/incitaciones)
 [![Publish to npm](https://github.com/charly-vibes/incitaciones/actions/workflows/npm-publish.yml/badge.svg)](https://github.com/charly-vibes/incitaciones/actions/workflows/npm-publish.yml)
 

package/content/distilled/whisper/SKILL.md

@@ -1,37 +1,20 @@
-# Whisper — Deterministic Operational Knowledge
+# Whisper — knowledge workspace (pointer)
 
-> **This skill is a thin pointer.** The canonical, versioned copy ships with
-> the `turu` CLI ([charly-vibes/whisper](https://github.com/charly-vibes/whisper),
-> `cargo install whisper-vibes`) — install it with `turu skill install`.
-> This file stays so agents without the binary have fallbacks.
+The canonical, versioned procedure lives in the **turu skill pack** —
+installed with `turu skill install` and shipped with the `turu` CLI
+([charly-vibes/whisper](https://github.com/charly-vibes/whisper),
+`cargo install whisper-vibes`).
 
-The `turu` CLI owns every mechanical step: canonical repo keys, branch slugs,
-worktree slots, and scope routing. Same inputs, same outputs — no more
-hand-rolled shell pipelines.
+## Routing rule
 
-## Decision procedure
-
-1. **Is `turu` available?** Run `turu key --json`.
-2. **If yes** — everything mechanical is a turu command:
-
-| Intent | Command |
-|---|---|
-| Derive repo key / branch slug / worktree slot | `turu key --json` |
-| Find the write destination for a scope | `turu resolve <scope> --json` |
-| Record knowledge (extend, don't duplicate) | `turu append <scope> --text "..."` |
-| Create the workspace layout | `turu init --json` |
-| Inspect paths and existence | `turu status --json` |
-| Validate / detect legacy keys | `turu check --json` · `turu doctor --json` |
-| Refresh the AGENTS.md routing block | `turu sync --json` |
-
-   Scopes: `global` (rules.md), `repo` (env.md), `branch` (notes.md),
-   `worktree` (env.md), `group` (shared workspace for a set of repos).
-   If a `<!-- TURU:START -->` block exists in `AGENTS.md`, read the routing
-   map from there instead of re-deriving paths.
-
-3. **If no** — use the manual fallbacks in `references/` (they remain the
-   source of truth for the shell-snippet procedures) and suggest
-   `cargo install whisper-vibes`.
+- **If `whisper.md` sits next to this file** (the installed pack), read it and follow it as your single source of procedure. It owns everything: the session loop (`turu recall all`
+at start, `turu append <scope> "..."` at capture), scope routing
+  (global → group → repo → branch → worktree), the command table, and all
+  modes. This pointer defers entirely and adds nothing — never reconcile
+  the two by hand.
+- **If the pack is absent**, `turu` is not installed: use the manual
+  fallbacks in `references/` (source of truth for the shell-snippet
+  procedures) and suggest `cargo install whisper-vibes`.
 
 ## Invariants (with or without the binary)
 
@@ -41,15 +24,4 @@ hand-rolled shell pipelines.
   than creating a new one that says the same thing.
 - **One repo, one key.** The canonical key is a pure function of the remote
   URL; never invent a variant.
-- **Search first.** Before creating a new entry, check if one exists.
-
-## Modes
-
-`/w init` → `turu init` · `/w` or `/w status` → `turu status` ·
-`/w check` → `turu check` · `/w link` → `subs/link-manual` (no CLI verb yet)
-· `/w decommission` → `subs/decommission-manual` · `/w consolidate` →
-`subs/consolidate-manual` (detection ships via `turu doctor`).
-
-Manual procedures for each mode: `references/init.md`, `references/check.md`,
-`references/status.md`, `references/link.md`, `references/decommission.md`,
-`references/consolidate.md`.
+- **Search first.** Before creating a new entry, check if one exists.

package/content/manifest.json

@@ -1465,7 +1465,7 @@
       "name": "whisper",
       "type": "workflow",
       "title": "Whisper — Accumulated Operational Knowledge",
-      "description": "Knowledge workspace management: init, check, status, link plan, decommission, routing. Delegates to the turu CLI when installed.",
+      "description": "Deterministic knowledge workspace: session loop (recall all / append), scope routing, distill, bundle. Delegates to the turu CLI when installed; manual fallbacks otherwise.",
       "source": "content/prompt-workflow-whisper.md",
       "distilled": "content/distilled/whisper/SKILL.md",
       "skill_format": "progressive-disclosure",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "incitaciones",
-  "version": "0.11.0",
+  "version": "0.11.1",
   "description": "Reusable prompts and skills for CLI LLM tools, with native pi package support.",
   "repository": {
     "type": "git",

package/pi-package/prompts/whisper.md

@@ -1,5 +1,5 @@
 ---
-description: "Shortcut for the whisper skill. Knowledge workspace management: init, check, status, link plan, decommission, routing. Delegates to the turu CLI when installed."
+description: "Shortcut for the whisper skill. Deterministic knowledge workspace: session loop (recall all / append), scope routing, distill, bundle. Delegates to the turu CLI when installed; manual fallbacks otherwise."
 ---
 <!-- installed-from: incitaciones -->
 

package/pi-package/skills/whisper/SKILL.md

@@ -1,44 +1,27 @@
 ---
 name: whisper
-description: "Knowledge workspace management: init, check, status, link plan, decommission, routing. Delegates to the turu CLI when installed."
+description: "Deterministic knowledge workspace: session loop (recall all / append), scope routing, distill, bundle. Delegates to the turu CLI when installed; manual fallbacks otherwise."
 metadata:
   installed-from: "incitaciones"
 disable-model-invocation: true
 ---
-# Whisper — Deterministic Operational Knowledge
+# Whisper — knowledge workspace (pointer)
 
-> **This skill is a thin pointer.** The canonical, versioned copy ships with
-> the `turu` CLI ([charly-vibes/whisper](https://github.com/charly-vibes/whisper),
-> `cargo install whisper-vibes`) — install it with `turu skill install`.
-> This file stays so agents without the binary have fallbacks.
+The canonical, versioned procedure lives in the **turu skill pack** —
+installed with `turu skill install` and shipped with the `turu` CLI
+([charly-vibes/whisper](https://github.com/charly-vibes/whisper),
+`cargo install whisper-vibes`).
 
-The `turu` CLI owns every mechanical step: canonical repo keys, branch slugs,
-worktree slots, and scope routing. Same inputs, same outputs — no more
-hand-rolled shell pipelines.
+## Routing rule
 
-## Decision procedure
-
-1. **Is `turu` available?** Run `turu key --json`.
-2. **If yes** — everything mechanical is a turu command:
-
-| Intent | Command |
-|---|---|
-| Derive repo key / branch slug / worktree slot | `turu key --json` |
-| Find the write destination for a scope | `turu resolve <scope> --json` |
-| Record knowledge (extend, don't duplicate) | `turu append <scope> --text "..."` |
-| Create the workspace layout | `turu init --json` |
-| Inspect paths and existence | `turu status --json` |
-| Validate / detect legacy keys | `turu check --json` · `turu doctor --json` |
-| Refresh the AGENTS.md routing block | `turu sync --json` |
-
-   Scopes: `global` (rules.md), `repo` (env.md), `branch` (notes.md),
-   `worktree` (env.md), `group` (shared workspace for a set of repos).
-   If a `<!-- TURU:START -->` block exists in `AGENTS.md`, read the routing
-   map from there instead of re-deriving paths.
-
-3. **If no** — use the manual fallbacks in `references/` (they remain the
-   source of truth for the shell-snippet procedures) and suggest
-   `cargo install whisper-vibes`.
+- **If `whisper.md` sits next to this file** (the installed pack), read it and follow it as your single source of procedure. It owns everything: the session loop (`turu recall all`
+at start, `turu append <scope> "..."` at capture), scope routing
+  (global → group → repo → branch → worktree), the command table, and all
+  modes. This pointer defers entirely and adds nothing — never reconcile
+  the two by hand.
+- **If the pack is absent**, `turu` is not installed: use the manual
+  fallbacks in `references/` (source of truth for the shell-snippet
+  procedures) and suggest `cargo install whisper-vibes`.
 
 ## Invariants (with or without the binary)
 
@@ -48,15 +31,4 @@ hand-rolled shell pipelines.
   than creating a new one that says the same thing.
 - **One repo, one key.** The canonical key is a pure function of the remote
   URL; never invent a variant.
-- **Search first.** Before creating a new entry, check if one exists.
-
-## Modes
-
-`/w init` → `turu init` · `/w` or `/w status` → `turu status` ·
-`/w check` → `turu check` · `/w link` → `subs/link-manual` (no CLI verb yet)
-· `/w decommission` → `subs/decommission-manual` · `/w consolidate` →
-`subs/consolidate-manual` (detection ships via `turu doctor`).
-
-Manual procedures for each mode: `references/init.md`, `references/check.md`,
-`references/status.md`, `references/link.md`, `references/decommission.md`,
-`references/consolidate.md`.
+- **Search first.** Before creating a new entry, check if one exists.