@ascenda-one/gemini-hooks 0.1.34 → 0.1.36
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.
- package/NOTICE +4 -0
- package/README.md +8 -5
- package/dist/cli.js +1859 -716
- package/dist/cli.js.map +1 -1
- package/dist/mapGeminiEvent.js +7 -3
- package/dist/mapGeminiEvent.js.map +1 -1
- package/dist/setup.js +5 -8
- package/dist/setup.js.map +1 -1
- package/package.json +3 -2
package/NOTICE
ADDED
package/README.md
CHANGED
|
@@ -50,11 +50,14 @@ still cannot name its installation records the skipped send in the journal
|
|
|
50
50
|
| `ASCENDA_TOOL_INSTALLATION_ID` | overrides the pairing `setup` recorded |
|
|
51
51
|
| `ASCENDA_EVENT_WRITE_TOKEN` | overrides the stored token |
|
|
52
52
|
| `ASCENDA_API_BASE_URL` | overrides the ingest host |
|
|
53
|
-
| `ASCENDA_EVENT_LOG_FILE` |
|
|
54
|
-
|
|
55
|
-
|
|
56
|
-
`not_sent
|
|
57
|
-
|
|
53
|
+
| `ASCENDA_EVENT_LOG_FILE` | local JSONL log of every event, or `off` |
|
|
54
|
+
|
|
55
|
+
Without a pairing, every event is written to `~/.ascenda/events.jsonl` as
|
|
56
|
+
`not_sent`, so you can see exactly what would be transmitted, or read the
|
|
57
|
+
events with your own tools, without connecting anything.
|
|
58
|
+
[examples/local-event-reader](../examples/local-event-reader/) shows how.
|
|
59
|
+
`setup --event-log <path>` moves the file, `setup --event-log off` stops it,
|
|
60
|
+
and the variable wins over both. Every payload carries the UTC offset
|
|
58
61
|
and an idempotency key; both come from the shared sender in `tool-kit`, so
|
|
59
62
|
this adapter holds only its mapping.
|
|
60
63
|
|