@hiveku-apps/sync 0.5.26 → 0.5.29

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/README.md CHANGED
@@ -144,8 +144,8 @@ Pass `--trust` to pre-trust the folder in `~/.codex/config.toml` (so Codex loads
144
144
  the repo config without its first-run trust prompt).
145
145
 
146
146
  **Approvals.** Codex asks first only for a **fixed list** of high-risk Hiveku
147
- tools: the 391 names in `src/codex-prompt-tools.json`, the same list as the
148
- Hiveku Codex plugin 0.3.57. It includes `deploy_site`, `site_delete`,
147
+ tools: the 411 names in `src/codex-prompt-tools.json`, the same list as the
148
+ Hiveku Codex plugin 0.3.61. It includes `deploy_site`, `site_delete`,
149
149
  `project_files_bulk_save` and every `hiveku_batch`, and it is written as
150
150
  `[mcp_servers.hiveku.tools.<tool>] approval_mode = "prompt"`. **Every other tool
151
151
  on the `hiveku` server runs without asking** (`default_tools_approval_mode =
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@hiveku-apps/sync",
3
- "version": "0.5.26",
3
+ "version": "0.5.29",
4
4
  "description": "Sync a Hiveku account's memory/rules/skills + coder projects into a local folder, and ship projects (push/deploy/pull-env) from the terminal. Pairs with the Hiveku MCP at core.hiveku.com/mcp so Claude Code can drive Hiveku tools per-folder.",
5
5
  "type": "module",
6
6
  "license": "MIT",
@@ -1,5 +1,5 @@
1
1
  {
2
- "source": "locus2012/hiveku-codex-plugin 0.3.57 (feature/memory-page-ask-first 557c2b8, on main 09f9b5e), plugins/hiveku/.mcp.json: every hiveku.tools entry with approval_mode \"prompt\" (project_vcs_rollback included)",
2
+ "source": "locus2012/hiveku-codex-plugin 0.3.61 (feature/meet-discussions-ask-first 225d34f, on main f073885), plugins/hiveku/.mcp.json: every hiveku.tools entry with approval_mode \"prompt\" (project_vcs_rollback included)",
3
3
  "why": "hiveku-sync writes its own [mcp_servers.hiveku] into a Codex folder. Codex then uses that entry, not the plugin's, for the server's connection and for every tool's approval mode, so these prompts must be written here too. Refresh this list whenever the Codex plugin's prompt list changes.",
4
4
  "tools": [
5
5
  "deploy_site",
@@ -171,6 +171,17 @@
171
171
  "ppc_connection_update",
172
172
  "agent_approval_approve",
173
173
  "marketing_approval_approve",
174
+ "mc_task_claim",
175
+ "mc_task_release",
176
+ "mc_task_answer",
177
+ "marketing_webinar_invite",
178
+ "marketing_webinar_cancel",
179
+ "marketing_webinar_delete",
180
+ "meet_recording_delete",
181
+ "discussion_recording_delete",
182
+ "discussion_channel_share",
183
+ "discussion_channel_unshare",
184
+ "discussion_delete",
174
185
  "marketing_offline_conversions_go_live",
175
186
  "ppc_conversion_adjustments_go_live",
176
187
  "ppc_meta_lead_quality_enable",
@@ -206,6 +217,7 @@
206
217
  "crm_contact_email_send_from_domain",
207
218
  "crm_enroll_sequence",
208
219
  "crm_sequence_enroll_bulk",
220
+ "crm_sequence_enroll_audience",
209
221
  "email_sequence_enroll",
210
222
  "email_sequence_activate",
211
223
  "marketing_activate",
@@ -219,6 +231,14 @@
219
231
  "outbound_reply_draft_send",
220
232
  "outbound_lead_list_run_start",
221
233
  "outbound_lead_list_run_control",
234
+ "outbound_lead_grid_delete",
235
+ "outbound_lead_grid_rows_delete",
236
+ "outbound_lead_grid_rows_hold",
237
+ "outbound_lead_grid_formula_write",
238
+ "outbound_lead_grid_import_start",
239
+ "outbound_lead_grid_import_auto_run",
240
+ "outbound_lead_grid_auto_run_enable",
241
+ "outbound_lead_grid_auto_run_control",
222
242
  "voice_number_purchase",
223
243
  "voice_number_release",
224
244
  "voice_e911_address_create",