@ascenda-one/gemini-hooks 0.1.33 → 0.1.35
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 +11 -6
- package/dist/cli.js +1945 -893
- package/dist/cli.js.map +1 -1
- package/dist/liveSignal.js +7 -5
- package/dist/liveSignal.js.map +1 -1
- package/package.json +3 -2
package/NOTICE
ADDED
package/README.md
CHANGED
|
@@ -20,6 +20,7 @@ opened from the Dock.
|
|
|
20
20
|
|
|
21
21
|
```bash
|
|
22
22
|
npx @ascenda-one/gemini-hooks status # exits non-zero if anything is unwired
|
|
23
|
+
npx @ascenda-one/gemini-hooks doctor # can the hooks run, has one run, and does the screen saver hear them
|
|
23
24
|
npx @ascenda-one/gemini-hooks uninstall # removes hooks, the binary and this pairing
|
|
24
25
|
```
|
|
25
26
|
|
|
@@ -28,8 +29,9 @@ npx @ascenda-one/gemini-hooks uninstall # removes hooks, the binary and this p
|
|
|
28
29
|
| `--api-base-url <url>` | ingest host (default `https://api.ascenda.one`) |
|
|
29
30
|
| `--local [port]` | shorthand for a local [dev server](../ascenda-dev-server/) (default `4477`) |
|
|
30
31
|
| `--tool-installation-id <id>` / `--token <t>` | reuse an existing pairing instead of creating one |
|
|
31
|
-
| `--scope project
|
|
32
|
+
| `--scope user\|project` | register in `~/.gemini/settings.json` for every project (default), or in this project only |
|
|
32
33
|
| `--project-dir <path>` | project root for `--scope project` (default cwd) |
|
|
34
|
+
| `--no-pair` | install without pairing: the screen saver and live view work, nothing is sent |
|
|
33
35
|
| `--dry-run` | print what would change, write nothing |
|
|
34
36
|
|
|
35
37
|
`examples/` holds the equivalent hand-written config for anyone who would
|
|
@@ -48,11 +50,14 @@ still cannot name its installation records the skipped send in the journal
|
|
|
48
50
|
| `ASCENDA_TOOL_INSTALLATION_ID` | overrides the pairing `setup` recorded |
|
|
49
51
|
| `ASCENDA_EVENT_WRITE_TOKEN` | overrides the stored token |
|
|
50
52
|
| `ASCENDA_API_BASE_URL` | overrides the ingest host |
|
|
51
|
-
| `ASCENDA_EVENT_LOG_FILE` |
|
|
52
|
-
|
|
53
|
-
|
|
54
|
-
`not_sent
|
|
55
|
-
|
|
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
|
|
56
61
|
and an idempotency key; both come from the shared sender in `tool-kit`, so
|
|
57
62
|
this adapter holds only its mapping.
|
|
58
63
|
|