sensemaking 0.3.1 → 0.3.2

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "sensemaking",
-  "version": "0.3.1",
+  "version": "0.3.2",
   "description": "Query a knowledge base you build with an agent: filter notes by frontmatter, then search inside them",
   "keywords": [
     "markdown",

package/skills/sense/EXAMPLES.md

@@ -83,6 +83,7 @@ sense query "SELECT DISTINCT type FROM frontmatter"    # what a field's values a
 | `SELECT text FROM content` | dumps the vault into context | `snippet(content, -1, '«', '»', '…', 10)` |
 | `sense find "pricing"` | one word misses synonyms | `"pricing OR billing OR invoicing"` |
 | `sense find "pricing model details"` | bare words AND-join in FTS5; one absent word = zero rows | OR the words, or quote an exact phrase |
+| `sense find "customer-facing OR on-site"` | bare punctuation is FTS5 syntax (`-` = column filter) | double-quote the terms: `"customer-facing" OR "on-site"` |
 | `Read` a 4,000-token file for one section | 10× the tokens needed | `peek` first, `Read` the line range |
 | queries without `LIMIT` | unbounded output | `LIMIT 10`, widen only if all rows look wrong |
 | save every query to config | config churn for one-offs | ad-hoc `sense query`; save only reusable views |

package/skills/sense/SKILL.md

@@ -60,7 +60,9 @@ sense query "SELECT j.value, COUNT(*) n FROM frontmatter, json_each(frontmatter.
 ```
 
 - `content MATCH` takes FTS5 syntax: `a OR b`, `"phrase"`, `pref*`, `NEAR(a b, 5)`,
-  `summary: term`. Stemmed; markdown stripped at index time.
+  `summary: term`. Stemmed; markdown stripped at index time. Double-quote any term with
+  punctuation — bare `customer-facing` errors (`-` reads as a column filter), bare
+  apostrophes are syntax errors: write `"customer-facing"`, `"founder's"`.
 - Rank with `ORDER BY bm25(content, 10.0, 5.0, 1.0)` (title > summary > body); excerpt with
   `snippet(content, -1, '«', '»', '…', 10)`.
 - Select `content.title`/`content.summary` (always exist, empty when absent) rather than