Share to a team project

Copy a note from the personal/primary project into a configured team project so teammates can see it. This is the only path by which the plugin writes to a shared project, session checkpoints and /basic-memory:bm-remember always stay personal.

Steps

1. Resolve config. Read the basicMemory block with the hooks' precedence. For the user-level base, append settings.json to the literal value of CLAUDE_CONFIG_DIR when that environment variable is present; do not trim it, expand ~, or treat an empty value as unset. Use ~/.claude/settings.json only when the variable is absent. Then the project's .claude/settings.json and .claude/settings.local.json override per key:

   • teamProjects, a map of <project-ref> → { "promoteFolder": "shared" }. These are the allowed share targets. <project-ref> is a workspace-qualified name (e.g. my-team-2/notes) or an external_id UUID.
   • primaryProject, the source project notes are read from.

   If teamProjects is empty, tell the user there's no share target configured and suggest adding one (or running /basic-memory:bm-setup), then stop. Don't invent a target.

2. Find the source note. From $ARGUMENTS (a title, permalink, or memory:// URL), bm_read it from primaryProject. If $ARGUMENTS is empty (you were invoked from "share this"), use the note most clearly referenced in the conversation, confirm which one if there's any ambiguity. Capture its title, full content (including frontmatter), and source permalink.

3. Pick the target. If teamProjects has one entry, use it. If several, ask which team project to share to. Use that entry's promoteFolder (default shared).

4. Confirm before writing. This write is visible to teammates, so show the user what you're about to do, "Share '<title>' to <target>/<promoteFolder>?", and wait for a yes. Never share silently.