@hiveku-apps/sync 0.5.1 → 0.5.3

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@hiveku-apps/sync",
-  "version": "0.5.1",
+  "version": "0.5.3",
   "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.",
   "type": "module",
   "license": "MIT",

package/src/claude-md.mjs

@@ -30,16 +30,31 @@ export const CLAUDE_MD_BEGIN = '<!-- hiveku:memory:begin -->';
 /**
  * The source-of-truth rule, in the same words as the MCP server's own
  * instructions (hiveku-mcp-api-server src/services/mcp-instructions.service.ts,
- * MCP #100; Abe, 2026-10-03: "This memory needs to be the source of truth and
+ * MCP #100, with the two sentences MCP #174 adds on About your business and a
+ * local copy; Abe, 2026-10-03: "This memory needs to be the source of truth and
  * the agents know it and obey it"). CLAUDE.md's kept-current part and AGENTS.md
  * both carry it.
  */
 export const SOURCE_OF_TRUTH_LINE =
   'Hiveku Memory is the source of truth for this business: read it before you act, and follow it ' +
   'over your own assumptions, local files or earlier conversation. When something disagrees with ' +
-  'memory, trust memory and say so. When `memory_log_add` is listed, record your work: a Doing line ' +
-  'when you start a task for the person and a Done line when it ends. Save what you learned with the ' +
-  'memory_* tools.';
+  'memory, trust memory and say so. About your business is read with `account_memory_get`; ' +
+  'memory_list and memory_get leave it out. A local copy (ACCOUNT_MEMORY.md and the like) may be out ' +
+  'of date: read it again from Hiveku before you act on it. When `memory_log_add` is listed, record ' +
+  'your work: a Doing line when you start a task for the person and a Done line when it ends. Save ' +
+  'what you learned with the memory_* tools.';
+
+/**
+ * What Hiveku now writes in the memory log itself (MCP #174): a connected app's
+ * session gets its Doing at its first change and its Done when it goes quiet or
+ * ends, both counting the changes; the model's own Done says more and closes the
+ * session's run with its line. Both scaffolds put it right after the rule. The
+ * same words as the Claude Code plugin's shim and the VS Code extension.
+ */
+export const WORK_LOG_LINE =
+  "Hiveku records this session's Doing at its first change and its Done when the session goes quiet " +
+  'or ends. When the work ends, send a Done with `memory_log_add` and a one-line summary of what you ' +
+  'did, if you want the log to say more than the count of changes; leave `thread` out.';
 export const CLAUDE_MD_END = '<!-- hiveku:memory:end -->';
 
 /** The kept-current part: the markers and the two sections between them. */
@@ -51,6 +66,7 @@ export function claudeMdMemoryRegion() {
 anything else in this file disagrees with them, follow these two sections.
 
 ${SOURCE_OF_TRUTH_LINE}
+${WORK_LOG_LINE}
 
 \`hiveku-sync pull\` files every entry under the agent that owns it, the way the
 Memory page does: \`<type>/<agent>/<name>.md\`, and \`<type>/shared/<name>.md\` for
@@ -92,8 +108,10 @@ The local files are a mirror of what memory said the last time
 \`hiveku-sync pull\` ran, and memory wins. They are quick context (never the
 \`moved/\` and \`not-followed/\` folders above), but before you act on one, or
 change an entry starting from one, re-read the entry live with
-\`memory_get({ memory_id })\` (the \`id\` in its front matter) and follow what
-that read says. To refresh the copies, run \`hiveku-sync pull\`.
+\`memory_get({ memory_id })\` (the \`id\` in its front matter), and About your
+business (\`hiveku-data/account/ACCOUNT_MEMORY.md\`) with \`account_memory_get\`,
+which memory_list and memory_get leave out, and follow what that read says. To
+refresh the copies, run \`hiveku-sync pull\`.
 
 ## Memory writes
 

package/src/codex-prompt-tools.json

@@ -1,5 +1,5 @@
 {
-  "source": "locus2012/hiveku-codex-plugin #28 (b7ff5fd, 2026-10-03), plugins/hiveku/.mcp.json: every hiveku.tools entry with approval_mode \"prompt\" (project_vcs_rollback included)",
+  "source": "locus2012/hiveku-codex-plugin main (af0fd36, 0.3.8), plugins/hiveku/.mcp.json: every hiveku.tools entry with approval_mode \"prompt\" (project_vcs_rollback included)",
   "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.",
   "tools": [
     "deploy_site",
@@ -8,6 +8,7 @@
     "project_vcs_commit",
     "project_vcs_merge",
     "project_vcs_pr_merge",
+    "github_pr_merge",
     "project_vcs_env_bind",
     "project_vcs_branch_delete",
     "project_vcs_stash",
@@ -15,6 +16,9 @@
     "project_vcs_branch_preview_teardown",
     "project_vcs_revert",
     "project_vcs_rollback",
+    "project_vcs_resolve",
+    "project_vcs_pr_update",
+    "project_vcs_queue_add",
     "hiveku_batch",
     "project_checkpoint_restore",
     "checkpoint_restore",
@@ -67,10 +71,15 @@
     "ppc_google_ad_text_update",
     "ppc_google_ads_text_replace",
     "ppc_bing_rsa_text_update",
+    "ppc_meta_ad_text_update",
     "ppc_negatives_remove",
     "ppc_bing_url_tracking_set",
     "ppc_bing_ad_extension_update",
     "ppc_bing_ad_extension_remove",
+    "ppc_google_sitelink_update",
+    "ppc_bing_campaign_budget_move",
+    "ppc_bing_shared_budget_update",
+    "ppc_google_campaign_conversion_goals_set",
     "ppc_bing_experiment_create",
     "ppc_bing_experiment_update",
     "ppc_experiment_promote",
@@ -90,6 +99,7 @@
     "seo_ga4_event_create_rule_update",
     "accounting_bill_record_payment",
     "accounting_invoice_record_payment",
+    "accounting_subscription_create",
     "crm_contact_email_send",
     "crm_enroll_sequence",
     "crm_sequence_enroll_bulk",
@@ -165,6 +175,7 @@
     "seo_gtm_publish",
     "seo_gtm_install",
     "seo_ga4_key_event_delete",
+    "seo_ga4_custom_definition_archive",
     "seo_ga4_event_create_rule_delete",
     "seo_tracking_project_delete",
     "seo_rankings_platforms_set",

package/src/codex.mjs

@@ -45,7 +45,7 @@ import { formatKey, readTomlDeclarations } from './toml.mjs';
 import { loadDotenv, safeSlug } from './util.mjs';
 import { ownerFolder } from './knowledge-files.mjs';
 import { SHARED_OWNER, ownerLabel, ownerOrder } from './memory-owner.mjs';
-import { SOURCE_OF_TRUTH_LINE } from './claude-md.mjs';
+import { SOURCE_OF_TRUTH_LINE, WORK_LOG_LINE } from './claude-md.mjs';
 
 /**
  * The FIXED list of high-risk Hiveku tools that Codex asks about before
@@ -147,8 +147,10 @@ named \`hiveku-<agent>-<name>\` for the agent that owns them, invoked by name) a
 Non-negotiables (also in CLAUDE.md, restated because they are load-bearing):
 - **Verify identity before ANY write:** \`get_account_info\` must return THIS account.
 - **Hiveku Memory is the source of truth.** ${SOURCE_OF_TRUTH_LINE}
+  ${WORK_LOG_LINE}
   The memory files in this folder are a mirror of the last \`hiveku-sync pull\`, and memory wins: before you act
-  on one, or change an entry starting from one, re-read the entry live (\`memory_get({ memory_id })\`).
+  on one, or change an entry starting from one, re-read the entry live (\`memory_get({ memory_id })\`; About your
+  business, \`hiveku-data/account/ACCOUNT_MEMORY.md\`, with \`account_memory_get\`).
 - **Context and memory.** Call \`account_context_get({ domain })\` first, before any copy, plan or analysis.
   The account memory is read-only to you: owners edit it on the Hiveku dashboard, the local copy is
   \`hiveku-data/account/ACCOUNT_MEMORY.md\` (never edit or upload it); suggest one line with \`account_memory_append\`.