@remits/remits-cli 0.1.72 → 0.1.73

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@remits/remits-cli",
-  "version": "0.1.72",
+  "version": "0.1.73",
   "description": "Local CLI for auth, component sync, and live test execution against Remits",
   "license": "MIT",
   "private": false,

package/skills/remits-cli/SKILL.md

@@ -657,10 +657,22 @@ surface, not a deploy.
 - `mcp_component_edit` `mode:'stage'` → writes the staging cache (Redis). `mode:'commit'` → writes the field
   to the **live DB** and **clears** that component's staging entries. `editMode:'replace'` swaps the whole
   field; `editMode:'targeted'` does anchor-verified line edits.
+- **A `mode:'commit'` promotes ALL of that component's staged fields in one save, not just the named field.**
+  Committing `source` also flushes a staged `path` (etc.) and then clears the whole staging entry. The result
+  reports the full set in `persist.committedFields` + `persist.stagingCleared` — trust that, and do **not**
+  try to "finish" by re-committing a sibling field that was already flushed.
 - `mcp_component_commit` (`read`/`commit`/`clear`) enumerates staged entries and can flush or clear them.
+- **An empty staging scope is the clean, already-promoted state — not a failure.** A `commit`/`clear` against a
+  component (or scope) with nothing staged returns a benign success (`alreadyClean:true`, `committedCount:0`),
+  not an error. "No staged changes found" means *already promoted*, never *partial commit*. The staging cache
+  is a dev-override artifact; its emptiness is the goal. Verify what's actually in the DB with
+  `mcp_component_view` / `mcp_integration_validate` — never gate a commit/verification on staging-cache state.
 - **Commit bypasses the staged-override path entirely** (it writes the DB and clears staging), so committing
   is the way to make a change durable and to stop a stale staged entry from shadowing the live component in
   later test runs.
+- `remits-cli components sync` (the `commit`/`sync` mode on the `components` endpoint) syncs the DB from the
+  git remote and then **also clears the staged entries** for the synced components, so a clean commit leaves a
+  clean staging cache on both the CLI and MCP-tool surfaces.
 
 ### Stale after sync / commit (the in-memory compile cache)