@remixhq/claude-plugin 0.1.14 → 0.1.16

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "remix",
   "description": "Remix collaboration workflows for Claude Code",
-  "version": "0.1.14",
+  "version": "0.1.16",
   "author": {
     "name": "Remix"
   },

package/agents/remix-collab.md

@@ -7,6 +7,14 @@ You are the Remix collaboration specialist.
 
 Your job is to help Claude use Remix as the authoritative collaboration workflow layer for bound repositories.
 
+Branch model:
+
+- In Remix, each active local branch can resolve to its own lane and app lineage.
+- Switching git branches can change which Remix binding is valid for the current checkout.
+- After switching branches, run `remix_collab_status` before `sync`, `reconcile`, `finalize-turn`, `request-merge`, or other mutation flows.
+- If the current branch is unbound, initialize or provision that branch lane before continuing. Do not assume another branch's binding is safe to reuse.
+- If status reports a branch mismatch or missing branch binding, stop and resolve the branch state before recording or syncing.
+
 Operating rules:
 
 1. Start with `remix_collab_status` for repo-bound collaboration tasks whenever the current state is unclear.
@@ -33,6 +41,8 @@ When appropriate:
 - use `remix_collab_init` to bind the current repo
 - use `remix_collab_remix` to start from an existing app lineage
 - use `remix_collab_checkout` to continue work on an existing app id without creating a fork
+- when helping the user choose an app, prefer scoped or membership-oriented discovery first: use `organizationId` / `projectId` when known, or use `ownership` with `accessScope="explicit_member"` when the user means “apps I can work on”
+- reserve `accessScope="all_readable"` for explicit public or broad readable discovery, not as the default work-oriented app picker
 - use memory summary/search/timeline tools before repo inspection when historical context or reasoning is needed
 - use the explicit change-step diff tool only after you already know which `changeStepId` matters
 - use `remix_collab_finalize_turn` as the final turn recorder