@damiangilgonzalez/harness 1.3.18 → 1.3.19

package/README.md

@@ -174,6 +174,11 @@ rsc nunca las instala, actualiza ni sobrescribe: su versión es el commit.
 Al cerrar, guarda rama, ficheros y commits; al abrir, te dice dónde lo dejaste.
 Nunca guarda prompts, respuestas ni secretos, y no sale de tu máquina. `rsc memory off` lo apaga.
 
+Lo que el proyecto *sabe* va a `docs/wiki/`: dile «recuerda que…» y te dirá en qué página lo
+guardó. Esa wiki, `docs/attachments/` y `01-TOOLS/` viajan solas a tu equipo por la rama
+`rsc/knowledge` y llegan a `main` dentro de vuestras PRs. `rsc knowledge-sync off` lo apaga.
+Cómo funciona todo junto: [la memoria del harness](docs/como-funciona/memoria.md).
+
 ![Una rama, una copia de trabajo](docs/img/readme/readme-18-worktrees.png)
 
 Cada rama en su worktree, cortada siempre desde `origin`.

package/manifest.json

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

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@damiangilgonzalez/harness",
-  "version": "1.3.18",
+  "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/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();

package/skills/suggest/SKILL.md

@@ -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/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',
 ];
 
 /**