@appchy/jarvis 0.1.75 → 0.1.76
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 +1 -1
- package/harness/presets/appchy/PRESET.md +8 -0
- package/package.json +4 -4
package/dist/bin.js
CHANGED
|
@@ -10109,7 +10109,7 @@ import { createRequire as createRequire2 } from "module";
|
|
|
10109
10109
|
var _require = createRequire2(import.meta.url);
|
|
10110
10110
|
var VERSION2 = _require("../package.json").version ?? "0.0.0";
|
|
10111
10111
|
var IS_DEV = String(_require("../package.json").name ?? "").endsWith("-dev");
|
|
10112
|
-
var SHA = "
|
|
10112
|
+
var SHA = "7a9afe2";
|
|
10113
10113
|
var BUILT = "2026-09-10";
|
|
10114
10114
|
var BUILD = SHA ?? "source";
|
|
10115
10115
|
var BUILD_LABEL = `${SHA ? `${VERSION2} (${SHA}${BUILT ? ` ${BUILT}` : ""})` : `${VERSION2} (source)`}${IS_DEV ? " \u2014 development build" : ""}`;
|
|
@@ -159,6 +159,14 @@ preference — `jarvis work where` resolves it. Tiny mechanics need no sign-off.
|
|
|
159
159
|
from `jarvis work code <region>` overlap and the feature graph, not a lint. A cheap reshape happens in
|
|
160
160
|
the plan; a real trade-off routes through `AskUserQuestion` and lands as a new rule.
|
|
161
161
|
|
|
162
|
+
**A completed brief records what was BELIEVED then; it is not a statement about now.** Anything under
|
|
163
|
+
`complete/` or in a released cut describes the world its author was working in, and the tools it
|
|
164
|
+
asserts have moved since. Quote one only with its date attached, and check any claim about how a
|
|
165
|
+
command behaves against the command before planning on it. Three such claims were found false in one
|
|
166
|
+
evening across two repos — each specific, plausible, recently dated, and sitting in a file whose whole
|
|
167
|
+
job is to be trusted. Nothing catches this class: the sentence points at no file, so no link check
|
|
168
|
+
goes red, and the tree does not know it is a claim.
|
|
169
|
+
|
|
162
170
|
The completion gate enforces all three: a task that changed behaviour is not complete until every
|
|
163
171
|
`AC-nn` it targeted has passing evidence, `<feature>.md` (+ its `state:`), the durable rules and any
|
|
164
172
|
touched briefs match what was actually built. `map_scope {edits}` over the edit set flags governance the
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@appchy/jarvis",
|
|
3
|
-
"version": "0.1.
|
|
3
|
+
"version": "0.1.76",
|
|
4
4
|
"description": "Jarvis — local AI coding assistant CLI",
|
|
5
5
|
"private": false,
|
|
6
6
|
"type": "module",
|
|
@@ -58,15 +58,15 @@
|
|
|
58
58
|
"vitest": "^2.1.0",
|
|
59
59
|
"@jarvis/agents": "1.0.0",
|
|
60
60
|
"@jarvis/anthropic": "1.0.0",
|
|
61
|
-
"@jarvis/data": "0.1.0",
|
|
62
61
|
"@jarvis/board": "0.1.0",
|
|
62
|
+
"@jarvis/data": "0.1.0",
|
|
63
63
|
"@jarvis/errors": "1.0.0",
|
|
64
64
|
"@jarvis/logger": "1.0.0",
|
|
65
65
|
"@jarvis/rpc": "1.0.0",
|
|
66
66
|
"@jarvis/types": "1.0.0",
|
|
67
|
+
"@jarvis/typescript-config": "1.0.0",
|
|
67
68
|
"@jarvis/ui": "0.1.0",
|
|
68
|
-
"@jarvis/vitest-config": "1.0.0"
|
|
69
|
-
"@jarvis/typescript-config": "1.0.0"
|
|
69
|
+
"@jarvis/vitest-config": "1.0.0"
|
|
70
70
|
},
|
|
71
71
|
"scripts": {
|
|
72
72
|
"dev": "tsx watch src/bin.ts start --foreground",
|