@tanagram/lore 0.1.86 → 0.1.87

package/README.md

@@ -2,27 +2,24 @@
 
 The command-line interface for Lore.
 
-## Privacy: Lore only uploads from directories you allow
-
-By default the Lore daemon does **not** auto-upload any Claude Code
-session. You have to opt in per directory. This is the consent-first
-contract:
-
-- Sessions whose cwd is not under one of your upload directories are
-  ignored by the daemon — they stay on your machine.
-- The explicit commands (`lore export`, `lore share-codex`,
-  `lore share-cowork`) are user-initiated and bypass the upload-dir
-  gate. You can always opt-in per session.
-- The allowlist lives in `~/.lore/upload_dirs.json` (`~/.lore-dev/` in
-  dev), written with 0600 mode so other users on the same machine can't
-  read it.
-
-Adding directories takes a single keystroke on first login — the TUI
-shows your most-recent Claude Code project cwds with the top three
-pre-checked, and pressing Enter accepts them. `lore listen configure`
-re-enters that same interactive flow any time (it's also one of the
-quick actions on the `lore` dashboard). For scripted/non-interactive
-edits, manage the list directly:
+## Privacy: Lore uploads according to your local filters
+
+The Lore daemon evaluates `~/.lore/upload_filters.json` (`~/.lore-dev/`
+in dev) before auto-uploading Claude Code sessions. Missing config or an
+empty `include` allowlist means upload nothing. Non-empty `include`
+dimensions (`cwd`, `repo`, `skills`) are ANDed together, values within a
+dimension are ORed, and `exclude` rules override includes.
+
+The explicit commands (`lore export`, `lore share-codex`,
+`lore share-cowork`) are user-initiated and upload the requested session
+directly.
+
+Adding directories through the TUI is a convenience for writing cwd
+include filters. The post-login wizard shows your most-recent Claude Code
+project cwds with the top three pre-checked, and pressing Enter accepts
+them. `lore listen configure` re-enters that same interactive flow any
+time (it's also one of the quick actions on the `lore` dashboard). For
+scripted/non-interactive edits, manage the cwd filters directly:
 
 ```sh
 lore listen configure                         # re-run the interactive wizard
@@ -34,7 +31,7 @@ lore listen update ~/work --workspace other-corp    # reassign workspace
 lore listen delete ~/code/projectA            # stop uploading from
 ```
 
-Matching uses path-separator-aware **prefix-tree** semantics, so adding
+`cwd` matching uses path-separator-aware **prefix-tree** semantics, so adding
 `~/code` covers `~/code/projectA`, `~/code/projectA/src`, etc., but
 deliberately does **not** cover `~/code-other`. The most-specific
 matching entry wins, so you can have a broad personal `~/` allow plus a
@@ -79,8 +76,8 @@ through Ink in TTY mode:
   device code panel → polling), then a success box with the resolved
   LaunchAgent paths. Distinct copy for timed-out / denied / expired.
   On first login the device-code flow is followed by a one-screen
-  "Configure upload directories" wizard so the daemon has explicit
-  consent to upload anything (see Privacy section above).
+  "Configure upload directories" wizard that can write cwd include
+  filters for users who prefer a directory allowlist workflow.
 - **`lore enable` / `disable` / `restart`** — spinner with mode-specific
   copy while launchctl works, then a success or error MessageBox.
 - **`lore status`** — two-panel view (health on the left, paths on the