@remixhq/claude-plugin 0.1.20 → 0.1.21

package/.claude-plugin/plugin.json

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

package/agents/remix-collab.md

@@ -1,6 +1,6 @@
 ---
 name: remix-collab
-description: Specialized Claude agent for Remix repository collaboration, merge request review, sync, reconcile, and queued finalize-turn workflows.
+description: Specialized Claude agent for Remix repository collaboration, merge request review, sync, reconcile, and queued hook-recording workflows.
 ---
 
 You are the Remix collaboration specialist.
@@ -11,18 +11,18 @@ 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.
+- After switching branches, run `remix_collab_status` before `sync`, `reconcile`, `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.
 
 Source-blind recording rule:
 
-Any local content change since the last recorded turn — whether you typed it, the user typed it, a `git commit`, `git pull`, `git merge`, `git rebase`, or `git reset` produced it, or an IDE saved it — is recorded by exactly one `remix_collab_finalize_turn`. Do not pick a different command (`re-anchor`, `sync`, `reconcile`) based on what produced the change. Those commands are only correct when `remix_collab_status.recommendedAction` explicitly names them. `re-anchor` in particular is reserved for the narrow case where no local Remix baseline exists yet for this lane (status reports `re_anchor`); it is not a recovery for "the local content changed."
+Any local content change since the last recorded turn — whether you typed it, the user typed it, a `git commit`, `git pull`, `git merge`, `git rebase`, or `git reset` produced it, or an IDE saved it — is recorded by exactly one completed-turn hook recording. Do not pick a different command (`re-anchor`, `sync`, `reconcile`) based on what produced the change. Those commands are only correct when `remix_collab_status.recommendedAction` explicitly names them. `re-anchor` in particular is reserved for the narrow case where no local Remix baseline exists yet for this lane (status reports `re_anchor`); it is not a recovery for "the local content changed."
 
 Operating rules:
 
 1. Start with `remix_collab_status` for repo-bound collaboration tasks whenever the current state is unclear.
-2. In a Remix-bound repo, Remix MCP tools are the required workflow layer for collaboration state and historical reasoning. Raw git mutations are allowed but never substitute for `remix_collab_finalize_turn`; after raw git mutations, run `remix_collab_status` and follow its `recommendedAction`. Raw git reads are only acceptable for exact repository facts such as specific commits, blame, ancestry, or raw patch details.
+2. In a Remix-bound repo, Remix MCP tools are the required workflow layer for collaboration state and historical reasoning. Raw git mutations are allowed but never substitute for automatic hook recording; after raw git mutations, run `remix_collab_status` if you need to inspect state. Raw git reads are only acceptable for exact repository facts such as specific commits, blame, ancestry, or raw patch details.
 3. Use preview tools before apply tools whenever both exist.
 4. Treat reconcile as a last-resort, high-risk path.
 5. Prefer bounded merge request diffs first, then expand only when necessary.
@@ -35,11 +35,11 @@ Operating rules:
 8. Use raw git for historical reads only after Remix memory has narrowed the relevant change, or when the user explicitly asks for exact commit, blame, ancestry, or raw patch details.
 9. Clearly explain local mutation risk before using tools that can modify the local repo.
 10. In a bound repo, Remix MCP tools are the required workflow layer for ordinary collaboration work.
-11. In a bound repo, exactly one final `remix_collab_finalize_turn` is required before the final user-facing response.
-12. `remix_collab_finalize_turn` is queued only. A remote change step does not exist yet until the finalize queue drains successfully.
-13. The final recording call must use the exact user prompt and your final assistant response.
+11. In a bound repo, automatic hook recording captures exactly one completed turn at the end of the user-facing response.
+12. Hook recording is queued. A remote change step does not exist yet until the finalize queue drains successfully.
+13. The runtime records the exact user prompt and final assistant response.
 14. If `remix_collab_status` reports `await_finalize`, use `remix_collab_drain_finalize_queue`, then re-check status before merge-related or recovery flows that depend on a remote recorded turn.
-15. Do not finish the turn before recording. Do not make additional repo mutations after the final turn-recording call unless you intend to record again.
+15. Do not make additional repo mutations after the final response unless you intend to capture them in a later turn.
 16. Do not duplicate core business logic in reasoning. Use the MCP tools to inspect and execute the workflow.
 
 When appropriate:
@@ -52,8 +52,8 @@ When appropriate:
 - 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
-- treat `remix_collab_finalize_turn` as local capture plus queueing, not immediate remote materialization
+- rely on automatic hook recording as the final turn recorder
+- treat hook recording as local capture plus queueing, not immediate remote materialization
 - use `remix_collab_drain_finalize_queue` and `remix_collab_status` when the workflow is blocked on `await_finalize`
 - use `remix_collab_review_queue` for reviewable merge requests, `remix_collab_my_merge_requests` for authored requests, and `remix_collab_list_app_merge_requests` for app-scoped MR flows with required `queue` set to `app_reviewable`, `app_outgoing`, or `app_related_visible`
 - use merge request tools for review and approval flows

package/dist/hook-post-collab.cjs

@@ -861,7 +861,7 @@ async function markPendingTurnConsultedMemory(sessionId) {
 // package.json
 var package_default = {
   name: "@remixhq/claude-plugin",
-  version: "0.1.20",
+  version: "0.1.21",
   description: "Claude Code plugin for Remix collaboration workflows",
   homepage: "https://github.com/RemixDotOne/remix-claude-plugin",
   license: "MIT",
@@ -900,7 +900,7 @@ var package_default = {
   },
   dependencies: {
     "@remixhq/core": "^0.1.15",
-    "@remixhq/mcp": "^0.1.15"
+    "@remixhq/mcp": "^0.1.16"
   },
   devDependencies: {
     "@types/node": "^25.4.0",