@appchy/jarvis 0.1.118 → 0.1.119

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.
package/dist/bin.js CHANGED
@@ -10284,7 +10284,7 @@ import { createRequire as createRequire2 } from "module";
10284
10284
  var _require = createRequire2(import.meta.url);
10285
10285
  var VERSION2 = _require("../package.json").version ?? "0.0.0";
10286
10286
  var IS_DEV = String(_require("../package.json").name ?? "").endsWith("-dev");
10287
- var SHA = "1dfb739";
10287
+ var SHA = "0c6886b";
10288
10288
  var BUILT = "2026-09-12";
10289
10289
  var BUILD = SHA ?? "source";
10290
10290
  var BUILD_LABEL = `${SHA ? `${VERSION2} (${SHA}${BUILT ? ` ${BUILT}` : ""})` : `${VERSION2} (source)`}${IS_DEV ? " \u2014 development build" : ""}`;
@@ -5008,6 +5008,26 @@ def test_a_write_aimed_at_another_branch_is_refused():
5008
5008
  raise AssertionError("a write with --branch must be refused")
5009
5009
 
5010
5010
 
5011
+ def test_verify_takes_the_name_the_way_every_other_verb_does():
5012
+ # `move <name>`, `observed <task>`, `path <name>` all take a bare word, so that is
5013
+ # what people type for verify — and it read only `--task`. The positional landed
5014
+ # in `pos`, nothing looked at it, and nine gates ran against `""` for minutes and
5015
+ # recorded a result no item could claim. Observed live in `work/.verify` on
5016
+ # 2026-09-12 while a real run was in flight.
5017
+ seen = {}
5018
+ real = entry.cmd_verify
5019
+ try:
5020
+ entry.cmd_verify = lambda flags: seen.update(flags) or 0
5021
+ entry.dispatch("verify", ["an-item"], {}, {})
5022
+ assert seen.get("task") == "an-item", seen
5023
+ # An explicit flag still wins, so nothing changes for the tool surface.
5024
+ seen.clear()
5025
+ entry.dispatch("verify", ["positional"], {"task": "explicit"}, {})
5026
+ assert seen.get("task") == "explicit", seen
5027
+ finally:
5028
+ entry.cmd_verify = real
5029
+
5030
+
5011
5031
  def test_links_is_refused_a_branch_because_fix_writes_this_one():
5012
5032
  # It reports far more often than it fixes, which is what made listing it as a read
5013
5033
  # look right. `--fix` writes, and it writes to the tree that is CHECKED OUT — so
package/harness/work.py CHANGED
@@ -555,6 +555,13 @@ def dispatch(cmd, pos, flags, cfg) -> int:
555
555
  if cmd == "needs":
556
556
  return cmd_needs(flags)
557
557
  if cmd == "verify":
558
+ # A bare name is what the rest of this CLI takes — `move <name>`,
559
+ # `observed <task>`, `path <name>` — so it is what people type here too, and
560
+ # this read only `--task`. The positional went into `pos` and nothing looked
561
+ # at it: nine gates ran against an empty task name, for minutes, and recorded
562
+ # a result no item could claim. That reports identically to never having run.
563
+ if pos and not flags.get("task"):
564
+ flags = {**flags, "task": pos[0]}
558
565
  return cmd_verify(flags)
559
566
  if cmd == "observed":
560
567
  if not pos:
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@appchy/jarvis",
3
- "version": "0.1.118",
3
+ "version": "0.1.119",
4
4
  "description": "Jarvis — local AI coding assistant CLI",
5
5
  "private": false,
6
6
  "type": "module",
@@ -61,8 +61,8 @@
61
61
  "@jarvis/board": "0.1.0",
62
62
  "@jarvis/data": "0.1.0",
63
63
  "@jarvis/errors": "1.0.0",
64
- "@jarvis/rpc": "1.0.0",
65
64
  "@jarvis/logger": "1.0.0",
65
+ "@jarvis/rpc": "1.0.0",
66
66
  "@jarvis/types": "1.0.0",
67
67
  "@jarvis/typescript-config": "1.0.0",
68
68
  "@jarvis/ui": "0.1.0",