@agenit/cli 1.0.2 → 1.0.3
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/CHANGELOG.md +53 -0
- package/cli.js +371 -278
- package/package.json +2 -1
package/CHANGELOG.md
ADDED
|
@@ -0,0 +1,53 @@
|
|
|
1
|
+
# Changelog
|
|
2
|
+
|
|
3
|
+
All notable changes to `@agenit/cli` are documented here. The project
|
|
4
|
+
follows [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
|
|
5
|
+
|
|
6
|
+
## [1.0.3] - 2026-05-07
|
|
7
|
+
|
|
8
|
+
### Fixed
|
|
9
|
+
- **Artefacts now land in the user's project, not in the install repo.**
|
|
10
|
+
Previously every relative path in `flow.toml` (gemini `working_dir`,
|
|
11
|
+
`memory_dir`, `codedigest_dir`, `mempalace`, sona/reasoning/rvf)
|
|
12
|
+
resolved against the directory holding `flow.toml`, so spec.md /
|
|
13
|
+
hld.md / generated source from a `/feature` run landed inside the
|
|
14
|
+
agenIT install repo regardless of where you invoked `agenit`.
|
|
15
|
+
Project-side paths now resolve against the directory you ran
|
|
16
|
+
`agenit` from. Install-side paths (`soul_path`, `prompts_dir`,
|
|
17
|
+
`templates_dir`, `tools_dir`, `flow_home`) still resolve against
|
|
18
|
+
the install dir, so shipped assets remain shared.
|
|
19
|
+
- **Terminal resize no longer duplicates / corrupts REPL output.** The
|
|
20
|
+
Ink frontend now subscribes to `stdout`'s `resize` event, so Box
|
|
21
|
+
widths stay in sync with the actual terminal width and the
|
|
22
|
+
`<Static>` block diffs cleanly instead of re-flushing history.
|
|
23
|
+
- **`/feature` side rail updates during the speckit / export phases.**
|
|
24
|
+
The first ~2 minutes of a run no longer look frozen — the rail
|
|
25
|
+
shows "Spec-Kit (specify → plan → tasks)" and "Export spec → SWE.1"
|
|
26
|
+
before the V-Model nodes start firing their own stage updates.
|
|
27
|
+
|
|
28
|
+
### Added
|
|
29
|
+
- **Cross-platform Gemini CLI discovery.** `binary` in `flow.toml` can
|
|
30
|
+
now be a bare command name (`"gemini"` is the new default) — agenIT
|
|
31
|
+
searches `PATH` (with `PATHEXT` extensions on Windows) and falls
|
|
32
|
+
back to well-known install dirs per OS:
|
|
33
|
+
- macOS: `/opt/homebrew/bin`, `/usr/local/bin`, `~/.npm-global/bin`
|
|
34
|
+
- Linux: `/usr/local/bin`, `/usr/bin`, `/home/linuxbrew/.linuxbrew/bin`,
|
|
35
|
+
`~/.npm-global/bin`, `~/.local/bin`
|
|
36
|
+
- Windows: `%APPDATA%\npm`, `%ProgramFiles%\nodejs`,
|
|
37
|
+
`%LOCALAPPDATA%\Programs\gemini-cli`
|
|
38
|
+
|
|
39
|
+
Absolute paths are still honoured verbatim. On Windows the spawned
|
|
40
|
+
process uses `shell: true` so `.cmd` / `.bat` shims execute correctly
|
|
41
|
+
when invoked without their extension.
|
|
42
|
+
|
|
43
|
+
### Changed
|
|
44
|
+
- Default `flow.toml` ships `binary = "gemini"` (was the macOS
|
|
45
|
+
Homebrew absolute path) and drops the leading `../` from
|
|
46
|
+
`memory_dir` / `codedigest_dir` so artefacts land *inside* the
|
|
47
|
+
user's project.
|
|
48
|
+
|
|
49
|
+
### Tests
|
|
50
|
+
- New `tests/config-paths.test.ts` pins the install vs project anchor
|
|
51
|
+
split and the absolute-path passthrough.
|
|
52
|
+
- New `tests/binary-resolver.test.ts` covers PATH walking, absolute
|
|
53
|
+
path probing, and missing-binary handling.
|