@remits/remits-cli 0.1.75 → 0.1.76

package/README.md

@@ -65,7 +65,8 @@ remits-cli install --skills --overwrite true
 - The platform repo's `docs/guides/` tree remains the single source of truth; the platform serves it from the classpath, so published CLI versions never carry guide content.
 - Authenticated users also get the **core Remits platform repo** locally. After guide sync (and on `auth` / discovery), `remits-cli` first reuses any existing local copy it already knows about, can detect directly (`REMITS_PLATFORM_DIR`, the running CLI source in dev, `~/remits`), or can discover under the configured scan roots; only if none is found does it clone `git@github.com:tmillhouse/remits.git` (default `~/remits`, override with `REMITS_PLATFORM_DIR`; cloning only runs in an interactive terminal). On each authenticated run it also fast-forwards the repo (`git pull --ff-only`, once per process) so back-stage analysis runs against current code — skipped automatically if the working tree is dirty, so local work is never clobbered. The repo is tracked in `~/.remits-cli/account-repos.json` under the reserved `platform` entry so agents can analyze back-stage seams and open a fix PR when a front-stage failure turns out to be platform brittleness.
 - Branch defaults to the current local git branch.
-- Data mode defaults to `test`. Use `remits-cli data-mode set prod` only for production investigation.
+- Data mode defaults to `test`. For `remits-cli test run`, that default is now enforced even if the most-recent authenticated session for the account is `prod`; a production test run therefore requires an explicit `--data-mode prod` on the command line. Use `remits-cli data-mode set prod` only for production investigation.
+- Avoid commas in individual test names. The `--names` filter is comma-delimited, so a single test case whose name contains commas cannot be targeted cleanly through `remits-cli test run --names ...`.
 - Test activity is streamed from websocket `TestSuite` events while final status is also polled from `/cli/test`.
 - Tool execution writes the full response to a separate file so large payloads do not bloat the session log.
 

package/index.js

@@ -1758,7 +1758,12 @@ async function testCommand(flags) {
   const { session, accountId } = resolveSessionContext(cwd, flags);
   const baseUrl = flags['base-url'] || session.baseUrl || DEFAULT_BASE_URL;
   const branchName = flags.branch || currentBranch(cwd);
-  const dataMode = resolveDataMode(flags, session);
+  // Test runs must default to test dataMode even when the most-recent authenticated
+  // session for the account is prod. Production test runs therefore require an explicit
+  // --data-mode prod on the command line.
+  const dataMode = hasExplicitDataModeFlag(flags)
+    ? resolveDataMode(flags, null)
+    : DEFAULT_DATA_MODE;
   const testRef = flags.test || flags['test-id'] || flags.name;
 
   if (!testRef) {

package/package.json

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

package/skills/remits-cli/SKILL.md

@@ -471,6 +471,10 @@ remits-cli test run --test "Invoice Tests" --names "specific test case"
 
 Tests run on the platform against your staged snapshot. They stream results in real-time. If they fail, fix the code, re-stage, and re-run.
 
+Important test-runner constraints:
+- `remits-cli test run` now defaults to `test` dataMode unless you explicitly pass `--data-mode prod`.
+- Do not put commas in individual `test("...")` names. The CLI `--names` filter is comma-delimited, so comma-bearing test names cannot be targeted cleanly as a single selected case.
+
 If no relevant Test component exists yet, consider creating one. Test components live in `components/tests/` and follow the same component structure. They provide permanent regression protection — every test you write today saves debugging time tomorrow.
 
 New test files use the `new_` prefix (e.g., `new_MyTest.groovy`). New tests have no database ID, so you must run them **by name**: `remits-cli test run --test "My Test"`. After committing, the platform assigns an ID and renames the file (e.g., `4_MyTest.groovy`) — then you can run by either ID or name.
@@ -1196,6 +1200,10 @@ remits-cli tools [--data-mode test|prod]
 remits-cli tool --name <toolName> [--input "{...}"] [--data-mode test|prod]
 ```
 
+For tests specifically:
+- If `--data-mode` is omitted, `remits-cli test run` uses `test`.
+- `--names` is comma-delimited, so keep individual test names comma-free.
+
 ## Troubleshooting
 
 | Symptom | Fix |