@damiangilgonzalez/harness 1.3.17 → 1.3.19

package/manifest.json

@@ -1,5 +1,5 @@
 {
-  "version": "1.3.17",
+  "version": "1.3.19",
   "counts": {
     "skills": 294,
     "agents": 34,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@damiangilgonzalez/harness",
-  "version": "1.3.17",
+  "version": "1.3.19",
   "description": "A guided harness builder that turns your goal into a minimal, verified AI-agent setup using strict best practices.",
   "type": "module",
   "bin": {

package/scripts/doctor.js

@@ -261,7 +261,7 @@ export function doctor({ target, home, cwd }) {
   // #277 — the three "missing" lists share one shape, { id, path, action }, so whoever builds on top
   // of doctor reads them the same way; and `healthy` is what the exit code says.
   for (const [id, e] of Object.entries(state.skills)) {
-    for (const f of e.files) if (!existsSync(f)) report.missing.push({ id, path: f, action: 'Run `npx @ericrisco/rsc sync` to restore this managed skill.' });
+    for (const f of e.files) if (!existsSync(f)) report.missing.push({ id, path: f, action: 'Run `npx @damiangilgonzalez/harness sync` to restore this managed skill.' });
   }
   report.healthy = report.hookWired && !report.missing.length && !missingAgents.length && !missingCommands.length;
   return report;

package/scripts/install-apply.js

@@ -21,6 +21,7 @@ import {
 import {
   wireMemory, unwireMemory, memoryManagedPaths, memoryModeFor, memoryEnabledForProject, memoryArtifactsPresent,
 } from '../targets/memory.js';
+import { wireKnowledge, unwireKnowledge, knowledgeManagedPaths, knowledgeArtifactsPresent } from '../targets/knowledge-wiring.js';
 
 const ROOT = join(dirname(fileURLToPath(import.meta.url)), '..');
 const CLI_VERSION = JSON.parse(readFileSync(join(ROOT, 'package.json'), 'utf8')).version;
@@ -94,6 +95,7 @@ export function managedPathsForInstall({ skillIds, agentIds = [], target, home,
   const out = [paths.stateFile, versionFile(cwd), baseVersionsFile(cwd)];
   if (policy?.context7 === false) out.push(join(cwd, '.rsc', '.no-context7'));
   if (policy?.memory !== false) out.push(...memoryManagedPaths(target, cwd));
+  out.push(...knowledgeManagedPaths(target, cwd));
   if (targetHasAgents(target)) {
     const state = readState(paths.stateFile);
     const explicit = [...new Set([...(state.explicitAgents || readManifest(cwd)?.agents || []), ...agentIds])];
@@ -273,6 +275,10 @@ export async function applyInstall({ skillIds = [], agentIds = [], target, home,
     ? { mode: 'disabled', reason: 'onboarding-policy', paths: unwireMemory(target, cwd) }
     : wireMemory(target, cwd);
   state.memory = { mode: memoryResult.mode, reason: memoryResult.reason, paths: memoryResult.paths };
+  // Knowledge sync is its own decision (`.no-knowledge-sync`, checked at runtime) and never part of
+  // the memory, so the memory's policy does not decide it: wired wherever the assistant can run it.
+  const knowledgeResult = wireKnowledge(target, cwd);
+  state.knowledge = { mode: knowledgeResult.mode, reason: knowledgeResult.reason || null, paths: knowledgeResult.paths };
   const context7OptOut = join(cwd, '.rsc', '.no-context7');
   if (policy?.context7 === false) {
     mkdirSync(dirname(context7OptOut), { recursive: true });
@@ -587,6 +593,7 @@ export function removeTargetInstall({ target, home, cwd = process.cwd() }) {
   }
   unwireHook(target, paths);
   unwireMemory(target, cwd);
+  unwireKnowledge(target, cwd);
   rmSync(paths.stateFile, { force: true });
   const gitignore = join(cwd, '.gitignore');
   if (existsSync(gitignore)) {
@@ -731,8 +738,10 @@ export async function purge({ home, cwd = process.cwd(), withDocs = false, dryRu
     if (!dryRun) {
       removed.push(...unwireHook(target, paths));
       removed.push(...unwireMemory(target, cwd));
+      removed.push(...unwireKnowledge(target, cwd));
     } else {
       removed.push(...memoryArtifactsPresent(target, cwd));
+      removed.push(...knowledgeArtifactsPresent(target, cwd));
     }
     // A lost state file also loses proof of ownership. Leave same-named user files
     // behind rather than guessing from a catalog id and deleting their work.

package/scripts/rsc.js

@@ -41,7 +41,7 @@ if (['--version', '-v', 'version'].includes(rawArgv[0])) {
 const GLOBAL_VALUE_FLAGS = new Set([
   '--target', '--technical-level', '--accompaniment', '--project-kind', '--goal', '--goal-base64', '--software-scope', '--accept-plan',
 ]);
-const COMMANDS = new Set(['onboard', 'reassess', 'add', 'install', 'consult', 'catalog', 'audit', 'list', 'doctor', 'memory', 'sync', 'backups', 'restore', 'upgrade', 'registry', 'worktrees', 'capabilities', 'review', 'sello', 'repair', 'uninstall', 'purge']);
+const COMMANDS = new Set(['onboard', 'reassess', 'add', 'install', 'consult', 'catalog', 'audit', 'list', 'doctor', 'memory', 'knowledge-sync', 'sync', 'backups', 'restore', 'upgrade', 'registry', 'worktrees', 'capabilities', 'review', 'sello', 'repair', 'uninstall', 'purge']);
 function positionalTokens(input) {
   const out = [];
   for (let i = 0; i < input.length; i++) {
@@ -756,6 +756,32 @@ async function main() {
       printContextBudget(report.contextBudget);
       return void say(JSON.stringify({ ...report, contextBudget: undefined }, null, 2));
     }
+    case 'knowledge-sync': {
+      // On by default; the switch is a PROJECT decision (`.no-knowledge-sync`, recorded in `.rsc.json`
+      // optOuts by the sync below), because one person off means the team stops seeing their work.
+      const sub = argv[1] || 'status';
+      const root = process.cwd();
+      const { mkdirSync, writeFileSync, rmSync } = await import('node:fs');
+      const { join } = await import('node:path');
+      const marker = join(root, '.rsc', '.no-knowledge-sync');
+      if (sub === 'on' || sub === 'off') {
+        mkdirSync(join(root, '.rsc'), { recursive: true });
+        if (sub === 'off') writeFileSync(marker, '');
+        else rmSync(marker, { force: true });
+        for (const t of targets) await syncInstalled({ target: t, cwd: root });
+        say(sub === 'off'
+          ? 'rsc knowledge-sync off: 01-TOOLS/ and docs/ no longer sync on their own in this project. Commit .rsc.json so the team gets the same decision.'
+          : 'rsc knowledge-sync on: 01-TOOLS/ and docs/ go up when a turn ends and come down before each message. Commit .rsc.json so the team gets the same decision.');
+        return;
+      }
+      if (sub === 'status') {
+        const { knowledgeStatus } = await import('../targets/knowledge-sync.mjs');
+        return void say(JSON.stringify(knowledgeStatus(root), null, 2));
+      }
+      say('Use: npx @damiangilgonzalez/harness@latest knowledge-sync on|off|status');
+      process.exitCode = 2;
+      return;
+    }
     case 'memory': {
       const sub = argv[1] || 'status';
       const root = process.cwd();
@@ -885,11 +911,72 @@ async function main() {
       const root = W.resolveMainRoot(process.cwd());
       const sub = argv[1];
 
+      if (sub === 'new') {
+        // Creating is not cleaning, so the cleanup opt-out does not apply here. Two things a worktree
+        // was measured lacking when it is born: a current base (local main was 400 commits behind
+        // origin) and what git does not track (.env, dependencies). The base is fixed here; the rest
+        // is the project's own hook, because only the project knows what makes it runnable.
+        const branchAt = argv.indexOf('--branch');
+        const branch = branchAt >= 0 ? argv[branchAt + 1] : undefined;
+        if (branchAt >= 0 && (!branch || branch.startsWith('--'))) { say('rsc: --branch needs a branch name.'); process.exitCode = 1; return; }
+        const name = argv.slice(2).find((a, i, all) => !a.startsWith('--') && all[i - 1] !== '--branch');
+        if (!name) { say('Use: npx @damiangilgonzalez/harness worktrees new <nombre> [--branch <rama>]'); process.exitCode = 1; return; }
+        const out = W.createWorktree(root, name, { branch });
+        if (!out.created) { say(`rsc: ${out.reason}`); process.exitCode = 1; return; }
+        if (!out.fetched) say(`⚠️  git fetch origin failed (${out.fetchError || 'no detail'}); starting from the last known ${out.base}, which may be stale.`);
+        say(`✅ worktree ${out.path}`);
+        say(`   branch ${out.branch}, from ${out.base}`);
+        const hook = W.findPrepareHook(out.path, root);
+        if (hook) {
+          say(`   preparing it: ${hook}`);
+          const ran = W.runPrepareHook(hook, out.path, root);
+          if (!ran.ok) { say(`⚠️  the preparation hook failed (${ran.reason}). The worktree exists; finish preparing it by hand.`); process.exitCode = 1; }
+        } else {
+          say(`   No preparation hook (${W.PREPARE_HOOKS.join(' or ')}): .env files and dependencies are NOT copied — create the hook to do it on every new worktree.`);
+        }
+        say(`Next: cd "${out.path}"`);
+        return;
+      }
+
       if (!W.isCleanupEnabled(root)) {
         say(`worktree cleanup is off for this project (.rsc/${W.OPT_OUT}). Delete that file to turn it back on.`);
         return;
       }
 
+      if (sub === 'reap' && argv.includes('--merged')) {
+        // The bulk answer to "delete the worktrees" — asked four times in one project, with up to
+        // fourteen open. Merged is judged against origin's trunk AFTER a fetch, so a branch landed in
+        // the forge an hour ago counts. Without --confirm this only lists: one look, then one yes.
+        const fetched = W.fetchOrigin(root);
+        if (!fetched.ok) say(`⚠️  git fetch origin failed (${fetched.err || 'no detail'}); judging against the last known trunk.`);
+        const all = W.classifyWorktrees(root);
+        const merged = W.mergedCandidates(all);
+        const held = all.filter((c) => c.verdict === 'ask' && !merged.includes(c));
+        if (!merged.length) say('No merged worktree that can be removed in bulk.');
+        if (!argv.includes('--confirm')) {
+          if (merged.length) {
+            say(`${merged.length} merged worktree(s), clean, removable in one go:`);
+            for (const c of merged) say(`  ${c.path}${c.branch ? ` (${c.branch})` : ''}`);
+          }
+          for (const c of held) say(W.describe(c));
+          if (merged.length) say('\nRemove them all:  npx @damiangilgonzalez/harness worktrees reap --merged --confirm');
+          return;
+        }
+        for (const c of merged) {
+          const out = W.reapWorktree(root, c.path, { confirmed: true });
+          if (out.removed) {
+            say(`✅ removed ${out.path}`);
+            if (out.branchKept) say(`   branch ${out.branch} kept — git will not delete it safely, and while it exists the commits are recoverable.`);
+          } else {
+            say(`⏸  kept ${c.path} — ${out.reason}`);
+            process.exitCode = 1;
+          }
+        }
+        // What a bulk yes never covers, said out loud so nobody thinks it was forgotten.
+        for (const c of held) say(`⏸  kept ${c.path} — ${W.refusal(c)}`);
+        return;
+      }
+
       const candidates = W.classifyWorktrees(root).filter((c) => c.verdict !== 'skip');
 
       if (sub === 'reap') {
@@ -920,6 +1007,7 @@ async function main() {
       say('');
       say('Remove the safe ones:  npx @damiangilgonzalez/harness worktrees reap');
       say('Remove one by name:    npx @damiangilgonzalez/harness worktrees reap <path> [--confirm]');
+      say('Remove every merged:   npx @damiangilgonzalez/harness worktrees reap --merged [--confirm]');
       return;
     }
     case 'capabilities': {
@@ -1195,7 +1283,7 @@ async function main() {
       return void (await runPurge(argv.includes('--dry-run'), argv.includes('--with-docs')));
     default:
       say(`rsc: unknown command '${cmd}'.`);
-      say('Use: npx @damiangilgonzalez/harness onboard | reassess | add <id...> | install --profile <p> | consult "<text>" | list | capabilities [--full|gap-log] | audit | registry refresh | doctor | sync | memory <on|off|status|save|resume|learn|metrics> | sello <on|off|status|…> | worktrees [reap [path] [--confirm]] | backups | restore <id|latest> | upgrade | repair | uninstall <id> | purge');
+      say('Use: npx @damiangilgonzalez/harness onboard | reassess | add <id...> | install --profile <p> | consult "<text>" | list | capabilities [--full|gap-log] | audit | registry refresh | doctor | sync | memory <on|off|status|save|resume|learn|metrics> | sello <on|off|status|…> | worktrees [new <nombre> [--branch <rama>] | reap [path|--merged] [--confirm]] | backups | restore <id|latest> | upgrade | repair | uninstall <id> | purge');
       say('Any command takes --target <claude|codex|cursor|copilot|gemini|…> (comma-separate for several)');
       say('   → without it, rsc uses the assistant already installed here; if two are, it asks instead of guessing.');
       process.exitCode = 1;

package/skills/building-agents/SKILL.md

@@ -14,7 +14,7 @@ A thin provider adapter, a disciplined agent loop, schema-validated tools, provi
 
 > Program against a **capability interface**, never a vendor SDK. Vendor specifics (model id, tool-schema shape, JSON mode, caching, token limits) live behind one adapter resolved from config. Model names and prices rot — if one appears in business logic it's a bug, and re-verify the dated tables before quoting a number.
 
-**Hand off instead when:** a new non-trivial feature has no approved spec + plan under `docs/wiki/sdd/` → stop and write one first (the `to-spec` skill, or `superpowers:writing-plans`), which routes back here once the plan is approved; one-line/low-risk changes go straight through. Anthropic-SDK internals (caching, thinking, batch) in a file that *only* imports `anthropic` → `claude-api` if your environment has it, since this skill stays multi-provider. Workspace scaffolding → [`harness`](../harness/SKILL.md). Choosing *which* coding agent to use → agent-eval territory. Pure prompt-wording tuning with no architecture change → prompt engineering, not this. A one-shot throwaway prompt, or no retrieval/tools/loop/evals at all → you don't need an agent; call the SDK directly and say so.
+**Hand off instead when:** a new non-trivial feature has no approved spec + plan under `docs/wiki/sdd/` → stop and write one first (the `to-spec` skill, then `to-tickets`), which routes back here once the plan is approved; one-line/low-risk changes go straight through. Anthropic-SDK internals (caching, thinking, batch) in a file that *only* imports `anthropic` → `claude-api` if your environment has it, since this skill stays multi-provider. Workspace scaffolding → [`harness`](../harness/SKILL.md). Choosing *which* coding agent to use → agent-eval territory. Pure prompt-wording tuning with no architecture change → prompt engineering, not this. A one-shot throwaway prompt, or no retrieval/tools/loop/evals at all → you don't need an agent; call the SDK directly and say so.
 
 ## Decision rules (read before writing code)
 

package/skills/grill-with-docs/SKILL.md

@@ -2,7 +2,6 @@
 name: grill-with-docs
 description: "A relentless interrogation to sharpen a plan or design, which also builds documentation (ADRs and a glossary) along the way."
 tags: ["planning", "questioning", "documentation", "adr"]
-disable-model-invocation: true
 profiles: [core, ui, full]
 origin: damiangil
 ---

package/skills/harness/references/daily-curation-automation.md

@@ -42,7 +42,8 @@ process inbox/, then scan the workspace (minus .rscignore) for un-ingested docum
 applying Clean-as-you-go (move loose root-level + inbox files into raw/ after a
 verified ingest; copy files nested in user-maintained folders and propose
 consolidation), record them in wiki/.ingested.json, and list ambiguous folders as
-proposals (do not grab them). Then compile pending raw/worklog/ material into wiki/
+proposals (do not grab them). Then compile pending raw/worklog/ material (skip this
+step if raw/worklog/ does not exist; do not list a missing folder) into wiki/
 pages (update existing before creating new), keep frontmatter + relative markdown
 links OKF-consistent, append significant decisions to wiki/harness/decisions.md,
 refresh the .base-backed navigation, recompute scores.json + the score: property,

package/skills/harness/references/wiki-protocol.md

@@ -417,7 +417,9 @@ safety rule the curation pass honors.
 ### Steps
 
 1. **Capture.** Write the worklog to `raw/worklog/YYYY-MM-DD-<slug>.md`
-   (`status: unprocessed`). Infer `topic` from content.
+   (`status: unprocessed`). Infer `topic` from content. If `raw/worklog/` does
+   not exist yet, create it (`mkdir -p`) — never list it blindly: the checkpoint
+   hook already says whether it exists and how many worklogs it holds.
 2. **Compile.** Run the normal Compile (Fetch is a no-op — the worklog is already
    `raw`): distill durable points into `wiki/<topic>/` articles (update existing
    before creating new), add markdown-link cross-refs + `## Related`, cascade.

package/skills/implement/SKILL.md

@@ -2,7 +2,6 @@
 name: implement
 description: "Implements a piece of work from a spec or a set of tickets."
 tags: ["implementation", "spec", "tickets"]
-disable-model-invocation: true
 profiles: [core, ui, full]
 origin: damiangil
 ---

package/skills/implement-spec/SKILL.md

@@ -2,12 +2,11 @@
 name: implement-spec
 description: "Implement the result of /to-spec and /to-tickets in code, orchestrating parallel implementer subagents over the ticket graph."
 tags: ["implementation", "spec", "tickets", "subagents", "orchestration"]
-disable-model-invocation: true
 profiles: [core, ui, full]
 origin: damiangil
 ---
 
-Te han dado una spec. Esa spec debería tener tickets asociados que describen cómo implementarla.
+Te han dado una spec. Esa spec debería tener tickets asociados que describen cómo implementarla. Si no los tiene, **para**: lanza `to-tickets` sobre la spec y vuelve aquí con el grafo ya publicado. Sin tickets no hay frontera que repartir, y esto se convierte en una implementación a ciegas.
 
 El issue tracker debería estar descrito en `docs/agents/issue-tracker.md`. Si falta, pregunta al usuario dónde viven los tickets y cómo se cierra el trabajo (PR, issue, fichero).
 

package/skills/init/SKILL.md

@@ -165,11 +165,13 @@ means the user starts clean.
    machine and flags overlap or skills with no footprint, so the project starts with the right set
    rather than a pile. Summarize at their level.
 4. **Tell them about the danger guard.** A `technical_level` of `non-technical` or `mixed` (and the
-   state before any profile exists) turns on a `PreToolUse` guard that blocks irreversible commands —
-   `rm -rf`, `git push --force`, `git reset --hard`, `DROP`/`TRUNCATE`, `DELETE`/`UPDATE` with no
-   `WHERE`, `dd` to a device, `curl | bash` — and asks for a safer alternative. A fully `technical`
-   user is never guarded. It turns off only if the user explicitly asks: `.rsc/.no-danger-guard`.
-   Mention it when you set a non-technical level, so a later block is not a surprise.
+   state before any profile exists) turns on a `PreToolUse` guard for irreversible commands —
+   `rm -rf`, `git push --force`, `git reset --hard`, `git branch -D`, `DROP`/`TRUNCATE`,
+   `DELETE`/`UPDATE` with no `WHERE`, `dd` to a device, `curl | bash`. For `non-technical` (or no
+   profile) Claude Code asks the user to confirm each one, saying what the command destroys; their
+   yes is the order that runs it. For `mixed` it only warns. A fully `technical` user is never
+   guarded. It turns off only if the user explicitly asks: `.rsc/.no-danger-guard`.
+   Mention it when you set a non-technical level, so a later confirmation is not a surprise.
 
 ### Phase 5 — HANDOFF
 

package/skills/postgresdb/SKILL.md

@@ -13,7 +13,7 @@ fix slow SQL, run zero-downtime migrations, and operate/secure the database. Too
 example is runnable.
 
 New, non-trivial feature with no approved spec + plan under `docs/wiki/sdd/`? Hand off to
-the `to-spec` skill before writing feature code (or `superpowers:writing-plans`); build
+the `to-spec` skill before writing feature code (then `to-tickets`); build
 straight from here only for a genuinely one-line, low-risk change.
 
 Deep dives: [schema-and-indexing](references/schema-and-indexing.md) (types, constraints, every index

package/skills/suggest/SKILL.md

@@ -34,8 +34,8 @@ The shape of the chain:
   when the effort will not fit one sitting.
 - Once the shape is known, capture it as a spec, and give any call that would be costly to undo
   its own ADR.
-- Build from a written plan. Tickets are the exception: only work that grew out of the
-  wayfinding step is broken into them first. A screen also routes through `flujo-interfaz`.
+- Small work builds straight from the clarified ask; big work is split into tickets first and
+  built from them. A screen also routes through `flujo-interfaz`.
 - Review the finished change against the repo's standards and against the spec before merging.
 
 Two exceptions, and say out loud when you take one:
@@ -54,9 +54,9 @@ whole run — advance through the phases without re-asking.
 If a step's skill is not installed, offer to add it (§2) before routing. `implement` always
 pairs with test-driven development and a verification pass before anything is called done.
 
-Exact skill names and order: `grill-with-docs` or `wayfinder` -> `superpowers:brainstorming` or
-`to-spec` (and `write-adr` for decisions) -> `superpowers:writing-plans` ->
-`superpowers:executing-plans` (big spec: `to-tickets` -> `implement-spec`) -> `code-review` -> `pr`.
+Exact skill names, by size. Small: `superpowers:brainstorming` or `grill-with-docs` ->
+`implement`. Big: `grill-with-docs` or `wayfinder` -> `to-spec` -> `to-tickets` ->
+`implement-spec`. Both: `write-adr` for decisions, then `code-review` -> `pr`.
 On Claude Code this rule also arrives as a per-turn hook; the brevity here is deduplication,
 not relaxation.
 
@@ -71,13 +71,12 @@ name it and offer it. This runs mid-conversation, not only at project start.
 1. `npx @damiangilgonzalez/harness catalog --available` lists every not-installed skill as
    `id  available  short description`.
 2. Pick the single best fit **by meaning**, the way you would match a request to a teammate's
-   expertise — "mandar emails de bienvenida" → an email/outreach skill, though not one keyword
-   overlaps. If nothing genuinely fits, say so
-   and move on: a tangential suggestion is worse than none.
+   expertise, even when no keyword overlaps. If nothing genuinely fits, say so and move on: a
+   tangential suggestion is worse than none.
 3. Ask once, plainly: "Para esto instalaría `<id>`, que aún no tienes. ¿La instalo? (sí/no)".
 4. On yes, run `npx @damiangilgonzalez/harness add <id>`, then continue the original task.
 
-Installing changes the user's environment, so it is always their call. One suggestion at a time,
+One suggestion at a time,
 and never to interrupt a flow with a nice-to-have. Never recommend something already installed
 (`npx @damiangilgonzalez/harness list`).
 
@@ -95,9 +94,8 @@ Not covered → one line, skill or agent. Rules: `skill-scout`.
 
 ## 3. A harness that is broken fixes itself
 
-You are injected into every session, so you are the only thing that can notice a broken
-harness before its owner does — and its owner usually cannot, because the symptoms name
-nothing they recognise. When any of these is true, act on it **once** in the session:
+Its owner rarely notices: the symptoms name nothing they know. When any of these
+is true, act on it **once** in the session:
 
 - `.rsc.json` exists and what it declares is not what is installed;
 - the same hook seems to run several times;
@@ -117,7 +115,7 @@ a cause. Then:
   teammate added, disarming a gate — **ask first**. A `git pull` never rewrites someone's
   machine.
 
-Offer once per session. Never mention any of it when the harness is healthy.
+Offer once per session; say nothing when the harness is healthy.
 
 ## 4. First contact
 
@@ -130,6 +128,12 @@ Before handling the first request of a session, check the workspace:
   `.rsc/.no-harness`, confirm in one line, and never auto-start `init` in this repo again.
 - Once the profile exists, this gate is inert. Never re-onboard.
 
+## 5. «Recuerda esto»
+
+A project or business fact goes to its topic page in `docs/wiki/` (link a new page from
+`wiki/index.md`); say the path. Your own memory sits outside the project, unseen by person and
+team: keep there only how this person likes you to work (or all, without `docs/`).
+
 ## Explain without assuming
 
 Define a term at first use; never give a command, flag or path without saying what it does.

package/skills/suggest/evals/cases.yaml

@@ -76,3 +76,9 @@ capability:
       - "Names that one missing automation/connector skill"
       - "Asks one short confirmation before installing and does not auto-install"
       - "On confirmation, runs `npx @damiangilgonzalez/harness add <id>` for that one missing skill, then resumes the automation task"
+
+  - scenario: "In a workspace with `docs/wiki/`, the user says 'recuerda que toda la actividad, también la de Andorra, va por una sola sociedad, Nadsan 2006 S.L.'. Show where rsc-suggest puts it."
+    must_include:
+      - "Writes the fact into the `docs/wiki/` page of its topic (creating it and linking it from `wiki/index.md` if none exists), not only into the assistant's own memory under `~/.claude/projects/`"
+      - "Tells the person the path where it was saved"
+      - "Does not start the feature chain or ask a lane question for it"

package/skills/to-spec/SKILL.md

@@ -2,7 +2,6 @@
 name: to-spec
 description: "Turns the current conversation into a spec (PRD) and publishes it to the project's issue tracker — no interview, just a synthesis of what has already been discussed."
 tags: ["spec", "prd", "issue-tracker"]
-disable-model-invocation: true
 profiles: [core, ui, full]
 origin: damiangil
 ---

package/skills/to-tickets/SKILL.md

@@ -2,7 +2,6 @@
 name: to-tickets
 description: "Breaks down a plan, a spec, or the current conversation into a set of \\"tracer bullet\\" tickets (vertical slices), each declaring which tickets block it, and publishes them to the configured tracker — as local files (one per ticket) or as issues with native blocking links in a real tracker."
 tags: ["tickets", "planning", "issue-tracker"]
-disable-model-invocation: true
 profiles: [core, ui, full]
 origin: damiangil
 ---

package/skills/wayfinder/SKILL.md

@@ -2,7 +2,6 @@
 name: wayfinder
 description: "Plans a huge chunk of work — more than fits in a single agent session — as a shared map of decision tickets in the repo's issue tracker, and resolves them one at a time until the path to the destination is clear."
 tags: ["planning", "issue-tracker", "large-scale-work"]
-disable-model-invocation: true
 profiles: [core, ui, full]
 origin: damiangil
 ---

package/targets/_md-block.js

@@ -21,7 +21,7 @@ export function writeSkill(id, fromDir, toPath) {
 export function wireHook(paths, sourceMd, policy = {}) {
   const full = stripFrontmatter(readFileSync(sourceMd, 'utf8'));
   const body = policy.codeHooks === false
-    ? `# rsc-suggest — always-on operations layer\n\nRead \`docs/wiki/harness/user-profile.md\` before acting. If the user wants to build, add or change something, route it through \`grill-with-docs\` or \`wayfinder\`, then write the spec with \`superpowers:brainstorming\` or \`to-spec\` (decisions go to \`write-adr\`) before any code, then build it with \`superpowers:writing-plans\` (or \`to-tickets\` then \`implement-spec\` for a big spec or one that came out of \`wayfinder\`), and review it with \`code-review\` before merging, writing the PR body with \`pr\` (si toca pantalla, \`flujo-interfaz\` dice que skill de diseno manda) — unless it is a one-line change, typo, or config bump, which skips the chain. Use \`orient\` to keep the user situated and \`suggest\` to offer a missing skill only when the current task needs it. Close with the configured orientation block.\n`
+    ? `# rsc-suggest — always-on operations layer\n\nRead \`docs/wiki/harness/user-profile.md\` before acting. If the user wants to build, add or change something, pick the chain by size and chain each step yourself. Small (one sitting, one ticket): clarify with \`superpowers:brainstorming\` (idea still vague) or \`grill-with-docs\` (a plan to harden), then build with \`implement\`. Big: \`grill-with-docs\` or \`wayfinder\` -> \`to-spec\` -> \`to-tickets\` -> \`implement-spec\`. Hard-to-reverse decisions go to \`write-adr\`; review with \`code-review\` and write the PR with \`pr\` before merging (si toca pantalla, \`flujo-interfaz\` dice que skill de diseno manda) — unless it is a one-line change, typo, or config bump, which skips the chain. Use \`orient\` to keep the user situated and \`suggest\` to offer a missing skill only when the current task needs it. Close with the configured orientation block.\n`
     : full;
   const block = `${MARK_START}\n${body}\n${MARK_END}`;
   let doc = existsSync(paths.hookTarget) ? readFileSync(paths.hookTarget, 'utf8') : '';

package/targets/claude.js

@@ -175,7 +175,8 @@ export function wireHook(paths, sourceMd, policy = {}) {
 
   if (policy.codeHooks !== false) {
   // Ship guard: a PreToolUse(Bash) hook that DENIES switching to / merging the trunk
-  // while the current feature branch has uncommitted or unpushed work — forcing the
+  // while the current feature branch has unpushed commits (uncommitted changes only get a
+  // worktree hint: they may be the user's own) — forcing the
   // commit → push → PR close (the `ship` skill). Materialized + node-run (Windows-safe),
   // registered idempotently, fail-open, opt-out via .rsc/.no-ship-guard. Other
   // (non-rsc) PreToolUse hooks are preserved.

package/targets/clone-bootstrap.mjs

@@ -43,7 +43,7 @@ const SEMVER = /^\d+\.\d+\.\d+(?:-[0-9a-z.-]+)?$/i;
  * nothing checks is just drift with a head start.
  */
 export const PROJECT_OPT_OUTS = [
-  'audit', 'claudemd-check', 'danger-guard', 'feature-gate', 'gitmoji', 'ship-guard', 'worktree-cleanup',
+  'audit', 'claudemd-check', 'danger-guard', 'feature-gate', 'gitmoji', 'knowledge-sync', 'ship-guard', 'trunk-guard', 'trunk-open', 'worktree-cleanup', 'worktree-isolation',
 ];
 
 /**