trackfw 8.0.0-rc1 → 8.0.0-rc3

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.
Files changed (2) hide show
  1. package/README.md +29 -13
  2. package/package.json +7 -7
package/README.md CHANGED
@@ -93,15 +93,23 @@ brew install kgsaran/tap/trackfw
93
93
  go install github.com/kgsaran/trackfw/cmd/trackfw@latest
94
94
  ```
95
95
 
96
- ### npm (pure Node.js — no binary)
96
+ ### npm
97
97
 
98
98
  ```bash
99
99
  npm install -g trackfw
100
100
  ```
101
101
 
102
- The npm package is pure Node.js — no compiled binary or postinstall download.
103
- It installs wherever Node.js ≥ 18 is installed. Shared behavior, including the AI
104
- integration lifecycle, follows the [CLI parity contract](docs/cli-parity.md).
102
+ From v8.0.0, the npm package is a ~80-line JavaScript shim that resolves
103
+ `@trackfw-bin/<platform>` at install time and executes the Go binary. **It is no
104
+ longer pure Node.js — it contains a compiled binary.** The binary arrives through
105
+ the `npm` channel rather than as a separate download, so organisations whose policy
106
+ allows `npm install` but blocks direct executable downloads remain served.
107
+
108
+ If your policy forbids compiled binaries in any form regardless of channel, this
109
+ version is a breaking change for you. See [Changelog](CHANGELOG.md) for the full
110
+ declaration.
111
+
112
+ Shared behavior follows the [command contract](docs/cli-parity.md).
105
113
 
106
114
  > **The CLI installs on Node ≥ 18 alone — the generated guard hooks do not run on
107
115
  > Node alone.** They are POSIX shell scripts and need a POSIX shell to execute. On
@@ -118,19 +126,17 @@ are than let you find them after adoption.
118
126
 
119
127
  **What we know works**
120
128
 
121
- - The three CLIs install (`npm install -g trackfw`, `pip install trackfw`, and the
122
- published `trackfw_<version>_windows_amd64.tar.gz`).
129
+ - All four channels install (`npm install -g trackfw`, `pip install trackfw`,
130
+ `curl … | sh` via `scripts/install.sh` on Git Bash / MSYS2 / Cygwin, and the
131
+ published `trackfw_<version>_windows_amd64.tar.gz` / `windows_arm64.tar.gz`). From v8.0.0 all
132
+ channels deliver the same Go binary; no separate Node.js or Python implementation.
123
133
  - Core governance commands — `req new`, `roadmap new`, `roadmap move`, `status`,
124
134
  `validate` — run, and artifacts are written with LF endings.
125
135
 
126
136
  **What we know does not work yet**
127
137
 
128
- - `scripts/install.sh` **refuses Windows**, even though we publish a Windows binary.
129
- Install manually from the release archive for now.
130
138
  - Our Windows CI still reports **known test failures**. They are mapped by root cause,
131
139
  not unknown — but they are not zero.
132
- - **Windows ARM64 is not built.** Only `windows_amd64` is published.
133
-
134
140
  **Guard hooks on Windows — measured, per agent CLI**
135
141
 
136
142
  The guard hooks are `.sh` scripts, executed by *your* AI agent CLI. Which shell that CLI
@@ -168,9 +174,19 @@ an issue with what you measured.
168
174
  pip install trackfw
169
175
  ```
170
176
 
171
- The pip package is pure Python 3.10+ — no compiled binary or postinstall
172
- download. Shared commands, validation rules, and by_agent behavior follow the
173
- [CLI parity contract](docs/cli-parity.md).
177
+ From v8.0.0, the pip package is a binary wheel in `gh-bin` format — **it contains
178
+ no Python files and no source**. The Go binary is installed into the PATH by pip.
179
+ `python -m trackfw` no longer works; use the `trackfw` executable directly.
180
+
181
+ Platforms not covered by the published wheels now fail at resolution time with
182
+ "no matching distribution found" — a clean failure instead of silently installing
183
+ the wrong thing. Eight wheels are published: `manylinux_2_17_x86_64`, `musllinux_1_2_x86_64`,
184
+ `manylinux_2_17_aarch64`, `musllinux_1_2_aarch64`, `macosx_10_9_x86_64`,
185
+ `macosx_11_0_arm64`, `win_amd64`, `win_arm64`. Linux publishes two wheels per
186
+ architecture (manylinux + musllinux), so Alpine and similar musl-based distributions
187
+ are covered.
188
+
189
+ Shared behavior follows the [command contract](docs/cli-parity.md).
174
190
 
175
191
  ---
176
192
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "trackfw",
3
- "version": "8.0.0-rc1",
3
+ "version": "8.0.0-rc3",
4
4
  "description": "Governance CLI for AI-native software delivery and AI coding agents. Enforces traceability: ADR → REQ → ROADMAP → kanban. Native support for Codex, Claude Code, Gemini CLI, Cursor, Copilot, Windsurf, Amazon Q, OpenCode, and Kiro.",
5
5
  "keywords": [
6
6
  "cli",
@@ -63,11 +63,11 @@
63
63
  "node": ">=18"
64
64
  },
65
65
  "optionalDependencies": {
66
- "@trackfw-bin/darwin-arm64": "8.0.0-rc1",
67
- "@trackfw-bin/darwin-x64": "8.0.0-rc1",
68
- "@trackfw-bin/linux-arm64": "8.0.0-rc1",
69
- "@trackfw-bin/linux-x64": "8.0.0-rc1",
70
- "@trackfw-bin/win32-arm64": "8.0.0-rc1",
71
- "@trackfw-bin/win32-x64": "8.0.0-rc1"
66
+ "@trackfw-bin/darwin-arm64": "8.0.0-rc3",
67
+ "@trackfw-bin/darwin-x64": "8.0.0-rc3",
68
+ "@trackfw-bin/linux-arm64": "8.0.0-rc3",
69
+ "@trackfw-bin/linux-x64": "8.0.0-rc3",
70
+ "@trackfw-bin/win32-arm64": "8.0.0-rc3",
71
+ "@trackfw-bin/win32-x64": "8.0.0-rc3"
72
72
  }
73
73
  }