@tanagram/lore 0.1.179 → 0.1.182

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.
Files changed (3) hide show
  1. package/README.md +3 -3
  2. package/dist/index.js +271 -271
  3. package/package.json +5 -5
package/README.md CHANGED
@@ -10,7 +10,7 @@ copy-paste, no screenshots, no "save this thread" button to remember.
10
10
  ## Get started
11
11
 
12
12
  ```sh
13
- npm install -g @tanagram/lore
13
+ npm install -g @loredotlink/cli
14
14
  lore
15
15
  ```
16
16
 
@@ -249,7 +249,7 @@ Esc to return to the sidebar, and q to exit.
249
249
  ## Dev vs prod
250
250
 
251
251
  The CLI is environment-stamped at build time (esbuild `--define`), not via
252
- runtime env vars. The published `@tanagram/lore` on npm is pinned to prod;
252
+ runtime env vars. The published `@loredotlink/cli` on npm is pinned to prod;
253
253
  anything built locally (`pnpm build`, `tsx`, `pnpm dev`) is pinned to dev.
254
254
 
255
255
  Because both can be installed on the same machine, they keep separate state
@@ -295,7 +295,7 @@ roots. It is intentionally separate from the default `pnpm test` glob so CI can
295
295
  choose when to run the full acceptance loop explicitly:
296
296
 
297
297
  ```sh
298
- pnpm --filter @tanagram/lore test:skill-sync:e2e
298
+ pnpm --filter @loredotlink/cli test:skill-sync:e2e
299
299
  ```
300
300
 
301
301
  The suite covers private capture, workspace publish/install, subscriber update