@tanagram/lore 0.1.30 → 0.1.31
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/dist/index.js +68 -67
- package/package.json +1 -1
- package/skills/share/SKILL.md +5 -1
package/package.json
CHANGED
package/skills/share/SKILL.md
CHANGED
|
@@ -48,12 +48,15 @@ The first command prints a single JSON object on stdout:
|
|
|
48
48
|
"project": "/Users/me/repo",
|
|
49
49
|
"reused": false,
|
|
50
50
|
"visibility": "workspace",
|
|
51
|
-
"clipboard_copied": true
|
|
51
|
+
"clipboard_copied": true,
|
|
52
|
+
"remix_of_thread_id": null,
|
|
53
|
+
"remix_parent_dropped": false
|
|
52
54
|
}
|
|
53
55
|
```
|
|
54
56
|
|
|
55
57
|
- `url` — the shareable Lore link for the session thread. **Always show this to the user as the primary result.**
|
|
56
58
|
- `clipboard_copied` — `true` when the URL was copied to the system clipboard (via `pbcopy` on macOS, `wl-copy`/`xclip`/`xsel` on Linux, `clip.exe` on Windows). `false` when no clipboard tool was available. Mention this to the user when `true` so they know they can paste it directly.
|
|
59
|
+
- `remix_parent_dropped` — `true` when a `LORE_REMIX.md` was present in the cwd but the parent thread it pointed at couldn't be resolved (missing, deleted, or not visible). The export still succeeded; the lineage was just dropped. The CLI also prints a one-line warning to stderr in this case suggesting the user delete the stale `LORE_REMIX.md`.
|
|
57
60
|
|
|
58
61
|
## After Running
|
|
59
62
|
|
|
@@ -65,6 +68,7 @@ Echo the session URL back to the user as a clickable link. If `clipboard_copied`
|
|
|
65
68
|
|
|
66
69
|
- **Not logged in**: the command returns `not logged in — run 'lore login' first`. Tell the user to run `lore login` and try again.
|
|
67
70
|
- **No matching history entry**: this happens when `${CLAUDE_SESSION_ID}` isn't present in `~/.claude/history.jsonl` yet (very fresh session) or when the user asked to share a session that the CLI can't find. Ask the user which session they want to share, or suggest `--session-id <id>` / `--project <path>` with the value they provide.
|
|
71
|
+
- **Stale remix lineage** (not a failure, but worth surfacing): if a `LORE_REMIX.md` is sitting in the cwd from a prior `lore remix` whose parent isn't shareable, the export succeeds with `remix_parent_dropped: true` and a one-line stderr warning. Pass that warning along to the user so they know whether to delete the stale brief.
|
|
68
72
|
|
|
69
73
|
## What This Does NOT Do
|
|
70
74
|
|