@leadbay/mcp 0.39.8 → 0.39.10
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/MIGRATION.md +5 -5
- package/dist/bin.js +973 -204
- package/dist/http-server.js +957 -191
- package/dist/installer-electron.js +1 -1
- package/dist/installer-gui.js +1 -1
- package/package.json +1 -1
package/MIGRATION.md
CHANGED
|
@@ -32,9 +32,9 @@ field. On the `notification_id` path the job is done when `in_progress` is false
|
|
|
32
32
|
`still_running[]` is empty on that path from the first poll and must not be read
|
|
33
33
|
as "done". On the `lead_ids` path, done means `still_running[]` is empty.
|
|
34
34
|
|
|
35
|
-
`leadbay_bulk_enrich_status` answers `ENRICH_JOB_NO_COUNTERS
|
|
36
|
-
notification carries
|
|
37
|
-
|
|
35
|
+
`leadbay_bulk_enrich_status` no longer answers `ENRICH_JOB_NO_COUNTERS`. An
|
|
36
|
+
enrichment notification never carries per-contact counters, so the tool reads the
|
|
37
|
+
job's lead set back from the backend and answers through the per-lead path.
|
|
38
38
|
|
|
39
39
|
## Errors removed
|
|
40
40
|
|
|
@@ -43,8 +43,8 @@ notification carries no per-contact counters (the common case) — re-call with
|
|
|
43
43
|
no longer exist, and neither does `~/.leadbay/bulks.json` or the
|
|
44
44
|
`LEADBAY_BULK_STORE_ALLOW_MEMORY` escape hatch. The replacements are
|
|
45
45
|
`ENRICH_STATUS_INPUT_REQUIRED`, `ENRICH_JOB_NOT_FOUND`, `ENRICH_JOB_WRONG_KIND`,
|
|
46
|
-
`
|
|
47
|
-
|
|
46
|
+
`QUALIFY_STATUS_INPUT_REQUIRED`, `QUALIFY_JOB_NOT_FOUND` and
|
|
47
|
+
`QUALIFY_JOB_WRONG_KIND`. The 0.5.0 sections below describe the old store and
|
|
48
48
|
are kept as history.
|
|
49
49
|
|
|
50
50
|
---
|