Harness spec 1.2.0: the library's tools fit both projects; the CLI implements it

The CLI's facts in memory, notes_search, note_manage, skills_list,
skill_view and skill_manage are `variables` now, filled with the CLI's own
values (src/tool/spec-vars.ts): every description and parameter list the CLI
sends is word for word what 1.1.0 said, except note and document ids, which
are strings on both sides (a number is still taken). Descriptions are
filled by the prompt texts' rules, parameter descriptions too. `narrow`
says what a project offers of a shared tool's parameters. Memory's changes
are one pure function (applyOps). Conformance: fill, narrow, memory.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

harness/tools/skill_view.json

@@ -11,7 +11,10 @@
       "skill_get"
     ]
   },
-  "description": "Load a skill: its full instructions, and the list of its supporting files (references, templates, scripts, assets). To read one of those, call again with file_path.",
+  "variables": {
+    "files": "what else a skill carries and how to read it (\", and the list of its supporting files (references, templates, scripts, assets). To read one of those, call again with file_path.\"), or \".\""
+  },
+  "description": "Load a skill: its full instructions{{files}}",
   "parameters": {
     "type": "object",
     "properties": {
@@ -27,5 +30,12 @@
     "required": [
       "name"
     ]
+  },
+  "narrow": {
+    "llembas": {
+      "drop": [
+        "file_path"
+      ]
+    }
   }
 }