@younndai/lyt-skills 0.9.3 → 0.9.4
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@younndai/lyt-skills",
|
|
3
|
-
"version": "0.9.
|
|
3
|
+
"version": "0.9.4",
|
|
4
4
|
"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.",
|
|
5
5
|
"homepage": "https://linkyourthink.com",
|
|
6
6
|
"repository": {
|
|
@@ -49,7 +49,7 @@
|
|
|
49
49
|
"prepublishOnly": "node ../../scripts/check-no-vendored-deps.mjs --root ../.. && node ../../scripts/public-release/scan-tarball.mjs lyt-skills"
|
|
50
50
|
},
|
|
51
51
|
"dependencies": {
|
|
52
|
-
"@younndai/lyt-vault": "^0.9.
|
|
52
|
+
"@younndai/lyt-vault": "^0.9.4",
|
|
53
53
|
"commander": "^12.1.0"
|
|
54
54
|
},
|
|
55
55
|
"devDependencies": {
|
|
@@ -39,7 +39,9 @@ Do **not** guess from cwd. If `--vault` / env var / home convention all miss, as
|
|
|
39
39
|
|
|
40
40
|
If the resolved path **does not exist or is not a Lyt vault** (no `.lyt/vault.yon` inside), do **not** create files in it. Stop and tell the user:
|
|
41
41
|
|
|
42
|
-
> The target vault `<path>` doesn't exist (or isn't a Lyt vault — no `.lyt/vault.yon`). Create it with `lyt vault init <
|
|
42
|
+
> The target vault `<path>` doesn't exist (or isn't a Lyt vault — no `.lyt/vault.yon`). Create it with `lyt vault init <mesh>/<vault>` (create-if-missing — makes the mesh if absent; bare names land in `personal/`), or pass `--vault <existing-name-or-path>`.
|
|
43
|
+
|
|
44
|
+
A `--vault` argument may be a `{mesh}/{vault}` name, a bare leaf (resolved to a unique vault; the CLI errors and lists candidates on a collision), or a pod-local alias (`lyt alias <name> <target>`) — all resolve to the same vault. Resolve names via `lyt vault list --json` rather than guessing.
|
|
43
45
|
|
|
44
46
|
## Phase 2 — Build the Figment under the v1 8-field contract
|
|
45
47
|
|