Add 2026-06-08 knowledge ingest report

docs/reports/2026-06-08-knowledge-intake-ingestion-run.md

@@ -0,0 +1,57 @@
+# Knowledge Intake Ingestion Run — 2026-06-08
+
+Operational run of the `knowledge-intake` ingestion pipeline, capturing how many items each source returned and documenting the unresolved Gmail auth blocker for the `email` source.
+
+## Command
+
+```bash
+cd ~/dev/knowledge-intake && source .env && bun run src/cli.ts ingest
+```
+
+- **Run date**: 2026-06-08
+- **Repo**: `~/dev/knowledge-intake` (sibling to `intent-layer`)
+- **Runtime**: `bun`
+- **Exit code**: `0` (overall CLI exited successfully; one source failed before completing)
+
+## Per-source results
+
+| Source   | Items fetched | Status |
+|----------|--------------:|--------|
+| pinboard | 0             | OK |
+| papers   | 0             | OK |
+| github   | 100           | OK |
+| email    | 0             | Error before successful fetch; item count not confirmed empty |
+| **Total**| **100**       | 3 of 4 sources completed |
+
+The CLI-reported total of **100 new items** equals pinboard (0) + papers (0) + github (100). The `email` source did not complete successfully, so its `0` reflects a failed fetch path rather than a confirmed empty result set.
+
+## Source-level error: email
+
+The `email` source failed during a Gmail search via the `gog` CLI:
+
+```text
+[email] error: gog gmail search failed (exit 1): gmail options: token source: get token for ryan.orban@gmail.com: read token: keyring connection timed out after 10s while reading keyring item (macOS Keychain may be waiting for a permission prompt; run `gog auth list` from a terminal and click "Always Allow" when prompted); set GOG_KEYRING_BACKEND=file and GOG_KEYRING_PASSWORD=<password> to use encrypted file storage instead
+```
+
+### Remediation attempted in this run
+
+1. Ran `gog auth list` from an interactive shell in `~/dev/knowledge-intake`; the command hung waiting on the same Keychain access path and did not unlock the token.
+2. Confirmed the Gmail token key exists with `gog auth tokens list --plain --no-input`, but token export still blocked when attempting to read the secret for migration to file-backed storage.
+
+### Current blocker
+
+The host still requires an interactive macOS Keychain approval for the Gmail token, and that approval cannot be completed from this automation environment. Because of that, the ingestion result for `email` remains incomplete.
+
+## Raw log
+
+```text
+$ cd ~/dev/knowledge-intake && source .env && bun run src/cli.ts ingest
+
+[pinboard] fetched 0 new items
+[papers] fetched 0 new items
+[github] fetched 100 new items
+[email] error: gog gmail search failed (exit 1): gmail options: token source: get token for ryan.orban@gmail.com: read token: keyring connection timed out after 10s while reading keyring item (macOS Keychain may be waiting for a permission prompt; run `gog auth list` from a terminal and click "Always Allow" when prompted); set GOG_KEYRING_BACKEND=file and GOG_KEYRING_PASSWORD=<password> to use encrypted file storage instead
+
+Ingestion complete: 100 new items
+EXIT_CODE=0
+```