@younndai/lyt-skills 0.9.5 → 0.9.7

package/README.md

@@ -24,20 +24,20 @@
 
 ## What is this?
 
-`@younndai/lyt-skills` is where [Lyt™](https://github.com/YounndAI/lyt)'s **AI-first** design becomes tangible: fifteen harness skills that let AI agents — Claude Code, Codex, and generic agent runtimes — drive your markdown vaults as **first-class operators**. Install once and your agent can capture notes, search your pod, record decisions, write plans, retros, and handoffs, explore meshes, and sync vaults — through the same governed operation set you use, under the same permission semantics. This is the "install once, every agent runtime knows Lyt" layer.
+`@younndai/lyt-skills` is where [Lyt™](https://github.com/YounndAI/lyt)'s **AI-first** design becomes tangible: sixteen harness skills that let AI agents — Claude Code, Codex, and generic agent runtimes — drive your markdown vaults as **first-class operators**. Install once and your agent can capture notes, search your pod, record decisions, write plans, retros, and handoffs, explore meshes, and sync vaults — through the same governed operation set you use, under the same permission semantics. This is the "install once, every agent runtime knows Lyt" layer.
 
-Most skills wrap a pattern verb from the `lyt pattern run` runtime, so structured knowledge work (plans, results, decisions, captures) shows up as first-class agent skills inside any vault; the read/orient skills (`/lyt-pod`, `/lyt-search`, `/lyt-primer-context`, `/lyt-mesh-explore`, `/lyt-sync`) wrap the corresponding CLI verbs directly. Pairs with [`@younndai/lyt-vault`](https://www.npmjs.com/package/@younndai/lyt-vault), which ships the four default patterns the skills resolve against.
+Most skills wrap a pattern verb from the `lyt pattern run` runtime, so structured knowledge work (plans, results, decisions, captures) shows up as first-class agent skills inside any vault; the read/orient + addressing skills (`/lyt-pod`, `/lyt-search`, `/lyt-primer-context`, `/lyt-mesh-explore`, `/lyt-sync`, `/lyt-alias`) wrap the corresponding CLI verbs directly. Pairs with [`@younndai/lyt-vault`](https://www.npmjs.com/package/@younndai/lyt-vault), which ships the four default patterns the skills resolve against.
 
 ## Install
 
 ```bash
 npm install -g @younndai/lyt@alpha   # the meta package bundles lyt-skills
-lyt skills install                   # links the 15 SKILL.md files into your harness(es)
+lyt skills install                   # links the 16 SKILL.md files into your harness(es)
 ```
 
 Tri-runtime: the installer detects Claude Code, Codex, and generic agent runtimes, and installs per-runtime (symlink by default, `--copy` for regular directories).
 
-## The 15 skills
+## The 16 skills
 
 | Skill                 | Wraps                                              | Use it when                                                  |
 | --------------------- | -------------------------------------------------- | ------------------------------------------------------------ |
@@ -46,6 +46,7 @@ Tri-runtime: the installer detects Claude Code, Codex, and generic agent runtime
 | `/lyt-search`         | `lyt search` (tiered cascade)                      | Ranked search across the whole pod, a mesh, or a vault.      |
 | `/lyt-pod`            | `lyt mesh list` + `lyt vault list`                 | Enumerating every mesh + vault on the machine.               |
 | `/lyt-mesh-explore`   | `lyt mesh info`                                    | Drilling into one mesh's members and metadata.               |
+| `/lyt-alias`          | `lyt alias` set/`--list`/`--remove`                | Managing pod-local vault aliases (name → rid).               |
 | `/lyt-primer-context` | `lyt primer` + `lyt vault info`                    | Priming an agent with vault/mesh/pod context.                |
 | `/lyt-sync`           | gated git pull/commit/push                         | Syncing a vault with its remote under the writable gate.     |
 | `/lyt-plan`           | work-management + plan                             | Drafting a multi-phase plan before implementation.           |

package/dist/symlink.js

@@ -86,10 +86,24 @@ export function symlinkSkillsTriRuntime(opts = {}) {
 }
 function installOne(input) {
     const { sourceSkillDir, targetSkillDir, copy, force, symlinkFn, collisionStampFn } = input;
-    if (!existsSync(targetSkillDir)) {
-        return { status: createLink(sourceSkillDir, targetSkillDir, copy, symlinkFn) };
+    let stat = null;
+    try {
+        stat = lstatSync(targetSkillDir);
+    }
+    catch (err) {
+        if (err.code === "ENOENT") {
+            return { status: createLink(sourceSkillDir, targetSkillDir, copy, symlinkFn) };
+        }
+        throw err;
+    }
+    if (stat.isSymbolicLink() && !existsSync(targetSkillDir)) {
+        rmSync(targetSkillDir, { recursive: true, force: true });
+        const newStatus = createLink(sourceSkillDir, targetSkillDir, copy, symlinkFn);
+        return {
+            status: "replaced",
+            message: `healed dangling symlink (target was missing); now ${newStatus}`,
+        };
     }
-    const stat = lstatSync(targetSkillDir);
     if (stat.isSymbolicLink()) {
         const existingTarget = resolve(readlinkSync(targetSkillDir));
         if (existingTarget === sourceSkillDir) {

package/dist/symlink.js.map

@@ -1 +1 @@
-{"version":3,"file":"symlink.js","sourceRoot":"","sources":["../src/symlink.ts"],"names":[],"mappings":"AAgBA,OAAO,EACL,MAAM,EACN,UAAU,EACV,SAAS,EACT,SAAS,EACT,WAAW,EACX,YAAY,EACZ,YAAY,EACZ,UAAU,EACV,MAAM,EACN,QAAQ,EACR,WAAW,GACZ,MAAM,SAAS,CAAC;AACjB,OAAO,EAAE,OAAO,EAAE,QAAQ,EAAE,MAAM,SAAS,CAAC;AAC5C,OAAO,EAAE,QAAQ,EAAE,OAAO,EAAE,IAAI,EAAE,OAAO,EAAE,MAAM,WAAW,CAAC;AAC7D,OAAO,EAAE,aAAa,EAAE,MAAM,UAAU,CAAC;AAIzC,MAAM,CAAC,MAAM,YAAY,GAAuB,CAAC,QAAQ,EAAE,OAAO,EAAE,QAAQ,CAAC,CAAC;AAqD9E,MAAM,mBAAmB,GAAkC;IACzD,MAAM,EAAE,GAAG,EAAE,CAAC,IAAI,CAAC,OAAO,EAAE,EAAE,SAAS,EAAE,QAAQ,CAAC;IAClD,KAAK,EAAE,GAAG,EAAE,CAAC,IAAI,CAAC,OAAO,EAAE,EAAE,QAAQ,EAAE,QAAQ,CAAC;IAChD,MAAM,EAAE,GAAG,EAAE,CAAC,IAAI,CAAC,OAAO,EAAE,EAAE,SAAS,EAAE,QAAQ,CAAC;CACnD,CAAC;AAEF,MAAM,UAAU,mBAAmB,CAAC,OAAgB;IAClD,OAAO,mBAAmB,CAAC,OAAO,CAAC,EAAE,CAAC;AACxC,CAAC;AAED,MAAM,UAAU,mBAAmB;IACjC,MAAM,IAAI,GAAG,OAAO,CAAC,aAAa,CAAC,MAAM,CAAC,IAAI,CAAC,GAAG,CAAC,CAAC,CAAC;IACrD,OAAO,OAAO,CAAC,IAAI,EAAE,IAAI,EAAE,QAAQ,CAAC,CAAC;AACvC,CAAC;AAED,MAAM,UAAU,iBAAiB,CAAC,SAAiB;IACjD,IAAI,CAAC,UAAU,CAAC,SAAS,CAAC,EAAE,CAAC;QAC3B,OAAO,EAAE,CAAC;IACZ,CAAC;IACD,OAAO,WAAW,CAAC,SAAS,CAAC,CAAC,MAAM,CAAC,CAAC,IAAI,EAAE,EAAE;QAC5C,MAAM,QAAQ,GAAG,IAAI,CAAC,SAAS,EAAE,IAAI,CAAC,CAAC;QACvC,IAAI,CAAC,QAAQ,CAAC,QAAQ,CAAC,CAAC,WAAW,EAAE;YAAE,OAAO,KAAK,CAAC;QACpD,OAAO,UAAU,CAAC,IAAI,CAAC,QAAQ,EAAE,UAAU,CAAC,CAAC,CAAC;IAChD,CAAC,CAAC,CAAC;AACL,CAAC;AAED,SAAS,WAAW;IAClB,OAAO,QAAQ,EAAE,KAAK,OAAO,CAAC,CAAC,CAAC,UAAU,CAAC,CAAC,CAAC,KAAK,CAAC;AACrD,CAAC;AAED,SAAS,UAAU,CACjB,cAAsB,EACtB,cAAsB,EACtB,IAAa,EACb,SAA2E;IAE3E,IAAI,IAAI,EAAE,CAAC;QACT,MAAM,CAAC,cAAc,EAAE,cAAc,EAAE,EAAE,SAAS,EAAE,IAAI,EAAE,CAAC,CAAC;QAC5D,OAAO,gBAAgB,CAAC;IAC1B,CAAC;IACD,IAAI,CAAC;QACH,SAAS,CAAC,cAAc,EAAE,cAAc,EAAE,WAAW,EAAE,CAAC,CAAC;QACzD,OAAO,mBAAmB,CAAC;IAC7B,CAAC;IAAC,OAAO,GAAG,EAAE,CAAC;QACb,MAAM,IAAI,GAAI,GAA6B,CAAC,IAAI,CAAC;QACjD,IAAI,IAAI,KAAK,OAAO,IAAI,IAAI,KAAK,QAAQ,EAAE,CAAC;YAC1C,MAAM,CAAC,cAAc,EAAE,cAAc,EAAE,EAAE,SAAS,EAAE,IAAI,EAAE,CAAC,CAAC;YAC5D,OAAO,yBAAyB,CAAC;QACnC,CAAC;QACD,MAAM,GAAG,CAAC;IACZ,CAAC;AACH,CAAC;AAED,MAAM,gBAAgB,GAAG,CAAC,MAAc,EAAE,IAAY,EAAE,IAAwB,EAAQ,EAAE;IACxF,WAAW,CAAC,MAAM,EAAE,IAAI,EAAE,IAAI,CAAC,CAAC;AAClC,CAAC,CAAC;AAEF,MAAM,UAAU,uBAAuB,CAAC,OAA6B,EAAE;IACrE,MAAM,SAAS,GAAG,IAAI,CAAC,SAAS,CAAC,CAAC,CAAC,OAAO,CAAC,IAAI,CAAC,SAAS,CAAC,CAAC,CAAC,CAAC,mBAAmB,EAAE,CAAC;IACnF,MAAM,QAAQ,GAAG,IAAI,CAAC,QAAQ,IAAI,YAAY,CAAC;IAC/C,MAAM,IAAI,GAAG,IAAI,CAAC,IAAI,IAAI,KAAK,CAAC;IAChC,MAAM,KAAK,GAAG,IAAI,CAAC,KAAK,IAAI,KAAK,CAAC;IAElC,IAAI,CAAC,UAAU,CAAC,SAAS,CAAC,EAAE,CAAC;QAC3B,MAAM,IAAI,KAAK,CACb,0CAA0C,SAAS,oCAAoC,CACxF,CAAC;IACJ,CAAC;IAED,MAAM,UAAU,GAAG,iBAAiB,CAAC,SAAS,CAAC,CAAC;IAChD,MAAM,UAAU,GAAG,IAAI,CAAC,UAAU;QAChC,CAAC,CAAC,UAAU,CAAC,MAAM,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,IAAI,CAAC,UAAW,CAAC,QAAQ,CAAC,CAAC,CAAC,CAAC;QACxD,CAAC,CAAC,UAAU,CAAC;IAEf,MAAM,SAAS,GAAG,IAAI,CAAC,iBAAiB,IAAI,gBAAgB,CAAC;IAC7D,MAAM,gBAAgB,GAAG,IAAI,CAAC,gBAAgB,IAAI,qBAAqB,CAAC;IACxE,MAAM,OAAO,GAAyB,EAAE,CAAC;IAEzC,KAAK,MAAM,OAAO,IAAI,QAAQ,EAAE,CAAC;QAC/B,MAAM,UAAU,GAAG,IAAI,CAAC,kBAAkB,EAAE,CAAC,OAAO,CAAC,IAAI,mBAAmB,CAAC,OAAO,CAAC,CAAC;QACtF,SAAS,CAAC,UAAU,EAAE,EAAE,SAAS,EAAE,IAAI,EAAE,CAAC,CAAC;QAE3C,KAAK,MAAM,KAAK,IAAI,UAAU,EAAE,CAAC;YAC/B,MAAM,cAAc,GAAG,OAAO,CAAC,IAAI,CAAC,SAAS,EAAE,KAAK,CAAC,CAAC,CAAC;YACvD,MAAM,cAAc,GAAG,IAAI,CAAC,UAAU,EAAE,KAAK,CAAC,CAAC;YAC/C,MAAM,MAAM,GAAG,UAAU,CAAC;gBACxB,cAAc;gBACd,cAAc;gBACd,IAAI;gBACJ,KAAK;gBACL,SAAS;gBACT,gBAAgB;aACjB,CAAC,CAAC;YACH,OAAO,CAAC,IAAI,CAAC,EAAE,KAAK,EAAE,OAAO,EAAE,UAAU,EAAE,cAAc,EAAE,GAAG,MAAM,EAAE,CAAC,CAAC;QAC1E,CAAC;IACH,CAAC;IAED,OAAO,EAAE,SAAS,EAAE,QAAQ,EAAE,OAAO,EAAE,CAAC;AAC1C,CAAC;AAgBD,SAAS,UAAU,CAAC,KAAsB;IACxC,MAAM,EAAE,cAAc,EAAE,cAAc,EAAE,IAAI,EAAE,KAAK,EAAE,SAAS,EAAE,gBAAgB,EAAE,GAAG,KAAK,CAAC;IAE3F,IAAI,CAAC,UAAU,CAAC,cAAc,CAAC,EAAE,CAAC;QAChC,OAAO,EAAE,MAAM,EAAE,UAAU,CAAC,cAAc,EAAE,cAAc,EAAE,IAAI,EAAE,SAAS,CAAC,EAAE,CAAC;IACjF,CAAC;IAED,MAAM,IAAI,GAAG,SAAS,CAAC,cAAc,CAAC,CAAC;IAEvC,IAAI,IAAI,CAAC,cAAc,EAAE,EAAE,CAAC;QAC1B,MAAM,cAAc,GAAG,OAAO,CAAC,YAAY,CAAC,cAAc,CAAC,CAAC,CAAC;QAC7D,IAAI,cAAc,KAAK,cAAc,EAAE,CAAC;YACtC,OAAO,EAAE,MAAM,EAAE,gBAAgB,EAAE,CAAC;QACtC,CAAC;QACD,IAAI,CAAC,KAAK,EAAE,CAAC;YACX,OAAO;gBACL,MAAM,EAAE,mBAAmB;gBAC3B,OAAO,EAAE,8BAA8B,cAAc,kCAAkC;aACxF,CAAC;QACJ,CAAC;QACD,MAAM,CAAC,cAAc,EAAE,EAAE,SAAS,EAAE,IAAI,EAAE,KAAK,EAAE,IAAI,EAAE,CAAC,CAAC;QACzD,MAAM,SAAS,GAAG,UAAU,CAAC,cAAc,EAAE,cAAc,EAAE,IAAI,EAAE,SAAS,CAAC,CAAC;QAC9E,OAAO;YACL,MAAM,EAAE,UAAU;YAClB,OAAO,EAAE,yBAAyB,cAAc,UAAU,SAAS,EAAE;SACtE,CAAC;IACJ,CAAC;IAED,IAAI,IAAI,CAAC,WAAW,EAAE,EAAE,CAAC;QAgBvB,IAAI,SAAS,CAAC,cAAc,EAAE,cAAc,CAAC,EAAE,CAAC;YAC9C,MAAM,CAAC,cAAc,EAAE,EAAE,SAAS,EAAE,IAAI,EAAE,KAAK,EAAE,IAAI,EAAE,CAAC,CAAC;YACzD,MAAM,SAAS,GAAG,UAAU,CAAC,cAAc,EAAE,cAAc,EAAE,IAAI,EAAE,SAAS,CAAC,CAAC;YAC9E,OAAO;gBACL,MAAM,EAAE,UAAU;gBAClB,OAAO,EAAE,yDAAyD,SAAS,EAAE;aAC9E,CAAC;QACJ,CAAC;QACD,MAAM,SAAS,GAAG,WAAW,CAAC,cAAc,EAAE,gBAAgB,CAAC,CAAC;QAChE,MAAM,SAAS,GAAG,UAAU,CAAC,cAAc,EAAE,cAAc,EAAE,IAAI,EAAE,SAAS,CAAC,CAAC;QAC9E,OAAO;YACL,MAAM,EAAE,mBAAmB;YAC3B,OAAO,EACL,0EAA0E;gBAC1E,IAAI,QAAQ,CAAC,SAAS,CAAC,gEAAgE,SAAS,GAAG;SACtG,CAAC;IACJ,CAAC;IAKD,KAAK,KAAK,CAAC;IACX,OAAO;QACL,MAAM,EAAE,wBAAwB;QAChC,OAAO,EAAE,GAAG,cAAc,0DAA0D;KACrF,CAAC;AACJ,CAAC;AAMD,SAAS,qBAAqB;IAC5B,OAAO,IAAI,IAAI,EAAE;SACd,WAAW,EAAE;SACb,OAAO,CAAC,OAAO,EAAE,EAAE,CAAC;SACpB,OAAO,CAAC,WAAW,EAAE,GAAG,CAAC,CAAC;AAC/B,CAAC;AAMD,SAAS,WAAW,CAAC,cAAsB,EAAE,OAAqB;IAChE,MAAM,IAAI,GAAG,GAAG,cAAc,UAAU,OAAO,EAAE,EAAE,CAAC;IACpD,IAAI,SAAS,GAAG,IAAI,CAAC;IACrB,IAAI,CAAC,GAAG,CAAC,CAAC;IACV,OAAO,UAAU,CAAC,SAAS,CAAC,EAAE,CAAC;QAC7B,SAAS,GAAG,GAAG,IAAI,IAAI,CAAC,EAAE,CAAC;QAC3B,CAAC,EAAE,CAAC;IACN,CAAC;IACD,UAAU,CAAC,cAAc,EAAE,SAAS,CAAC,CAAC;IACtC,OAAO,SAAS,CAAC;AACnB,CAAC;AAOD,SAAS,SAAS,CAAC,CAAS,EAAE,CAAS;IACrC,IAAI,MAAgB,CAAC;IACrB,IAAI,MAAgB,CAAC;IACrB,IAAI,CAAC;QACH,MAAM,GAAG,WAAW,CAAC,CAAC,CAAC,CAAC,IAAI,EAAE,CAAC;QAC/B,MAAM,GAAG,WAAW,CAAC,CAAC,CAAC,CAAC,IAAI,EAAE,CAAC;IACjC,CAAC;IAAC,MAAM,CAAC;QACP,OAAO,KAAK,CAAC;IACf,CAAC;IACD,IAAI,MAAM,CAAC,MAAM,KAAK,MAAM,CAAC,MAAM;QAAE,OAAO,KAAK,CAAC;IAClD,KAAK,IAAI,CAAC,GAAG,CAAC,EAAE,CAAC,GAAG,MAAM,CAAC,MAAM,EAAE,CAAC,EAAE,EAAE,CAAC;QACvC,IAAI,MAAM,CAAC,CAAC,CAAC,KAAK,MAAM,CAAC,CAAC,CAAC;YAAE,OAAO,KAAK,CAAC;QAC1C,MAAM,EAAE,GAAG,IAAI,CAAC,CAAC,EAAE,MAAM,CAAC,CAAC,CAAE,CAAC,CAAC;QAC/B,MAAM,EAAE,GAAG,IAAI,CAAC,CAAC,EAAE,MAAM,CAAC,CAAC,CAAE,CAAC,CAAC;QAC/B,MAAM,EAAE,GAAG,SAAS,CAAC,EAAE,CAAC,CAAC;QACzB,MAAM,EAAE,GAAG,SAAS,CAAC,EAAE,CAAC,CAAC;QACzB,IAAI,EAAE,CAAC,cAAc,EAAE,IAAI,EAAE,CAAC,cAAc,EAAE;YAAE,OAAO,KAAK,CAAC;QAC7D,IAAI,EAAE,CAAC,WAAW,EAAE,KAAK,EAAE,CAAC,WAAW,EAAE;YAAE,OAAO,KAAK,CAAC;QACxD,IAAI,EAAE,CAAC,WAAW,EAAE,EAAE,CAAC;YACrB,IAAI,CAAC,SAAS,CAAC,EAAE,EAAE,EAAE,CAAC;gBAAE,OAAO,KAAK,CAAC;QACvC,CAAC;aAAM,CAAC;YACN,IAAI,EAAE,CAAC,IAAI,KAAK,EAAE,CAAC,IAAI;gBAAE,OAAO,KAAK,CAAC;YACtC,IAAI,CAAC,YAAY,CAAC,EAAE,CAAC,CAAC,MAAM,CAAC,YAAY,CAAC,EAAE,CAAC,CAAC;gBAAE,OAAO,KAAK,CAAC;QAC/D,CAAC;IACH,CAAC;IACD,OAAO,IAAI,CAAC;AACd,CAAC"}
+{"version":3,"file":"symlink.js","sourceRoot":"","sources":["../src/symlink.ts"],"names":[],"mappings":"AAgBA,OAAO,EACL,MAAM,EACN,UAAU,EACV,SAAS,EACT,SAAS,EACT,WAAW,EACX,YAAY,EACZ,YAAY,EACZ,UAAU,EACV,MAAM,EACN,QAAQ,EACR,WAAW,GACZ,MAAM,SAAS,CAAC;AACjB,OAAO,EAAE,OAAO,EAAE,QAAQ,EAAE,MAAM,SAAS,CAAC;AAC5C,OAAO,EAAE,QAAQ,EAAE,OAAO,EAAE,IAAI,EAAE,OAAO,EAAE,MAAM,WAAW,CAAC;AAC7D,OAAO,EAAE,aAAa,EAAE,MAAM,UAAU,CAAC;AAIzC,MAAM,CAAC,MAAM,YAAY,GAAuB,CAAC,QAAQ,EAAE,OAAO,EAAE,QAAQ,CAAC,CAAC;AAqD9E,MAAM,mBAAmB,GAAkC;IACzD,MAAM,EAAE,GAAG,EAAE,CAAC,IAAI,CAAC,OAAO,EAAE,EAAE,SAAS,EAAE,QAAQ,CAAC;IAClD,KAAK,EAAE,GAAG,EAAE,CAAC,IAAI,CAAC,OAAO,EAAE,EAAE,QAAQ,EAAE,QAAQ,CAAC;IAChD,MAAM,EAAE,GAAG,EAAE,CAAC,IAAI,CAAC,OAAO,EAAE,EAAE,SAAS,EAAE,QAAQ,CAAC;CACnD,CAAC;AAEF,MAAM,UAAU,mBAAmB,CAAC,OAAgB;IAClD,OAAO,mBAAmB,CAAC,OAAO,CAAC,EAAE,CAAC;AACxC,CAAC;AAED,MAAM,UAAU,mBAAmB;IACjC,MAAM,IAAI,GAAG,OAAO,CAAC,aAAa,CAAC,MAAM,CAAC,IAAI,CAAC,GAAG,CAAC,CAAC,CAAC;IACrD,OAAO,OAAO,CAAC,IAAI,EAAE,IAAI,EAAE,QAAQ,CAAC,CAAC;AACvC,CAAC;AAED,MAAM,UAAU,iBAAiB,CAAC,SAAiB;IACjD,IAAI,CAAC,UAAU,CAAC,SAAS,CAAC,EAAE,CAAC;QAC3B,OAAO,EAAE,CAAC;IACZ,CAAC;IACD,OAAO,WAAW,CAAC,SAAS,CAAC,CAAC,MAAM,CAAC,CAAC,IAAI,EAAE,EAAE;QAC5C,MAAM,QAAQ,GAAG,IAAI,CAAC,SAAS,EAAE,IAAI,CAAC,CAAC;QACvC,IAAI,CAAC,QAAQ,CAAC,QAAQ,CAAC,CAAC,WAAW,EAAE;YAAE,OAAO,KAAK,CAAC;QACpD,OAAO,UAAU,CAAC,IAAI,CAAC,QAAQ,EAAE,UAAU,CAAC,CAAC,CAAC;IAChD,CAAC,CAAC,CAAC;AACL,CAAC;AAED,SAAS,WAAW;IAClB,OAAO,QAAQ,EAAE,KAAK,OAAO,CAAC,CAAC,CAAC,UAAU,CAAC,CAAC,CAAC,KAAK,CAAC;AACrD,CAAC;AAED,SAAS,UAAU,CACjB,cAAsB,EACtB,cAAsB,EACtB,IAAa,EACb,SAA2E;IAE3E,IAAI,IAAI,EAAE,CAAC;QACT,MAAM,CAAC,cAAc,EAAE,cAAc,EAAE,EAAE,SAAS,EAAE,IAAI,EAAE,CAAC,CAAC;QAC5D,OAAO,gBAAgB,CAAC;IAC1B,CAAC;IACD,IAAI,CAAC;QACH,SAAS,CAAC,cAAc,EAAE,cAAc,EAAE,WAAW,EAAE,CAAC,CAAC;QACzD,OAAO,mBAAmB,CAAC;IAC7B,CAAC;IAAC,OAAO,GAAG,EAAE,CAAC;QACb,MAAM,IAAI,GAAI,GAA6B,CAAC,IAAI,CAAC;QACjD,IAAI,IAAI,KAAK,OAAO,IAAI,IAAI,KAAK,QAAQ,EAAE,CAAC;YAC1C,MAAM,CAAC,cAAc,EAAE,cAAc,EAAE,EAAE,SAAS,EAAE,IAAI,EAAE,CAAC,CAAC;YAC5D,OAAO,yBAAyB,CAAC;QACnC,CAAC;QACD,MAAM,GAAG,CAAC;IACZ,CAAC;AACH,CAAC;AAED,MAAM,gBAAgB,GAAG,CAAC,MAAc,EAAE,IAAY,EAAE,IAAwB,EAAQ,EAAE;IACxF,WAAW,CAAC,MAAM,EAAE,IAAI,EAAE,IAAI,CAAC,CAAC;AAClC,CAAC,CAAC;AAEF,MAAM,UAAU,uBAAuB,CAAC,OAA6B,EAAE;IACrE,MAAM,SAAS,GAAG,IAAI,CAAC,SAAS,CAAC,CAAC,CAAC,OAAO,CAAC,IAAI,CAAC,SAAS,CAAC,CAAC,CAAC,CAAC,mBAAmB,EAAE,CAAC;IACnF,MAAM,QAAQ,GAAG,IAAI,CAAC,QAAQ,IAAI,YAAY,CAAC;IAC/C,MAAM,IAAI,GAAG,IAAI,CAAC,IAAI,IAAI,KAAK,CAAC;IAChC,MAAM,KAAK,GAAG,IAAI,CAAC,KAAK,IAAI,KAAK,CAAC;IAElC,IAAI,CAAC,UAAU,CAAC,SAAS,CAAC,EAAE,CAAC;QAC3B,MAAM,IAAI,KAAK,CACb,0CAA0C,SAAS,oCAAoC,CACxF,CAAC;IACJ,CAAC;IAED,MAAM,UAAU,GAAG,iBAAiB,CAAC,SAAS,CAAC,CAAC;IAChD,MAAM,UAAU,GAAG,IAAI,CAAC,UAAU;QAChC,CAAC,CAAC,UAAU,CAAC,MAAM,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,IAAI,CAAC,UAAW,CAAC,QAAQ,CAAC,CAAC,CAAC,CAAC;QACxD,CAAC,CAAC,UAAU,CAAC;IAEf,MAAM,SAAS,GAAG,IAAI,CAAC,iBAAiB,IAAI,gBAAgB,CAAC;IAC7D,MAAM,gBAAgB,GAAG,IAAI,CAAC,gBAAgB,IAAI,qBAAqB,CAAC;IACxE,MAAM,OAAO,GAAyB,EAAE,CAAC;IAEzC,KAAK,MAAM,OAAO,IAAI,QAAQ,EAAE,CAAC;QAC/B,MAAM,UAAU,GAAG,IAAI,CAAC,kBAAkB,EAAE,CAAC,OAAO,CAAC,IAAI,mBAAmB,CAAC,OAAO,CAAC,CAAC;QACtF,SAAS,CAAC,UAAU,EAAE,EAAE,SAAS,EAAE,IAAI,EAAE,CAAC,CAAC;QAE3C,KAAK,MAAM,KAAK,IAAI,UAAU,EAAE,CAAC;YAC/B,MAAM,cAAc,GAAG,OAAO,CAAC,IAAI,CAAC,SAAS,EAAE,KAAK,CAAC,CAAC,CAAC;YACvD,MAAM,cAAc,GAAG,IAAI,CAAC,UAAU,EAAE,KAAK,CAAC,CAAC;YAC/C,MAAM,MAAM,GAAG,UAAU,CAAC;gBACxB,cAAc;gBACd,cAAc;gBACd,IAAI;gBACJ,KAAK;gBACL,SAAS;gBACT,gBAAgB;aACjB,CAAC,CAAC;YACH,OAAO,CAAC,IAAI,CAAC,EAAE,KAAK,EAAE,OAAO,EAAE,UAAU,EAAE,cAAc,EAAE,GAAG,MAAM,EAAE,CAAC,CAAC;QAC1E,CAAC;IACH,CAAC;IAED,OAAO,EAAE,SAAS,EAAE,QAAQ,EAAE,OAAO,EAAE,CAAC;AAC1C,CAAC;AAgBD,SAAS,UAAU,CAAC,KAAsB;IACxC,MAAM,EAAE,cAAc,EAAE,cAAc,EAAE,IAAI,EAAE,KAAK,EAAE,SAAS,EAAE,gBAAgB,EAAE,GAAG,KAAK,CAAC;IAa3F,IAAI,IAAI,GAAwC,IAAI,CAAC;IACrD,IAAI,CAAC;QACH,IAAI,GAAG,SAAS,CAAC,cAAc,CAAC,CAAC;IACnC,CAAC;IAAC,OAAO,GAAG,EAAE,CAAC;QACb,IAAK,GAA6B,CAAC,IAAI,KAAK,QAAQ,EAAE,CAAC;YAErD,OAAO,EAAE,MAAM,EAAE,UAAU,CAAC,cAAc,EAAE,cAAc,EAAE,IAAI,EAAE,SAAS,CAAC,EAAE,CAAC;QACjF,CAAC;QACD,MAAM,GAAG,CAAC;IACZ,CAAC;IAID,IAAI,IAAI,CAAC,cAAc,EAAE,IAAI,CAAC,UAAU,CAAC,cAAc,CAAC,EAAE,CAAC;QAEzD,MAAM,CAAC,cAAc,EAAE,EAAE,SAAS,EAAE,IAAI,EAAE,KAAK,EAAE,IAAI,EAAE,CAAC,CAAC;QACzD,MAAM,SAAS,GAAG,UAAU,CAAC,cAAc,EAAE,cAAc,EAAE,IAAI,EAAE,SAAS,CAAC,CAAC;QAC9E,OAAO;YACL,MAAM,EAAE,UAAU;YAClB,OAAO,EAAE,qDAAqD,SAAS,EAAE;SAC1E,CAAC;IACJ,CAAC;IAED,IAAI,IAAI,CAAC,cAAc,EAAE,EAAE,CAAC;QAC1B,MAAM,cAAc,GAAG,OAAO,CAAC,YAAY,CAAC,cAAc,CAAC,CAAC,CAAC;QAC7D,IAAI,cAAc,KAAK,cAAc,EAAE,CAAC;YACtC,OAAO,EAAE,MAAM,EAAE,gBAAgB,EAAE,CAAC;QACtC,CAAC;QACD,IAAI,CAAC,KAAK,EAAE,CAAC;YACX,OAAO;gBACL,MAAM,EAAE,mBAAmB;gBAC3B,OAAO,EAAE,8BAA8B,cAAc,kCAAkC;aACxF,CAAC;QACJ,CAAC;QACD,MAAM,CAAC,cAAc,EAAE,EAAE,SAAS,EAAE,IAAI,EAAE,KAAK,EAAE,IAAI,EAAE,CAAC,CAAC;QACzD,MAAM,SAAS,GAAG,UAAU,CAAC,cAAc,EAAE,cAAc,EAAE,IAAI,EAAE,SAAS,CAAC,CAAC;QAC9E,OAAO;YACL,MAAM,EAAE,UAAU;YAClB,OAAO,EAAE,yBAAyB,cAAc,UAAU,SAAS,EAAE;SACtE,CAAC;IACJ,CAAC;IAED,IAAI,IAAI,CAAC,WAAW,EAAE,EAAE,CAAC;QAgBvB,IAAI,SAAS,CAAC,cAAc,EAAE,cAAc,CAAC,EAAE,CAAC;YAC9C,MAAM,CAAC,cAAc,EAAE,EAAE,SAAS,EAAE,IAAI,EAAE,KAAK,EAAE,IAAI,EAAE,CAAC,CAAC;YACzD,MAAM,SAAS,GAAG,UAAU,CAAC,cAAc,EAAE,cAAc,EAAE,IAAI,EAAE,SAAS,CAAC,CAAC;YAC9E,OAAO;gBACL,MAAM,EAAE,UAAU;gBAClB,OAAO,EAAE,yDAAyD,SAAS,EAAE;aAC9E,CAAC;QACJ,CAAC;QACD,MAAM,SAAS,GAAG,WAAW,CAAC,cAAc,EAAE,gBAAgB,CAAC,CAAC;QAChE,MAAM,SAAS,GAAG,UAAU,CAAC,cAAc,EAAE,cAAc,EAAE,IAAI,EAAE,SAAS,CAAC,CAAC;QAC9E,OAAO;YACL,MAAM,EAAE,mBAAmB;YAC3B,OAAO,EACL,0EAA0E;gBAC1E,IAAI,QAAQ,CAAC,SAAS,CAAC,gEAAgE,SAAS,GAAG;SACtG,CAAC;IACJ,CAAC;IAKD,KAAK,KAAK,CAAC;IACX,OAAO;QACL,MAAM,EAAE,wBAAwB;QAChC,OAAO,EAAE,GAAG,cAAc,0DAA0D;KACrF,CAAC;AACJ,CAAC;AAMD,SAAS,qBAAqB;IAC5B,OAAO,IAAI,IAAI,EAAE;SACd,WAAW,EAAE;SACb,OAAO,CAAC,OAAO,EAAE,EAAE,CAAC;SACpB,OAAO,CAAC,WAAW,EAAE,GAAG,CAAC,CAAC;AAC/B,CAAC;AAMD,SAAS,WAAW,CAAC,cAAsB,EAAE,OAAqB;IAChE,MAAM,IAAI,GAAG,GAAG,cAAc,UAAU,OAAO,EAAE,EAAE,CAAC;IACpD,IAAI,SAAS,GAAG,IAAI,CAAC;IACrB,IAAI,CAAC,GAAG,CAAC,CAAC;IACV,OAAO,UAAU,CAAC,SAAS,CAAC,EAAE,CAAC;QAC7B,SAAS,GAAG,GAAG,IAAI,IAAI,CAAC,EAAE,CAAC;QAC3B,CAAC,EAAE,CAAC;IACN,CAAC;IACD,UAAU,CAAC,cAAc,EAAE,SAAS,CAAC,CAAC;IACtC,OAAO,SAAS,CAAC;AACnB,CAAC;AAOD,SAAS,SAAS,CAAC,CAAS,EAAE,CAAS;IACrC,IAAI,MAAgB,CAAC;IACrB,IAAI,MAAgB,CAAC;IACrB,IAAI,CAAC;QACH,MAAM,GAAG,WAAW,CAAC,CAAC,CAAC,CAAC,IAAI,EAAE,CAAC;QAC/B,MAAM,GAAG,WAAW,CAAC,CAAC,CAAC,CAAC,IAAI,EAAE,CAAC;IACjC,CAAC;IAAC,MAAM,CAAC;QACP,OAAO,KAAK,CAAC;IACf,CAAC;IACD,IAAI,MAAM,CAAC,MAAM,KAAK,MAAM,CAAC,MAAM;QAAE,OAAO,KAAK,CAAC;IAClD,KAAK,IAAI,CAAC,GAAG,CAAC,EAAE,CAAC,GAAG,MAAM,CAAC,MAAM,EAAE,CAAC,EAAE,EAAE,CAAC;QACvC,IAAI,MAAM,CAAC,CAAC,CAAC,KAAK,MAAM,CAAC,CAAC,CAAC;YAAE,OAAO,KAAK,CAAC;QAC1C,MAAM,EAAE,GAAG,IAAI,CAAC,CAAC,EAAE,MAAM,CAAC,CAAC,CAAE,CAAC,CAAC;QAC/B,MAAM,EAAE,GAAG,IAAI,CAAC,CAAC,EAAE,MAAM,CAAC,CAAC,CAAE,CAAC,CAAC;QAC/B,MAAM,EAAE,GAAG,SAAS,CAAC,EAAE,CAAC,CAAC;QACzB,MAAM,EAAE,GAAG,SAAS,CAAC,EAAE,CAAC,CAAC;QACzB,IAAI,EAAE,CAAC,cAAc,EAAE,IAAI,EAAE,CAAC,cAAc,EAAE;YAAE,OAAO,KAAK,CAAC;QAC7D,IAAI,EAAE,CAAC,WAAW,EAAE,KAAK,EAAE,CAAC,WAAW,EAAE;YAAE,OAAO,KAAK,CAAC;QACxD,IAAI,EAAE,CAAC,WAAW,EAAE,EAAE,CAAC;YACrB,IAAI,CAAC,SAAS,CAAC,EAAE,EAAE,EAAE,CAAC;gBAAE,OAAO,KAAK,CAAC;QACvC,CAAC;aAAM,CAAC;YACN,IAAI,EAAE,CAAC,IAAI,KAAK,EAAE,CAAC,IAAI;gBAAE,OAAO,KAAK,CAAC;YACtC,IAAI,CAAC,YAAY,CAAC,EAAE,CAAC,CAAC,MAAM,CAAC,YAAY,CAAC,EAAE,CAAC,CAAC;gBAAE,OAAO,KAAK,CAAC;QAC/D,CAAC;IACH,CAAC;IACD,OAAO,IAAI,CAAC;AACd,CAAC"}

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@younndai/lyt-skills",
-  "version": "0.9.5",
-  "description": "Lyt harness skills — 15 skills (/lyt-plan, /lyt-progress, /lyt-result, /lyt-retro, /lyt-insight, /lyt-handoff, /lyt-decision, /lyt-pattern, /lyt-capture, /lyt-recall, /lyt-pod, /lyt-mesh-explore, /lyt-primer-context, /lyt-search, /lyt-sync) symlinked tri-runtime into ~/.claude/skills/, ~/.codex/skills/, ~/.agents/skills/. Composed into the `lyt skills install` and `lyt skills list` meta-CLI verbs.",
+  "version": "0.9.7",
+  "description": "Lyt harness skills — 16 skills (/lyt-plan, /lyt-progress, /lyt-result, /lyt-retro, /lyt-insight, /lyt-handoff, /lyt-decision, /lyt-pattern, /lyt-capture, /lyt-recall, /lyt-pod, /lyt-mesh-explore, /lyt-primer-context, /lyt-search, /lyt-sync, /lyt-alias) symlinked tri-runtime into ~/.claude/skills/, ~/.codex/skills/, ~/.agents/skills/. Composed into the `lyt skills install` and `lyt skills list` meta-CLI verbs.",
   "homepage": "https://linkyourthink.com",
   "repository": {
     "type": "git",
@@ -49,7 +49,7 @@
     "prepublishOnly": "node ../../scripts/check-no-vendored-deps.mjs --root ../.. && node ../../scripts/public-release/scan-tarball.mjs lyt-skills"
   },
   "dependencies": {
-    "@younndai/lyt-vault": "^0.9.5",
+    "@younndai/lyt-vault": "^0.9.7",
     "commander": "^12.1.0"
   },
   "devDependencies": {

package/skills/lyt-alias/SKILL.md

@@ -0,0 +1,92 @@
+---
+name: lyt-alias
+description: >
+  Manage pod-local vault aliases — bind a short handler-chosen name to a vault (alias → rid; survives rename + move), list the bindings, re-point one, or remove one. Trigger when the user runs /lyt-alias, or says "alias this vault as X", "give <vault> a short name", "what aliases do I have", "list my aliases", "rename my alias", "re-point alias X", "remove alias X", "drop the alias for X". Wraps `lyt alias <name> <target>` / `lyt alias --list` / `lyt alias --remove <name>` (all `--json`). Aliases are pod-local: synced across your own pod's machines, never to subscribers. Read-only on the target — works on a subscribed/read-only vault. Pairs with /lyt-pod and /lyt-search (which resolve `@alias` addresses).
+visibility: public
+lyt-version: 0.9.5
+capabilities: [read, write]
+runtimes: [claude, codex, agents]
+requires_writable_vault: false
+---
+
+# /lyt-alias
+
+Manage **pod-local aliases** — a short, handler-chosen name that resolves to a vault. An alias binds a name to the vault's **`rid` (its UUIDv7 identity)**, not to its `{mesh}/{vault}` display name, so the alias keeps working after the vault is renamed or moved between meshes. Aliases are a convenience layer over the one addressing chokepoint every `lyt` verb resolves through (`{mesh}/{vault}` → bare leaf → alias → origin coordinate).
+
+This skill is pure prose around three existing CLI forms of one verb — it adds no new command and changes no `lyt-vault` code:
+
+- `lyt alias <name> <target>` — **set / re-point** (bind, or rebind, `name` → the vault `target` resolves to)
+- `lyt alias --list` (or bare `lyt alias`) — **list** every pod-local alias
+- `lyt alias --remove <name>` — **remove** an alias
+
+All three accept `--json` for a machine-readable emission. The CLI does the resolution and validation; this skill resolves the user's intent into the right form, runs it (preferring `--json`), and formats the result for the handler.
+
+**Pod-local, never federated.** Aliases live in your local registry and sync across **your own pod's** machines — they are filtered out of the publish surface, so a subscriber never sees them. They are per-pod, individual naming. (Mechanically each set/remove appends a convergent `@ALIAS` record to this writer's own append-only shard, HLC-stamped, so re-point and remove converge correctly across your machines — but that is invisible at the skill surface.)
+
+## When to invoke
+
+When the user runs `/lyt-alias [...]`, or says something like:
+
+- "alias `<vault>` as `<name>`" / "give `<mesh>/<vault>` the short name `<name>`" — _set_
+- "what aliases do I have" / "list my aliases" / "show my pod-local names" — _list_
+- "re-point `<name>` to `<other-vault>`" / "make `<name>` point at `<vault>` instead" — _re-point (same as set)_
+- "remove the alias `<name>`" / "drop my `<name>` alias" / "unbind `<name>`" — _remove_
+
+If the user wants to browse what vaults exist (to pick a target), prefer `/lyt-pod`. If they want to search content, prefer `/lyt-search`. This skill only manages the name→vault bindings.
+
+## Phase 1 — Classify the intent
+
+Pick the form from the user's wording:
+
+1. **Set / re-point** — a `name` AND a `target` are present ("alias `ro` to `company/company-ro`"). Re-pointing is the same verb: running `lyt alias <name> <newtarget>` again supersedes the prior binding (the fold is a name-keyed register — no separate "rename" verb, no need to remove first).
+2. **List** — no name given, or the user asks to see bindings.
+3. **Remove** — the user wants a binding gone.
+
+If the user names a target ambiguously, resolve it the way the CLI will (see Phase 2) rather than guessing.
+
+## Phase 2 — Validate the inputs you control
+
+The CLI enforces these and will error cleanly, but check first so you can ask instead of emitting a failed command:
+
+- **Alias `name`** must be non-empty, contain **no `/`** (slash is reserved for `{mesh}/{vault}`), **no whitespace**, and **must not start with `@`**. The `@` is the chat-surface sigil — an address like `@ro` resolves to the alias `ro`; aliases are stored **raw** (sigil-free), so a leading `@` is rejected at the write boundary. If the user says "alias it as `@ro`", store `ro` and explain `@ro` is how they'll _reference_ it.
+- **`target`** (for set) may be a `{mesh}/{vault}` qualified address, a **bare leaf** (unique vault name across meshes), or **another alias**. It is resolved through the addressing chokepoint; if it resolves to nothing the CLI raises `alias-target-not-found` (exit 2). Surface that to the user with `lyt vault list` as the next step — don't retry blindly.
+
+## Phase 3 — Run the verb
+
+Prefer `--json` so you parse a typed result rather than scraping prose.
+
+```bash
+# set / re-point
+lyt alias <name> <target> --json        # → { alias, vaultRidHex, targetDisplayName }
+
+# list
+lyt alias --list --json                  # → { aliases: [{ alias, vaultRidHex, targetDisplayName }] }
+
+# remove
+lyt alias --remove <name> --json         # → { removed: <bool>, alias }
+```
+
+## Phase 4 — Present the result
+
+- **Set / re-point:** confirm the binding, e.g. _"Aliased `ro` → `company/company-ro` (`vault:0a1b…`). Reference it anywhere as `@ro` or `ro`."_ If it was a re-point, say what it now points at.
+- **List:** render one line per alias — `name → targetDisplayName (vault:<ridHex>)`. If `targetDisplayName` is **`(dangling — target removed)`**, flag it: the target vault is gone but the binding lingers — offer `lyt alias --remove <name>`. If there are none, say so and show the set form.
+- **Remove:** confirm removal. If `removed` is `false` (no such alias), tell the user plainly — don't claim success.
+
+## Notes on lifecycle
+
+- **Aliases self-clean on vault teardown.** When a vault is removed via `lyt vault delete` / `lyt vault forget`, every pod-local alias pointing at it is **warned about and dropped** as part of that flow — you don't need to pre-remove aliases before deleting a vault. (`lyt vault disconnect` does _not_ drop aliases; it only flips a status flag.)
+- **Re-point and remove converge across your pod's machines** by HLC-LWW — the newest set/remove wins per name. After a cross-machine change, a reconstitution (`lyt reindex` / the next sync-driven cache rebuild) refreshes the derived cache; the ledger is the source of truth.
+
+## Rules
+
+- **Never invent a target.** If the user's target doesn't resolve, surface the CLI's `alias-target-not-found` error and point them at `lyt vault list` — do not silently pick a different vault.
+- **Strip the `@` sigil before storing.** Store `ro`, never `@ro`. Explain the `@` is for referencing.
+- **Don't gate on vault writability.** Aliases are your own pod-local registry; you can alias a read-only or subscribed vault. `requires_writable_vault` is false by design.
+- **Prefer `--json`** and report the typed fields; don't paraphrase a binding you didn't read back.
+- **Removal/re-point is not destructive to the vault** — it only changes a local name binding. No handler-confirmation gate is required for alias set/list/remove (unlike `vault delete`/`forget`).
+
+## Companion skills
+
+- `/lyt-pod` — enumerate the vaults you might alias (and pick a target).
+- `/lyt-search` — query across the pod; resolves `@alias` addresses.
+- `/lyt-sync` — propagate alias changes across your pod's machines.

package/skills/lyt-capture/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: lyt-capture
 description: >
-  Capture a Figment (a markdown note) into a Lyt vault under the 8-field frontmatter contract. Trigger when the user runs /lyt-capture, or says "save this", "capture this", "add to my vault", "remember this in Lyt", or similar phrasing on content they want kept in their Lyt vault. Writes an Obsidian-flavored markdown file under <vault>/notes/ with frontmatter (title, created, modified, tags, purpose, topic, mesh-visibility, weight, meta) per yai.lyt v1 (arc §3). Wraps `lyt pattern run knowledge-capture capture` under the hood. Companion to lyt-recall.
+  Capture a Figment (a markdown note) into a Lyt vault under the 8-field frontmatter contract. Trigger when the user runs /lyt-capture, or says "save this", "capture this", "add to my vault", "remember this in Lyt", or similar phrasing on content they want kept in their Lyt vault. Writes an Obsidian-flavored markdown file under <vault>/notes/ with frontmatter (title, created, modified, tags, purpose, topic, mesh-visibility, weight, meta) per yai.lyt v1. Wraps `lyt pattern run knowledge-capture capture` under the hood. Companion to lyt-recall.
 visibility: public
 lyt-version: 0.2.0
 capabilities: [write]
@@ -45,7 +45,7 @@ A `--vault` argument may be a `{mesh}/{vault}` name, a bare leaf (resolved to a
 
 ## Phase 2 — Build the Figment under the v1 8-field contract
 
-Per yai.lyt v1 frontmatter contract (arc §3), every captured Figment carries 8 mandatory frontmatter fields plus a `meta:` escape hatch.
+Per yai.lyt v1 frontmatter contract, every captured Figment carries 8 mandatory frontmatter fields plus a `meta:` escape hatch.
 
 1. **Determine a title.** Use the user's explicit title if given. Otherwise infer a short noun-phrase (5–8 words) from the content. If unsure, ask.
 2. **Compute the slug** — lowercase, kebab-case the title, strip non-`[a-z0-9-]` characters, max 60 chars.
@@ -64,7 +64,7 @@ Per yai.lyt v1 frontmatter contract (arc §3), every captured Figment carries 8
 | `mesh-visibility` | default `local`                       | one of `local` / `parent` / `public` — ask only if user signals a non-default visibility |
 | `weight`          | default `3`                           | int 1–5 importance signal — ask only if user signals a non-default weight                |
 
-**Do NOT author-fill `links-out-of-vault`.** That field is reserved for the lyt scanner (block-B); it is intentionally absent at capture-write time. The contract is "scanner-filled, not author-filled."
+**Do NOT author-fill `links-out-of-vault`.** That field is reserved for the lyt scanner; it is intentionally absent at capture-write time. The contract is "scanner-filled, not author-filled."
 
 The `meta:` blob is a free-form escape hatch (`{}` by default) — fill it only when the content carries a field the 8-field contract does not cover.
 

package/skills/lyt-decision/SKILL.md

@@ -18,7 +18,7 @@ Record a locked decision — the choice, the alternatives, the reasoning. Use wh
 - `/lyt-decision` slash trigger
 - "lock this decision"
 - "we decided X — record it"
-- after a `/insight-assess` or `/insight-adversarial` lands a locked verdict
+- after a structured assessment or review lands a locked verdict
 - before starting work whose direction depends on a non-obvious choice
 
 ## Phase 1 — Resolve target

package/skills/lyt-handoff/SKILL.md

@@ -41,12 +41,12 @@ A good handoff has:
 - **Sources (@SOURCES.required + .optional)** — every file the next agent MUST read before drafting any plan
 - **Resume command** — numbered steps the next agent should follow
 - **Sign-off** — canonical retro path; structured @SESSION_REPORT format if applicable
-- **Activation phrase** — the `/handoff-execute "..."` command to paste into the fresh session
+- **Activation phrase** — the prompt to paste into the fresh session to resume the work
 
-The frontmatter `acceptance` field is load-bearing: the executing agent (via `/handoff-execute`) walks its clauses to verify the work matches the brief.
+The frontmatter `acceptance` field is load-bearing: the executing agent walks its clauses to verify the work matches the brief.
 
 ## Companion skills
 
-- `/handoff-execute` (in the handoff-execute skill) — consumes briefs written by this skill
+- a fresh agent session — consumes the brief written by this skill
 - `/lyt-result` — what the prior session shipped (context for the handoff)
 - `/lyt-retro` — usually written alongside or after the next-session retro

package/skills/lyt-mesh-explore/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: lyt-mesh-explore
 description: >
-  Drill into a single Lyt mesh — surface mesh metadata, member home vaults, update cadences, and the published @MESH_PUBLIC description for one named mesh. Trigger when the user runs /lyt-mesh-explore <mesh>, or says "show me the X mesh", "what's in mesh X", "drill into X mesh", "explore the X mesh", "give me X mesh details", or similar phrasing on mesh-scoped browsing. Wraps `lyt mesh info <mesh> [--remote] [--json]` (v1.B.6) — local mode reads the mesh's `.lyt/mesh.yon` SoT; `--remote` peeks at the published mesh.yon via gh api without cloning. Read-only; pairs with /lyt-pod (pod-level enumeration across all meshes) for breadth and /lyt-search (tiered query) for content.
+  Drill into a single Lyt mesh — surface mesh metadata and member home vaults for one named mesh. Trigger when the user runs /lyt-mesh-explore <mesh>, or says "show me the X mesh", "what's in mesh X", "drill into X mesh", "explore the X mesh", "give me X mesh details", or similar phrasing on mesh-scoped browsing. Wraps `lyt mesh info <mesh> [--remote] [--json]` — local mode reads the mesh's `.lyt/mesh.yon` SoT; `--remote` peeks at the remote mesh.yon via gh api without cloning. Read-only; pairs with /lyt-pod (pod-level enumeration across all meshes) for breadth and /lyt-search (tiered query) for content.
 visibility: public
 lyt-version: 0.8.0
 capabilities: [read]
@@ -11,12 +11,14 @@ requires_writable_vault: false
 
 # /lyt-mesh-explore
 
-Render a handler-facing overview of a single Lyt **mesh** — its metadata, its home vaults, its update cadences, and its published `@MESH_PUBLIC` description — by wrapping one primary CLI verb (plus an upstream `lyt mesh list --json` for mesh-name resolution per Phase 1):
+Render a handler-facing overview of a single Lyt **mesh** — its metadata and its home vaults — by wrapping one primary CLI verb (plus an upstream `lyt mesh list --json` for mesh-name resolution per Phase 1):
 
-- `lyt mesh info <mesh> [--remote] [--json]` (shipped v1.B.6). Canonical mesh-info verb per `packages/lyt-vault/src/commands/mesh-info.ts:20` (definition; registered at `commands/mesh.ts:37`). Local mode reads the registered mesh's main-vault `.lyt/mesh.yon` SoT; `--remote` peeks at the published mesh.yon via `gh api repos/<owner>/<mesh-main>/contents/.lyt/mesh.yon` without cloning the repo.
+- `lyt mesh info <mesh> [--remote] [--json]`. The canonical mesh-info verb. Local mode reads the registered mesh's main-vault `.lyt/mesh.yon` source of truth; `--remote` peeks at the published mesh.yon via `gh api repos/<owner>/<mesh-main>/contents/.lyt/mesh.yon` without cloning the repo.
 
 The skill is pure prose around existing CLI verbs — no new CLI verb, no new helper, no lyt-vault change. The CLI does the parsing (mesh.yon → typed `MeshInfoResult`); the skill resolves the user's intent (mesh name + local-or-remote), invokes the verb with `--json`, and formats the deterministic emission into a handler-facing mesh summary.
 
+> **Note:** `publicMeta`, `updateCadences`, and `defaultVaultUpdateCadence` were removed from `MeshInfoResult`. The JSON schema and rendering template below reflect the current post-deletion shape.
+
 User-facing language uses **"mesh"** throughout per the LYT vocabulary convention — "pod" is reserved for the user's _full_ set of meshes (which is `/lyt-pod`'s scope); "mesh" is the individual group of vaults sharing a GitHub push target.
 
 ## When to invoke
@@ -42,12 +44,12 @@ The CLI verb takes one required positional `<mesh>` (the mesh name). Pick by the
 
 **Resolve the candidate against `lyt mesh list --json` before passing it.** Don't guess — when the user names a mesh:
 
-1. Run `lyt mesh list --json` first (canonical mesh-enumeration verb per `packages/lyt-vault/src/commands/mesh.ts:277` — `buildMeshListSubcommand` definition; registered at `commands/mesh.ts:32`). The output's `meshes[].name` field is the source of truth for registered mesh names.
+1. Run `lyt mesh list --json` first (the canonical mesh-enumeration verb). The output's `meshes[].name` field is the source of truth for registered mesh names.
 2. Match the user's term to the listed names (exact, then case-insensitive, then prefix).
-3. **Reject any resolved name that begins with `-` or `--`** before passing it to the positional `<mesh>` argument — closes the flag-injection surface the same way lyt-sync, lyt-search, and lyt-pod close theirs (family: G.2 CR-1 gh-flag-injection). Mesh names are user-controlled at `lyt mesh init` time; a mesh literally named `--evil` would otherwise smuggle a flag-shaped token into the verb's argv.
+3. **Reject any resolved name that begins with `-` or `--`** before passing it to the positional `<mesh>` argument — closes the flag-injection surface the same way lyt-sync, lyt-search, and lyt-pod close theirs (the gh-flag-injection defense family). Mesh names are user-controlled at `lyt mesh init` time; a mesh literally named `--evil` would otherwise smuggle a flag-shaped token into the verb's argv.
 4. If no match (or the only match is `--`-leading), tell the user the available mesh names from `lyt mesh list --json` and stop — do not invent a name.
 
-**Decide `--remote` from explicit user signal only.** Pass `--remote` ONLY when the user explicitly says "without cloning" / "from GitHub" / "peek at the published mesh.yon" / "remote mesh info". The default is LOCAL invocation (no `--remote`) — it reads the locally-registered mesh's `.lyt/mesh.yon` SoT, which is faster, offline-safe, and authoritative for meshes the user owns. `--remote` requires the mesh to be registered locally with a `push_target` (the verb resolves the remote owner from the registry; it does NOT take a `--owner` override in v1.B.6).
+**Decide `--remote` from explicit user signal only.** Pass `--remote` ONLY when the user explicitly says "without cloning" / "from GitHub" / "peek at the published mesh.yon" / "remote mesh info". The default is LOCAL invocation (no `--remote`) — it reads the locally-registered mesh's `.lyt/mesh.yon` SoT, which is faster, offline-safe, and authoritative for meshes the user owns. `--remote` requires the mesh to be registered locally with a `push_target` (the verb resolves the remote owner from the registry; it does NOT take a `--owner` override).
 
 ## Phase 2 — Invoke `lyt mesh info`
 
@@ -70,7 +72,7 @@ Key rules:
 - `--json` is **mandatory** for this skill. The deterministic JSON emission is the contract the skill parses below; human-readable output is not.
 - `--remote` is a boolean flag; pass it (or omit) per the Phase 1 decision. Never pass `--remote=true` or `--remote=<anything>` — the flag is bare.
 
-The CLI emits Lock 0.3 stable-key-ordered JSON on stdout (exit 0 on success). The actual emitted shape (per `packages/lyt-vault/src/flows/mesh-info.ts:103-118`, the `MeshInfoResult` interface — `mesh-info.ts:40` does `JSON.stringify(result, null, 2)` verbatim with no transformation, so the TypeScript shape IS the JSON contract):
+The CLI emits stable, deterministically key-ordered JSON on stdout (exit 0 on success). The emitted shape (the `MeshInfoResult` interface):
 
 ```json
 {
@@ -82,33 +84,8 @@ The CLI emits Lock 0.3 stable-key-ordered JSON on stdout (exit 0 on success). Th
     "pushTarget": "<gh-target>" | null,
     "pushKind": "handle" | "org" | null,
     "mainVaultRid": "vault:<uuid-dashed>",
-    "createdAt": "<iso>",
-    "defaultVaultUpdateCadence": "<cadence-string>" | null
-  },
-  "publicMeta": {
-    "description": "<string>",
-    "topics": "<comma-separated>",
-    "maintainerContact": "<string>",
-    "maintainerHandle": "<string>",
-    "licenseOverride": "<spdx-id>",
-    "acceptContributions": true,
-    "contributionUrl": "<url>",
-    "homepageUrl": "<url>",
-    "chatUrl": "<url>",
     "createdAt": "<iso>"
-  } | null,
-  "updateCadences": [
-    {
-      "vaultRid": "vault:<uuid-dashed>",
-      "vaultRidHex": "<hex>",
-      "cadenceType": "cron" | "interval" | "on-demand",
-      "cron": "<expr>",
-      "intervalSeconds": <number>,
-      "timezone": "<tz>",
-      "peakHours": "<expr>",
-      "onDemandAllowed": <boolean>
-    }
-  ],
+  },
   "homeVaults": [
     {
       "vaultRid": "vault:<uuid-dashed>",
@@ -119,13 +96,11 @@ The CLI emits Lock 0.3 stable-key-ordered JSON on stdout (exit 0 on success). Th
 }
 ```
 
-Within `publicMeta` and `updateCadences[]`, every field except `description` (in publicMeta) and `vaultRid` / `vaultRidHex` / `cadenceType` (in updateCadences[]) is omitted from the emission when undefined — they are conditional object-literal spreads at flow-emission time. Treat missing keys as "field not set on this mesh", not "field is null".
-
 Failure modes (CLI emits to stderr; exits non-zero):
 
 - **Mesh not registered locally** (`MeshInfoNotFoundError`, exit 2) → `{ "error": "mesh-info-not-found", "mesh_name": "<name>", "message": "..." }`. Surface the message verbatim and suggest `lyt mesh list --json` to see registered meshes.
 - **--remote requested, gh unavailable** (`MeshInfoRemoteGhUnavailableError`, exit 4) → `{ "error": "remote-gh-unavailable", "mesh_name": "<name>", "message": "..." }`. Most common causes: the mesh has no `push_target` (initialized with `--no-push`), or `gh` is not authenticated. Surface the message and suggest dropping `--remote` to fall back to LOCAL mode.
-- **--remote requested, remote mesh.yon missing** (`MeshInfoRemoteMeshYonMissingError`, exit 4) → `{ "error": "remote-mesh-yon-missing", "mesh_name": "<name>", "message": "..." }`. The remote repo exists but `.lyt/mesh.yon` is absent at the repo root — the mesh has not yet been published via `lyt mesh publish`. Surface verbatim and suggest LOCAL mode.
+- **--remote requested, remote mesh.yon missing** (`MeshInfoRemoteMeshYonMissingError`, exit 4) → `{ "error": "remote-mesh-yon-missing", "mesh_name": "<name>", "message": "..." }`. The remote repo exists but `.lyt/mesh.yon` is absent at the repo root. Surface verbatim and suggest LOCAL mode.
 
 ## Phase 3 — Format mesh-overview for handler
 
@@ -139,43 +114,27 @@ Render the mesh summary as a markdown block. The handler-facing layout:
 - push target: `<mesh.pushKind>:<mesh.pushTarget>`     (omit line when pushTarget is null)
 - main vault rid: `<mesh.mainVaultRid>`
 - created: `<mesh.createdAt>`
-- default cadence: `<mesh.defaultVaultUpdateCadence>`  (omit line when null)
-
-**Public description:** (omit entire block when publicMeta is null)
-- description: <publicMeta.description>
-- topics: <publicMeta.topics>                          (omit when undefined)
-- maintainer: <publicMeta.maintainerContact>           (omit when undefined)
-- license: <publicMeta.licenseOverride>                (omit when undefined)
-- homepage: <publicMeta.homepageUrl>                   (omit when undefined)
-- chat: <publicMeta.chatUrl>                           (omit when undefined)
 
 **Home vaults:** (count = homeVaults.length)
 - ★ `<main-vault-name>` (`vault:<vaultRidHex>`)        — main vault, marked ★
 - `<vault-name>` (`vault:<vaultRidHex>`)
 - ...
-
-**Update cadences:** (count = updateCadences.length; omit entire block when length is 0)
-- `<vault-ridHex truncated to 12 chars>…` — <cadenceType> <detail>
-- ...
 ```
 
 Synthesis rules:
 
 - **Source line.** Render `(local)` or `(remote)` next to the mesh name based on `source` — handlers seeing the rendered output should know whether they're looking at on-disk SoT or a remote peek.
-- **Main-vault marker.** The home vault whose `vaultRid` equals `mesh.mainVaultRid` is the main vault — render it first with a `★` marker (parity with `lyt mesh list`'s human output per `packages/lyt-vault/src/commands/mesh.ts:333`). Other home vaults follow, sorted alphabetically by `vaultName`. Do not double-render the main vault.
-- **Cadence detail.** For `cadenceType: "cron"`, render the `cron` expression. For `"interval"`, render `every <intervalSeconds>s`. For `"on-demand"`, render `on-demand`. Truncate `vaultRidHex` to the first 12 chars with `…` for readability (parity with `mesh-info.ts:104`).
-- **Optional-field omission.** Treat absent keys in `publicMeta` + `updateCadences[]` as "field not set on this mesh"; omit those lines entirely rather than rendering `undefined` or `null` placeholders.
-- **No edges / subscriptions sections.** `lyt mesh info` surfaces mesh metadata + publicMeta + home vaults + update cadences ONLY — it does not emit mesh-edges (`@MESH_EDGE`) or cross-mesh subscriptions (`@MESH_SUBSCRIPTION`). Those are inspected via other surfaces (`lyt mesh list` exposes per-mesh `subscribed_vaults`; mesh-edges live in `.lyt/mesh.yon` but are not surfaced by this verb). Do NOT invent edge / subscription bullets — the verb does not expose them. Mention `/lyt-pod` as the path to subscription overview if the user asks.
-- **Empty publicMeta.** When `publicMeta === null`, the mesh was initialized without a `@MESH_PUBLIC` block. Omit the entire "Public description" section — do NOT render an empty heading.
+- **Main-vault marker.** The home vault whose `vaultRid` equals `mesh.mainVaultRid` is the main vault — render it first with a `★` marker (parity with `lyt mesh list`'s human output). Other home vaults follow, sorted alphabetically by `vaultName`. Do not double-render the main vault.
+- **No edges / subscriptions sections.** `lyt mesh info` surfaces mesh metadata + home vaults ONLY — it does not emit mesh-edges (`@MESH_EDGE`) or cross-mesh subscriptions. Those are inspected via other surfaces (`lyt mesh list` exposes per-mesh `subscribed_vaults`). Do NOT invent edge / subscription bullets — the verb does not expose them. Mention `/lyt-pod` as the path to subscription overview if the user asks.
 - **Use "mesh" framing throughout.** Never write "federation" or "pod" in this skill's user-facing prose. "Mesh" is the unit of grouping; "pod" is the user's full set of meshes (different scope; that's `/lyt-pod`'s domain).
-- **Remote-mode caveat.** When `source === "remote"`, the data is whatever the remote `.lyt/mesh.yon` currently advertises — it may be stale relative to the mesh's owner's local state if they haven't run `lyt mesh publish` recently. Mention this when the user explicitly asked for `--remote`, so they know what they're looking at.
+- **Remote-mode caveat.** When `source === "remote"`, the data is whatever the remote `.lyt/mesh.yon` currently advertises — it may be stale relative to the mesh's owner's local state if they haven't pushed recently. Mention this when the user explicitly asked for `--remote`, so they know what they're looking at.
 
 ## Rules
 
 - **MUST pass the mesh name as a separate argv argument**, not template-interpolated into a shell command string. Mesh names are user-controlled at init time; argv-array protects against shell-meta or flag-shaped tokens.
 - **MUST pass `--json`** on every invocation. Human-readable output is not a contract this skill parses.
-- **MUST resolve mesh names via `lyt mesh list --json` before passing them.** The canonical mesh-enumeration verb is `lyt mesh list` per `packages/lyt-vault/src/commands/mesh.ts:277` (`buildMeshListSubcommand` definition; registered at `commands/mesh.ts:32`). Do not guess names.
-- **MUST reject `--`-leading resolved mesh names** before passing them to the positional `<mesh>` argument (G.2 CR-1 flag-injection family defense).
+- **MUST resolve mesh names via `lyt mesh list --json` before passing them.** The canonical mesh-enumeration verb is `lyt mesh list`. Do not guess names.
+- **MUST reject `--`-leading resolved mesh names** before passing them to the positional `<mesh>` argument (the flag-injection defense family).
 - **MUST NOT cite `lyt mesh status`** as a verb. It does not exist. The canonical mesh-listing verb is `lyt mesh list`; the canonical single-mesh-inspection verb is `lyt mesh info` (this skill).
 - **MUST NOT modify or write any vault file.** This is a read-only skill (`requires_writable_vault: false`). If the user wants the mesh overview persisted to a Figment, run `/lyt-capture` separately on the formatted output.
 - **MUST NOT pass `--remote` by default.** LOCAL is the default; pass `--remote` only on explicit user signal ("without cloning", "from GitHub", "peek at the published mesh.yon", "remote").

package/skills/lyt-pod/SKILL.md

@@ -13,8 +13,8 @@ requires_writable_vault: false
 
 Render an agent-facing overview of the user's Lyt **pod** — every mesh and every vault on this machine — by composing two CLI verbs:
 
-1. `lyt mesh list --json` (shipped v1.B.1) — enumerates meshes the user participates in, including each mesh's main vault, home vaults, and subscribed vaults. Canonical mesh-enumeration verb per `packages/lyt-vault/src/commands/mesh.ts:277` (`buildMeshListSubcommand`).
-2. `lyt vault list --json` (shipped pre-v1.G.1) — enumerates every registered vault on the machine, with status, path, and per-vault metadata (mesh role, parent vault, tier hint). Canonical vault-enumeration verb per `packages/lyt-vault/src/commands/list.ts:6` (`buildListCommand`).
+1. `lyt mesh list --json` — enumerates meshes the user participates in, including each mesh's main vault, home vaults, and subscribed vaults. This is the canonical mesh-enumeration verb.
+2. `lyt vault list --json` — enumerates every registered vault on the machine, with status, path, and per-vault metadata (mesh role, parent vault, tier hint). This is the canonical vault-enumeration verb.
 
 The skill is pure prose around two existing CLI verbs — there is no new CLI verb, no new helper, no lyt-vault change. Both verbs always run on every invocation (default = full pod overview); user signal can narrow the synthesis focus post-facto but does NOT change which verbs run.
 
@@ -35,7 +35,7 @@ When the user runs `/lyt-pod`, or says something like:
 
 Invoke this skill **proactively** as the first move whenever the user asks a pod-scoped enumeration question or seems to want a survey of what's installed. Don't bypass it and start grep'ing the filesystem — the registry is the source of truth.
 
-If the user wants to drill into a single mesh (vault list + edges for one mesh), prefer `/lyt-mesh-explore` (post-Wave-3 G.9) once it ships. If the user wants per-vault writable status or agent priming, use `/lyt-primer-context`.
+If the user wants to drill into a single mesh (vault list + edges for one mesh), prefer `/lyt-mesh-explore`. If the user wants per-vault writable status or agent priming, use `/lyt-primer-context`.
 
 ## Phase 1 — Determine pod-scope intent
 
@@ -43,7 +43,7 @@ The default is **full pod overview** — both verbs run, every mesh and vault re
 
 - **Default — full pod overview.** Use when the user says "my pod", "show me everything", "list all vaults", "what meshes do I have", or omits scope entirely. Run both verbs (Phase 2 + Phase 3) and synthesize a complete pod summary in Phase 4.
 - **Narrow framing on a single mesh.** Use when the user says "focus on the `<name>` mesh", "just show me the `<name>` mesh's vaults", "what's in the `<name>` mesh". **Still run BOTH `lyt mesh list --json` and `lyt vault list --json`** — the CLI verbs do not support `--mesh` filtering on `lyt vault list`. Apply the user's narrow framing at **synthesis time** (Phase 4) by filtering the rendered output. Do NOT invent a CLI flag.
-- **Tombstoned-vault inclusion.** Default = hide soft-tombstoned rollup aggregates (matches CLI default per `packages/lyt-vault/src/commands/list.ts:11-19`). Pass `--include-tombstones` ONLY when the user explicitly says "show tombstoned vaults too", "include deleted vaults", "show buried vaults". Hard-tombstoned vaults (`status='tombstoned'`) are included in the default `lyt vault list` output already; `--no-tombstones` filters them out (do NOT pass by default — they are part of the pod's recent history).
+- **Tombstoned-vault inclusion.** Default = hide soft-tombstoned rollup aggregates (matches the CLI default). Pass `--include-tombstones` ONLY when the user explicitly says "show tombstoned vaults too", "include deleted vaults", "show buried vaults". Hard-tombstoned vaults (`status='tombstoned'`) are included in the default `lyt vault list` output already; `--no-tombstones` filters them out (do NOT pass by default — they are part of the pod's recent history).
 
 The skill never invents mesh or vault names. If the user names one and the post-Phase-2/3 synthesis can't match it, surface the available names and stop — do not guess.
 
@@ -59,7 +59,7 @@ lyt mesh list --json
 spawnSync("lyt", ["mesh", "list", "--json"]);
 ```
 
-The CLI emits Lock 0.3 stable-key-ordered JSON on stdout (exit 0 on success). The actual emitted shape (per `packages/lyt-vault/src/commands/mesh.ts:283-317`):
+The CLI emits stable, deterministically key-ordered JSON on stdout (exit 0 on success). The emitted shape:
 
 ```json
 {
@@ -105,7 +105,7 @@ spawnSync("lyt", ["vault", "list", "--json"]);
 spawnSync("lyt", ["vault", "list", "--json", "--include-tombstones"]);
 ```
 
-The CLI emits Lock 0.3 stable-key-ordered JSON on stdout (per `packages/lyt-vault/src/commands/list.ts:46-49` + `packages/lyt-vault/src/flows/list.ts:32-40`):
+The CLI emits stable, deterministically key-ordered JSON on stdout:
 
 ```json
 {
@@ -136,7 +136,7 @@ The CLI emits Lock 0.3 stable-key-ordered JSON on stdout (per `packages/lyt-vaul
 }
 ```
 
-**Field-type note (release review).** The four byte-typed fields (`rid`, `memscopeRid`, `parentVault`, `homeMeshRid`) are `Uint8Array` instances at the source (`packages/lyt-vault/src/registry/repo.ts:22-32`) and pass through `JSON.stringify(result, null, 2)` raw at `commands/list.ts:48`. `JSON.stringify` serializes a `Uint8Array` as a **byte-indexed object** (`{"0": 123, "1": 45, ..., "15": 254}`), NOT a hex string. **Always match on the `*Hex` companion fields** (`ridHex`, `memscopeRidHex`, `parentVaultHex`, `homeMeshRidHex`) — those are guaranteed-string and stable. Treat the raw byte-fields as opaque implementation detail.
+**Field-type note.** The four byte-typed fields (`rid`, `memscopeRid`, `parentVault`, `homeMeshRid`) are `Uint8Array` instances at the source and pass through `JSON.stringify(result, null, 2)` raw. `JSON.stringify` serializes a `Uint8Array` as a **byte-indexed object** (`{"0": 123, "1": 45, ..., "15": 254}`), NOT a hex string. **Always match on the `*Hex` companion fields** (`ridHex`, `memscopeRidHex`, `parentVaultHex`, `homeMeshRidHex`) — those are guaranteed-string and stable. Treat the raw byte-fields as opaque implementation detail.
 
 The vault-list output is the source of truth for **per-vault mesh membership** — match each vault's `homeMeshRidHex` (string) against each mesh's `rid_hex` (string) from Phase 2 to group vaults under their mesh in Phase 4. A vault with `homeMeshRidHex === null` is an **orphan** (registered but not adopted into any mesh — see Phase 4's orphan section).
 
@@ -174,7 +174,7 @@ Render the pod summary as a markdown block. The handler-facing layout:
 Synthesis rules:
 
 - **Summary line.** `N meshes` = `meshes.length` from Phase 2. `M vaults` = `vaults.length` from Phase 3 (filter out `status='tombstoned'` unless the user explicitly asked for tombstoned inclusion). The `(P pushable · S subscriber · O orphan)` breakdown counts each vault **once** by primary role, with precedence **home > subscriber > orphan** (a vault appearing in BOTH a `home_vaults` array AND any `subscribed_vaults` array is counted as **home**, not subscriber): a vault is **pushable** if it appears in any mesh's `home_vaults` AND that mesh has a non-null `push_target`; **subscriber** if it appears ONLY in `subscribed_vaults` arrays across all meshes (never as a home vault); **orphan** if its `homeMeshRidHex === null` (no mesh role at all).
-- **Mesh grouping.** Sort meshes by name (alphabetical) for stable rendering. Within each mesh: main vault first (marked `★` per `commands/mesh.ts:333` precedent), then other home vaults sorted alphabetically (exclude the main-vault entry from this alphabetic list — it already rendered above with `★`; `home_vaults` includes the main vault per Phase 2 shape, so an LLM iterating the array verbatim would otherwise double-render the main vault), then subscribed vaults grouped at the end with a "subscribed (cross-mesh)" hint.
+- **Mesh grouping.** Sort meshes by name (alphabetical) for stable rendering. Within each mesh: main vault first (marked `★`), then other home vaults sorted alphabetically (exclude the main-vault entry from this alphabetic list — it already rendered above with `★`; `home_vaults` includes the main vault per Phase 2 shape, so an LLM iterating the array verbatim would otherwise double-render the main vault), then subscribed vaults grouped at the end with a "subscribed (cross-mesh)" hint.
 - **Push-target hint.** Surface `push target: <push_kind>:<push_target>` next to the main vault when `push_target !== null`. Skip the hint when null (mesh is local-only).
 - **Orphan section.** Always include the heading even when empty (rendering "(none)" under it) — handlers parsing the output can rely on the section's presence. Each orphan vault gets a one-line heal suggestion: `lyt repair --target <orphan-vault-name> --apply --mesh <mesh>` (the canonical heal — binds a registered vault to a known mesh). A vault that is _registered-but-mesh-unlinked_ (the adopt mesh-link drift) heals via `lyt repair --apply` with **no args** (`lyt doctor` flags it). `lyt mesh adopt` remains for gh **cluster-discovery** of un-registered repos — not for re-linking an already-registered vault.
 - **User narrow framing.** If the user signaled a single mesh in Phase 1, render only that mesh's section under `## Meshes` plus the orphan section. Surface a one-line "(showing 1 of N meshes — re-invoke /lyt-pod for full overview)" hint.
@@ -189,8 +189,8 @@ Synthesis rules:
 - **MUST run BOTH verbs on every invocation.** The default is full pod overview; even when the user signals a narrow mesh framing, the vault list is needed to compute the orphan section and the summary-line counts. Do not skip one verb to "save time" — synthesis quality drops.
 - **MUST use "pod" framing in user-facing output.** Never write "federation" in handler-facing prose; "federation" is internal data-layer vocabulary only.
 - **MUST surface the orphan-vault section** even when empty (render "(none)" under the heading) so handlers can rely on its presence.
-- **MUST cite `lyt mesh list` as the canonical mesh-enumeration verb.** Some sibling SKILL.md files cite a different mesh-enumeration verb that does not exist; the canonical verb is `lyt mesh list` per `packages/lyt-vault/src/commands/mesh.ts:277`. Do not propagate the sibling error here.
-- **MUST cite `lyt vault info <name>` with a positional argument only.** The verb accepts a positional `<name>` per `packages/lyt-vault/src/commands/info.ts:20-26`; the only flag is `--json`. The pod skill does not call `vault info` at all (per-vault writable status is `/lyt-primer-context`'s job — pulling it here would duplicate that surface).
+- **MUST cite `lyt mesh list` as the canonical mesh-enumeration verb.** The canonical verb is `lyt mesh list`. Do not invent a different mesh-enumeration verb.
+- **MUST cite `lyt vault info <name>` with a positional argument only.** The verb accepts a positional `<name>`; the only flag is `--json`. The pod skill does not call `vault info` at all (per-vault writable status is `/lyt-primer-context`'s job — pulling it here would duplicate that surface).
 - **MUST NOT pass `--include-tombstones` by default.** Pass only on explicit user signal ("show tombstoned vaults", "include deleted vaults", "show buried vaults"). Default = hide soft-tombstoned rollup aggregates per CLI default.
 - **MUST NOT pass `--no-tombstones` by default.** Hard-tombstoned vaults (`status='tombstoned'`) are part of the pod's recent history; rendering them with a `[tombstoned]` status marker is the correct default. Pass `--no-tombstones` only on explicit user signal ("hide tombstones", "skip buried vaults").
 - **MUST NOT modify or write any file.** This is a read-only skill (`requires_writable_vault: false`). If the user wants the pod overview persisted to a Figment, run `/lyt-capture` separately on the formatted output.
@@ -199,7 +199,7 @@ Synthesis rules:
 
 ## Companion skills
 
-- **/lyt-mesh-explore** — drill into a single mesh (vault list + edges + subscriptions). Pair after `/lyt-pod` when the user picks one mesh to investigate (post-Wave-3 G.9).
+- **/lyt-mesh-explore** — drill into a single mesh (vault list + edges + subscriptions). Pair after `/lyt-pod` when the user picks one mesh to investigate.
 - **/lyt-primer-context** — prime an agent with Lyt-scoped context (top keywords, active arcs, writable status). Pair after `/lyt-pod` when the user wants the agent to start working in a specific vault — use `--scope vault --target <name>` per the chosen vault.
 - **/lyt-search** — query across the pod with the tiered-cascade engine. Pair after `/lyt-pod` when the user wants to look up specific content rather than survey what exists.
 - **/lyt-sync** — pull/commit/push a vault. Run before `/lyt-pod` if the user has unpushed local edits and wants the registry to reflect them (registry rows update on vault init/adopt; `/lyt-sync` doesn't change the pod shape but does freshen `lastVerifiedAt`).

package/skills/lyt-primer-context/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: lyt-primer-context
 description: >
-  Prime an agent with Lyt-scoped context — for a vault, a mesh, or the whole pod — by composing `lyt primer` (top keywords + active arcs + recent activity + top lanes) and `lyt vault info --json` (writable status for vault-scope). Trigger when the user runs /lyt-primer-context, or says "prime me for X", "give me context on this vault", "what's been happening in my pod lately", "what arcs are active in mesh Y", "give the agent context before X", or similar phrasing on a scope they want surfaced for agent priming. Wraps `lyt primer` (v1.D.4) + `lyt vault info --json` (v1.G.2 6-reason writable contract) — composes both into an agent-facing summary. Read-only; pairs with /lyt-search (query-driven recall) and /lyt-capture (write).
+  Prime an agent with Lyt-scoped context — for a vault, a mesh, or the whole pod — by composing `lyt primer` (top keywords + active arcs + recent activity + top lanes) and `lyt vault info --json` (writable status for vault-scope). Trigger when the user runs /lyt-primer-context, or says "prime me for X", "give me context on this vault", "what's been happening in my pod lately", "what arcs are active in mesh Y", "give the agent context before X", or similar phrasing on a scope they want surfaced for agent priming. Wraps `lyt primer` + `lyt vault info --json` (6-reason writable contract) — composes both into an agent-facing summary. Read-only; pairs with /lyt-search (query-driven recall) and /lyt-capture (write).
 visibility: public
 lyt-version: 0.6.0
 capabilities: [read]
@@ -13,10 +13,10 @@ requires_writable_vault: false
 
 Prime an agent with Lyt-scoped context for a **vault**, a **mesh**, or the whole **pod** by composing two CLI verbs:
 
-1. `lyt primer --scope <vault|mesh|federation> [--target <name>] --json --dry-run` (shipped v1.D.4) — aggregates top keywords, active arcs, recent activity, and top lanes across the scope into a Lock 0.3 stable-key-ordered JSON payload (including the full primer markdown body).
-2. `lyt vault info <name> --json` (shipped v1.G.2; 6-reason writable contract) — only for vault-scope priming, fetches `writable` + `writableDetermination` so the skill can surface a capability hint to the agent ("you can /lyt-capture here" vs reason-specific guidance).
+1. `lyt primer --scope <vault|mesh|federation> [--target <name>] --json --dry-run` — aggregates top keywords, active arcs, recent activity, and top lanes across the scope into a stable, deterministically key-ordered JSON payload (including the full primer markdown body).
+2. `lyt vault info <name> --json` (6-reason writable contract) — only for vault-scope priming, fetches `writable` + `writableDetermination` so the skill can surface a capability hint to the agent ("you can /lyt-capture here" vs reason-specific guidance).
 
-The skill is pure prose around two existing CLI verbs — there is no new CLI verb, no new helper, no lyt-vault change. The skill READS; it does not write (except the CLI's atomic primer-file write on non-dry-run, which is opt-in per Phase 2 the ratified default).
+The skill is pure prose around two existing CLI verbs — there is no new CLI verb, no new helper, no lyt-vault change. The skill READS; it does not write (except the CLI's atomic primer-file write on non-dry-run, which is opt-in per Phase 2's default).
 
 ## When to invoke
 
@@ -42,9 +42,9 @@ The `lyt primer` verb requires `--scope` and rejects ambiguity. Pick by the user
 
 **Resolve names before passing them.** Don't guess at mesh/vault names — when the user names one:
 
-1. Run `lyt vault list --json` (vaults) or `lyt mesh list --json` (meshes) first. `lyt mesh list` is the canonical mesh-enumeration verb (per `packages/lyt-vault/src/commands/mesh.ts:32`); both verbs emit Lock 0.3 stable-key-ordered JSON on `--json`.
+1. Run `lyt vault list --json` (vaults) or `lyt mesh list --json` (meshes) first. `lyt mesh list` is the canonical mesh-enumeration verb; both verbs emit stable, deterministically key-ordered JSON on `--json`.
 2. Match the user's term to the listed names (exact, then case-insensitive, then prefix).
-3. **Reject any resolved name that begins with `-` or `--`** before passing it to `--target <name>` — closes the flag-injection surface the same way lyt-sync (Phase 1) and lyt-search (Phase 1) do (family: G.2 CR-1 gh-flag-injection). Vault and mesh names are user-controlled at vault-init / mesh-create time; a vault literally named `--evil` would otherwise smuggle a flag-shaped token into the verb's argv.
+3. **Reject any resolved name that begins with `-` or `--`** before passing it to `--target <name>` — closes the flag-injection surface the same way lyt-sync (Phase 1) and lyt-search (Phase 1) do (the gh-flag-injection defense family). Vault and mesh names are user-controlled at vault-init / mesh-create time; a vault literally named `--evil` would otherwise smuggle a flag-shaped token into the verb's argv.
 4. If no match (or the only match is `--`-leading), tell the user the available names and stop — do not invent a name.
 
 The `--scope federation` invocation MUST NOT pass `--target` — the CLI ignores it for federation scope but it's noise; only pass `--target` for vault/mesh scopes.
@@ -68,12 +68,12 @@ Key rules:
 - `--scope` is **mandatory** (CLI rejects with `error: "invalid-scope"`, exit 1, if missing or unrecognised). The skill always passes one; default to `federation` when no user signal.
 - `--target <name>` is **required** for `--scope vault` and `--scope mesh`; **omitted** for `--scope federation`. CLI rejects missing target with `error: "missing-target"`, exit 1.
 - `--json` is **mandatory** for this skill. Without it, the CLI prints human-readable output that the skill can't reliably parse.
-- `--dry-run` is the **default for this skill** (ratified default). The CLI's non-dry-run mode atomically writes the primer markdown to `<vault>/.lyt/primers/{scope}-primer.md`; the skill READS the result for agent priming and does not need that persisted file as a side-effect of every invocation. Pass `--dry-run` unless the user explicitly asks to regenerate the on-disk primer ("refresh the primer file", "regenerate the on-disk primer" — then omit `--dry-run`).
+- `--dry-run` is the **default for this skill**. The CLI's non-dry-run mode atomically writes the primer markdown to `<vault>/.lyt/primers/{scope}-primer.md`; the skill READS the result for agent priming and does not need that persisted file as a side-effect of every invocation. Pass `--dry-run` unless the user explicitly asks to regenerate the on-disk primer ("refresh the primer file", "regenerate the on-disk primer" — then omit `--dry-run`).
 - `--top-keywords <n>`, `--top-arcs <n>`, `--provenance-days <n>` are advanced flags. Apply only when the user explicitly signals a cap ("top 50 keywords", "last 30 days of activity"); otherwise rely on CLI defaults (20 / 10 / 7).
 
 ## Phase 3 — Parse the JSON output
 
-The CLI emits Lock 0.3 stable-key-ordered JSON on stdout (exit 0 on success). The actual emitted shape (per `packages/lyt/src/commands/primer.ts:174-215`):
+The CLI emits stable, deterministically key-ordered JSON on stdout (exit 0 on success). The emitted shape:
 
 ```json
 {
@@ -124,7 +124,7 @@ Failure modes (CLI emits to stderr; exit non-zero):
 
 ## Phase 4 — Fetch writable status (vault-scope ONLY)
 
-**Skip this phase for `--scope mesh` and `--scope federation`** — those scopes span multiple vaults and there's no single writable status to surface (per the ratified default). For mesh/federation, jump to Phase 5 and present the primer summary alone. The agent can re-invoke `/lyt-primer-context` per-vault with `--scope vault --target <name>` if it needs write-action guidance for a specific vault.
+**Skip this phase for `--scope mesh` and `--scope federation`** — those scopes span multiple vaults and there's no single writable status to surface. For mesh/federation, jump to Phase 5 and present the primer summary alone. The agent can re-invoke `/lyt-primer-context` per-vault with `--scope vault --target <name>` if it needs write-action guidance for a specific vault.
 
 For `--scope vault --target <name>`, invoke `lyt vault info <name> --json` via Bash (argv-array form):
 
@@ -139,7 +139,7 @@ lyt vault info <name> --json
 spawnSync("lyt", ["vault", "info", vaultName, "--json"]);
 ```
 
-Parse the `vault.writable` + `vault.writableDetermination` fields per the v1.G.2 read-only-awareness contract (see `packages/lyt-vault/src/flows/writability.ts:42-48`). The verdict is tri-state (`true | false | "unknown"`); the determination is one of **6 reasons** the skill must branch on explicitly in Phase 5.
+Parse the `vault.writable` + `vault.writableDetermination` fields per the read-only-awareness contract. The verdict is tri-state (`true | false | "unknown"`); the determination is one of **6 reasons** the skill must branch on explicitly in Phase 5.
 
 ## Phase 5 — Synthesize agent-facing context
 
@@ -171,7 +171,7 @@ Render the agent-priming output as a markdown block. Layout:
 
 ### Capability hint — 6-reason writable contract (vault-scope only)
 
-For vault-scope invocations, surface a reason-specific capability hint based on `writable` + `writableDetermination`. The actual reason strings emitted by `vault info --json` (per `packages/lyt-vault/src/flows/writability.ts`) are listed in the **emitted name** column. The **semantic name** column gives the human-readable synonym some briefs use; the SKILL.md handler-facing prose uses the semantic name, but the comparison MUST be against the emitted name.
+For vault-scope invocations, surface a reason-specific capability hint based on `writable` + `writableDetermination`. The actual reason strings emitted by `vault info --json` are listed in the **emitted name** column. The **semantic name** column gives the human-readable synonym; the SKILL.md handler-facing prose uses the semantic name, but the comparison MUST be against the emitted name.
 
 | Emitted name (writableDetermination) | Semantic name               | writable    | Phase 5 capability hint                                                                                                                                                                                                                           |
 | ------------------------------------ | --------------------------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
@@ -182,20 +182,20 @@ For vault-scope invocations, surface a reason-specific capability hint based on
 | `no-remote`                          | (no-remote)                 | `"unknown"` | ⚠ Writable status unknown — vault has no git remote configured. Configure with `gh repo create` or `git remote add origin <url>`.                                                                                                                 |
 | `orphan-vault`                       | (orphan)                    | `"unknown"` | ⚠ Writable status unknown — vault has no mesh role (orphan). Heal: `lyt repair --apply` (fixes the adopt mesh-link drift, no args needed); a truly un-adopted vault: `lyt repair --target <vault> --apply --mesh <mesh>`. `lyt doctor` diagnoses. |
 
-**Note on emitted vs semantic names.** The brief that authored this skill (v1.G.7 handoff) lists `home-pushable-true` / `home-not-pushable-false` as semantic aliases for the first two reasons. The actual strings emitted by `writability.ts` are `gh-viewerCanPush-true` / `gh-viewerCanPush-false`. The semantic names are kept here as documentation aliases so future renames of the underlying enum (e.g. when the gh-probe naming hardens in v1.G.2.1) don't silently break the skill prose. The 4 unchanged reason strings (`subscriber-default-false`, `gh-unavailable`, `no-remote`, `orphan-vault`) match in both surfaces. **Comparison code MUST use the emitted name; handler-facing prose uses either.**
+**Note on emitted vs semantic names.** The semantic names `home-pushable-true` / `home-not-pushable-false` are documentation aliases for the first two emitted strings `gh-viewerCanPush-true` / `gh-viewerCanPush-false`, kept so future renames of the underlying enum don't silently break the skill prose. The 4 other reason strings (`subscriber-default-false`, `gh-unavailable`, `no-remote`, `orphan-vault`) are identical in both surfaces. **Comparison code MUST use the emitted name; handler-facing prose uses either.**
 
 ## Rules
 
 - **MUST pass `--scope`, `--target` (if applicable), and `--json` as separate argv arguments**, not template-interpolated into a shell command string. Mesh/vault names CAN contain shell metacharacters (backticks, `$()`, `;`, `&&`) — those MUST be conveyed as one argv element per name.
 - **MUST pass `--json`** on every invocation. Human-readable output is not a contract this skill parses.
-- **MUST pass `--dry-run`** UNLESS the user explicitly asks to regenerate the on-disk primer file (the ratified default counter-case). Otherwise every priming call pollutes `<vault>/.lyt/primers/`.
+- **MUST pass `--dry-run`** UNLESS the user explicitly asks to regenerate the on-disk primer file. Otherwise every priming call pollutes `<vault>/.lyt/primers/`.
 - **MUST resolve mesh/vault names via `lyt vault list --json` or `lyt mesh list --json` before passing `--target`.** Do not guess names.
-- **MUST reject `--`-leading names** from `lyt vault list --json` / `lyt mesh list --json` results before passing them to `--target` (G.6 inherited defense; family: G.2 CR-1 gh-flag-injection).
+- **MUST reject `--`-leading names** from `lyt vault list --json` / `lyt mesh list --json` results before passing them to `--target` (the gh-flag-injection defense family).
 - **MUST branch on all 6 writable reasons in Phase 5 (vault-scope).** Each has a distinct capability hint; collapsing them into a generic "can't write" message loses semantic signal the agent needs to recover.
 - **MUST NOT call `lyt primer` without `--scope`.** The CLI rejects with `error: "invalid-scope"`, exit 1.
 - **MUST NOT call `lyt primer` with `--scope vault` or `--scope mesh` without `--target`.** The CLI rejects with `error: "missing-target"`, exit 1.
-- **MUST NOT call `lyt vault info` for `--scope mesh` or `--scope federation`.** Phase 4 is skipped for those scopes (the ratified default); the primer summary alone is the output.
-- **MUST NOT modify or write any file.** This is a read-only skill (`requires_writable_vault: false`). The CLI's atomic primer-file write on non-dry-run is opt-in via the the ratified default counter-case; the skill itself never writes.
+- **MUST NOT call `lyt vault info` for `--scope mesh` or `--scope federation`.** Phase 4 is skipped for those scopes; the primer summary alone is the output.
+- **MUST NOT modify or write any file.** This is a read-only skill (`requires_writable_vault: false`). The CLI's atomic primer-file write on non-dry-run is opt-in only when the user explicitly asks; the skill itself never writes.
 - **MUST NOT compose shell command strings.** Argv-array always (parity with lyt-sync + lyt-search).
 - **MUST NOT silently degrade `writable === "unknown"` to a "writable" hint.** Surface the reason-specific guidance.
 

package/skills/lyt-search/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: lyt-search
 description: >
-  Search a Lyt pod (or a single mesh or vault) using the tiered-cascade engine — Tier 0 arcs (0.95) → Tier 1 lanes (0.90) → Tier 2 FTS5 (0.70) → Tier 3 edges (0.50) — with confidence ranking. Trigger when the user runs /lyt-search <query>, or says "search my pod for X", "find anything about X across my vaults", "search across all meshes for X", "what's in my pod about X", or similar phrasing on a query wider than a single vault. Wraps the `lyt search` CLI verb (v1.D.3b) — federation scope by default; --vault / --mesh narrow scope; --limit caps results. Returns ranked Figments with vault, mesh, snippet, and confidence. Companion to lyt-recall (single-vault keyword grep) for narrower local searches.
+  Search a Lyt pod (or a single mesh or vault) using the tiered-cascade engine — Tier 0 arcs (0.95) → Tier 1 lanes (0.90) → Tier 2 FTS5 (0.70) → Tier 3 edges (0.50) — with confidence ranking. Trigger when the user runs /lyt-search <query>, or says "search my pod for X", "find anything about X across my vaults", "search across all meshes for X", "what's in my pod about X", or similar phrasing on a query wider than a single vault. Wraps the `lyt search` CLI verb — federation scope by default; --vault / --mesh narrow scope; --limit caps results. Returns ranked Figments with vault, mesh, snippet, and confidence. Companion to lyt-recall (single-vault keyword grep) for narrower local searches.
 visibility: public
 lyt-version: 0.5.0
 capabilities: [search]
@@ -11,7 +11,7 @@ requires_writable_vault: false
 
 # /lyt-search
 
-Search a Lyt **pod** (default: every vault across every mesh) using the tiered-cascade engine. The skill is a thin LLM-driven wrapper around the `lyt search` CLI verb (shipped v1.D.3b); the heavy lifting — arc/lane/FTS5/edge cascade, confidence scoring, deterministic JSON emission — already lives in the CLI. The skill resolves the user's intent (query string + scope), invokes the verb with `--json`, parses the Lock 0.3 stable-key-ordered output, and presents ranked results to the handler.
+Search a Lyt **pod** (default: every vault across every mesh) using the tiered-cascade engine. The skill is a thin LLM-driven wrapper around the `lyt search` CLI verb; the heavy lifting — arc/lane/FTS5/edge cascade, confidence scoring, deterministic JSON emission — already lives in the CLI. The skill resolves the user's intent (query string + scope), invokes the verb with `--json`, parses the stable, deterministically key-ordered output, and presents ranked results to the handler.
 
 ## When to invoke
 
@@ -39,7 +39,7 @@ The CLI verb supports three mutually-exclusive scope flags; the default (no flag
 
 1. Run `lyt vault list --json` (vaults) or `lyt mesh list --json` (meshes) first.
 2. Match the user's term to the listed names (exact, then case-insensitive, then prefix).
-3. **Reject any resolved name that begins with `-` or `--`** before passing it to `--vault <name>` / `--mesh <name>` — closes the flag-injection surface the same way lyt-sync does at its Phase 1 (family: G.2 CR-1 gh-flag-injection). Vault names are user-controlled at vault-init time; a vault literally named `--evil` would otherwise smuggle a flag-shaped token into the verb's argv.
+3. **Reject any resolved name that begins with `-` or `--`** before passing it to `--vault <name>` / `--mesh <name>` — closes the flag-injection surface the same way lyt-sync does at its Phase 1 (the gh-flag-injection defense family). Vault names are user-controlled at vault-init time; a vault literally named `--evil` would otherwise smuggle a flag-shaped token into the verb's argv.
 4. If no match (or the only match is `--`-leading), tell the user the available names and stop — do not invent a name.
 
 Do **NOT** pass `--all` as an explicit flag — it's an alias for the default scope. Bare `lyt search` already searches federation; adding `--all` is redundant.
@@ -63,13 +63,13 @@ The Bash-tool variant: pass the argv array form to the tool's `args` field if th
 Key rules:
 
 - The first positional argument is the query — a single string. Multi-word queries are implicit AND. Quote the query so the shell treats it as one argv element.
-- `--json` is **mandatory** for this skill. It yields the deterministic Lock 0.3 stable-key-ordered output the skill parses below; without it, the CLI prints human-readable lines that the skill can't reliably parse.
+- `--json` is **mandatory** for this skill. It yields the deterministic, stable key-ordered output the skill parses below; without it, the CLI prints human-readable lines that the skill can't reliably parse.
 - `--limit <n>` defaults to 20 (CLI default), capped at 1000. Apply caller's `--limit` only when the user explicitly signals a cap ("top 5 results", "first 10"); otherwise rely on the CLI default.
 - Never combine `--vault` AND `--mesh` — the CLI rejects it with `error: "conflicting-scope-flags"` and exits 1.
 
 ## Phase 3 — Parse the JSON output
 
-The CLI emits Lock 0.3 stable-key-ordered JSON on stdout (exit 0 on success). Expected shape:
+The CLI emits stable, deterministically key-ordered JSON on stdout (exit 0 on success). Expected shape:
 
 ```json
 {

package/skills/lyt-sync/SKILL.md

@@ -11,7 +11,7 @@ requires_writable_vault: false
 
 # /lyt-sync
 
-Sync a Lyt vault — pull, detect-and-commit local changes, push (gated on the v1.G.2 writable verdict). The skill always runs; the push step gates internally on the 6-reason `writable` contract from `lyt vault info --json`, so even read-only / subscriber / orphan / no-remote vaults pull cleanly without touching origin.
+Sync a Lyt vault — pull, detect-and-commit local changes, push (gated on the writable verdict). The skill always runs; the push step gates internally on the 6-reason `writable` contract from `lyt vault info --json`, so even read-only / subscriber / orphan / no-remote vaults pull cleanly without touching origin.
 
 ## When to invoke
 
@@ -40,7 +40,7 @@ If the resolved path **does not exist or is not a Lyt vault** (no `.lyt/vault.yo
 
 > The target vault `<path>` doesn't exist (or isn't a Lyt vault — no `.lyt/vault.yon`). Use `lyt vault init <name>`, or pass `--vault <existing-path>`.
 
-**Path-shape safety check.** Before invoking `git -C <vault-path>`, reject any resolved path that begins with `-` or `--` (defensive against a crafted `--vault` argument, `$LYT_ACTIVE_VAULT` env value, or any other resolver-input that could smuggle a flag-shaped token into the git positional). The `.lyt/vault.yon` existence check above already filters most invalid paths; this `--`-leading rejection closes the remaining flag-injection surface (same family as the G.2 CR-1 gh-flag-injection close). Resolved paths MUST be absolute and MUST start with a drive letter (Windows) or `/` (POSIX) before they enter any `git` argv.
+**Path-shape safety check.** Before invoking `git -C <vault-path>`, reject any resolved path that begins with `-` or `--` (defensive against a crafted `--vault` argument, `$LYT_ACTIVE_VAULT` env value, or any other resolver-input that could smuggle a flag-shaped token into the git positional). The `.lyt/vault.yon` existence check above already filters most invalid paths; this `--`-leading rejection closes the remaining flag-injection surface (the gh-flag-injection defense family). Resolved paths MUST be absolute and MUST start with a drive letter (Windows) or `/` (POSIX) before they enter any `git` argv.
 
 ## Phase 2 — Pull with rebase
 
@@ -52,7 +52,7 @@ git -C <vault-path> pull --rebase
 
 (On Windows, `git -C <path>` works with quoted paths, but the lyt-vault precedent — `flows/clone.ts`, `flows/repair.ts`, `util/git-history.ts` — uses `spawnSync` with `cwd: <vault-path>` so the path doesn't need to be embedded in argv. Skill prose recommends the `cwd` shape for cross-platform stability.)
 
-**On rebase conflict** (`git pull --rebase` exits non-zero with conflict markers): per the ratified default (2026-06-01), do NOT attempt auto-resolution. Surface a structured result to the handler and halt:
+**On rebase conflict** (`git pull --rebase` exits non-zero with conflict markers): do NOT attempt auto-resolution. Surface a structured result to the handler and halt:
 
 ```json
 {
@@ -72,7 +72,7 @@ Run `git -C <vault-path> status --porcelain`. If the output is empty, skip to Ph
 1. Parse the porcelain output into a `GitDiffSummary`-shaped object (`{staged: string[], modified: string[]}`). Porcelain v1 (the default) emits one line per change with a 2-character prefix: column 1 is the index/staged status, column 2 is the working-tree status. Treat any line whose column-1 char is not space or `?` as **staged** (e.g. `A `, `M `, `MM`, `D `); treat any line whose column-2 char is not space (or whose prefix is `??`) as **modified**. Strip the 3-character prefix to recover the file path. Files that appear staged AND modified land in both arrays — that's tolerated; the helper sorts and de-orders naturally and the resulting message just lists the file once or twice depending on its multi-state shape.
 2. Decide on a commit message. The skill exposes one **caller-options**-style choice:
 
-- `options.commit-message: "auto"` _(default — the oversight handler default per the ratified default)_ — call the `inferCommitMessage(diff)` heuristic to summarise the diff:
+- `options.commit-message: "auto"` _(default)_ — call the `inferCommitMessage(diff)` heuristic to summarise the diff:
 - 0 files → `"no changes"` _(defensive; unreached because porcelain was non-empty)_
 - 1 file (non-mesh.yon) → `"sync: <filename>"`
 - 1 file (mesh.yon, at any depth) → `"sync: mesh.yon update"`
@@ -80,7 +80,7 @@ Run `git -C <vault-path> status --porcelain`. If the output is empty, skip to Ph
 - > 4 files → `"sync: N files (<first 3>, +M more)"`
 - `options.commit-message: "prompt-handler"` — pause and ask the handler for a one-line message; do not invent one.
 
-The heuristic lives in `packages/lyt-vault/src/util/sync-helpers.ts` as `inferCommitMessage`; the skill prose reproduces the rules above so an agent can run them inline without importing.
+The heuristic is `inferCommitMessage`; the skill prose reproduces the rules above so an agent can run them inline without importing.
 
 3. Stage and commit. **Pass the message via argv, NOT through shell interpolation.** The shell-syntax pseudocode below is for documentation only; agents executing this skill MUST translate it to an argv-safe `spawnSync` / `execFileSync` call so a filename containing shell metacharacters (backticks, `$()`, `;`, `"`) inside the inferred message can't escape into command execution. Concretely:
 
@@ -94,15 +94,15 @@ spawnSync("git", ["-C", vaultPath, "add", "-A"]);
 spawnSync("git", ["-C", vaultPath, "commit", "-m", message]);
 ```
 
-The matching precedent lives in `packages/lyt-vault/src/flows/clone.ts:87` (`execFileSync("git", ["clone", opts.url, target])`) — the same argv-array shape used everywhere the lyt-vault flow layer shells to git.
+The matching precedent is `execFileSync("git", ["clone", opts.url, target])` — the same argv-array shape used everywhere the lyt-vault flow layer shells to git.
 
 Do **not** add a `Co-Authored-By` trailer (per the project's `CLAUDE.md` commit conventions). Do **not** add an `@STAMP` block — that is a `.yon`-write concern handled by lyt-runner, not the sync skill.
 
 ## Phase 4 — Push (gated on the 6-reason writable verdict)
 
-Invoke `lyt vault info <vault-name> --json` and parse the `vault.writable` and `vault.writableDetermination` fields per the v1.G.2 read-only-awareness contract (see `packages/lyt-vault/src/flows/writability.ts:42-48`). The verdict is tri-state (`true | false | "unknown"`); the determination is one of **6 reasons** the skill must branch on explicitly.
+Invoke `lyt vault info <vault-name> --json` and parse the `vault.writable` and `vault.writableDetermination` fields per the read-only-awareness contract. The verdict is tri-state (`true | false | "unknown"`); the determination is one of **6 reasons** the skill must branch on explicitly.
 
-The actual reason strings emitted by `vault info --json` (per writability.ts at HEAD `16ccdf6`) are listed in the **emitted name** column. The **semantic name** column gives the human-readable synonym some briefs use; the SKILL.md surface uses the semantic name in handler-facing prose, but the comparison MUST be against the emitted name.
+The actual reason strings emitted by `vault info --json` are listed in the **emitted name** column. The **semantic name** column gives the human-readable synonym; the SKILL.md surface uses the semantic name in handler-facing prose, but the comparison MUST be against the emitted name.
 
 | Emitted name (writableDetermination) | Semantic name               | writable    | Phase 4 behavior                                                                                                                                               |
 | ------------------------------------ | --------------------------- | ----------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- |
@@ -113,7 +113,7 @@ The actual reason strings emitted by `vault info --json` (per writability.ts at
 | `no-remote`                          | (no-remote)                 | `"unknown"` | Skip push. Report: _"Skipped push: vault has no git remote configured. Configure a remote with `gh repo create` or `git remote add origin <url>`."_            |
 | `orphan-vault`                       | (orphan)                    | `"unknown"` | Skip push. Report: _"Skipped push: vault has no mesh role (orphan). Adopt into a mesh with `lyt mesh adopt --cluster <name>`."_                                |
 
-**Note on emitted vs semantic names.** The brief that authored this skill (v1.G.3 handoff) lists `home-pushable-true` and `home-not-pushable-false` as the writable-determination reason strings. The actual strings emitted by `writability.ts` are `gh-viewerCanPush-true` and `gh-viewerCanPush-false`. The semantic names are kept here as a documentation alias so future renames of the underlying enum (e.g. when the gh-probe naming hardens in v1.G.2.1) don't silently break the skill prose. The 4 unchanged reason strings (`subscriber-default-false`, `gh-unavailable`, `no-remote`, `orphan-vault`) match in both surfaces.
+**Note on emitted vs semantic names.** The semantic names `home-pushable-true` and `home-not-pushable-false` are documentation aliases for the actual emitted strings `gh-viewerCanPush-true` and `gh-viewerCanPush-false`, kept so future renames of the underlying enum don't silently break the skill prose. The 4 other reason strings (`subscriber-default-false`, `gh-unavailable`, `no-remote`, `orphan-vault`) are identical in both surfaces.
 
 Final handler-facing result shape:
 
@@ -131,7 +131,7 @@ Final handler-facing result shape:
 
 ## Rules
 
-- **MUST NOT auto-resolve a rebase conflict.** Halt with the structured-output shape in Phase 2 and let the handler resolve manually. Per the ratified default.
+- **MUST NOT auto-resolve a rebase conflict.** Halt with the structured-output shape in Phase 2 and let the handler resolve manually.
 - **MUST gate push on `vault.writable` / `vault.writableDetermination`.** Never `git push` unless `writableDetermination === "gh-viewerCanPush-true"` (equivalently, `writable === true`). The other 5 reasons all skip push.
 - **MUST branch on all 6 reasons.** Each has a distinct handler-facing message; collapsing them into a generic "can't push" message loses semantic signal the handler needs to recover.
 - **MUST NOT add a `Co-Authored-By` trailer** to the auto-commit. Per the project's `CLAUDE.md` commit conventions, unless the user explicitly requests one.