Parse LinkedIn MCP v4.22 inbox and conversations

.github/workflows/ci.yml

@@ -46,6 +46,10 @@ jobs:
         working-directory: bin/kbsearch
         run: go test ./rank -count=1
 
+      - name: Go tests (chats nested module)
+        working-directory: bin/chats
+        run: go test ./... -count=1
+
       - name: facts/audit self (lexicon consistency, no network)
         run: |
           ./bin/facts/audit self 2>/dev/null || echo "audit: not yet implemented; gate skipped"

PLAN.md

@@ -118,10 +118,11 @@ Common props on every node/edge: `root`, `confidence`, `evidence[]`, `how`,
 
 1. go vet + go test ./... (Go tools; root module)
 2. `go test ./rank` in `bin/kbsearch` (cgo-free ranking + flag parser; nested module still needs ladybug for the rest)
-3. python -m unittest discover (Py tools)
-4. bin/facts/audit self  (lexicon internal consistency)
-5. bin/kb/eval            (recall@5 ≥ 0.95, gates index regressions)
-6. md-docs build/lint if docs tooling arrives.
+3. `go test ./...` in `bin/chats` (Telegram + LinkedIn parsers; nested module)
+4. python -m unittest discover (Py tools)
+5. bin/facts/audit self  (lexicon internal consistency)
+6. bin/kb/eval            (recall@5 ≥ 0.95, gates index regressions)
+7. md-docs build/lint if docs tooling arrives.
 
 Feedback loop: every commit → PR → CI → green/gate → merge. Same discipline as
 `db/tech-poc`: contract first where there is an OpenAPI/message shape.