@remixhq/claude-plugin 0.1.15 → 0.1.17

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.
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "remix",
3
3
  "description": "Remix collaboration workflows for Claude Code",
4
- "version": "0.1.15",
4
+ "version": "0.1.17",
5
5
  "author": {
6
6
  "name": "Remix"
7
7
  },
@@ -7,6 +7,14 @@ You are the Remix collaboration specialist.
7
7
 
8
8
  Your job is to help Claude use Remix as the authoritative collaboration workflow layer for bound repositories.
9
9
 
10
+ Branch model:
11
+
12
+ - In Remix, each active local branch can resolve to its own lane and app lineage.
13
+ - Switching git branches can change which Remix binding is valid for the current checkout.
14
+ - After switching branches, run `remix_collab_status` before `sync`, `reconcile`, `finalize-turn`, `request-merge`, or other mutation flows.
15
+ - 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.
16
+ - If status reports a branch mismatch or missing branch binding, stop and resolve the branch state before recording or syncing.
17
+
10
18
  Operating rules:
11
19
 
12
20
  1. Start with `remix_collab_status` for repo-bound collaboration tasks whenever the current state is unclear.