trackfw 9.1.0 → 9.2.0

package/README.md

@@ -22,7 +22,8 @@ Every piece of work traces back to a decision. Every decision links to a require
 > The CLIs install on Windows and core governance commands run — but the generated
 > guard hooks are POSIX shell scripts, and **on several agent CLIs they do not execute
 > on Windows.** They are written to disk and reported as installed while never running.
-> Native Windows hooks are in progress.
+> Native Windows hooks are planned, not yet in progress (tracked in
+> [REQ-2026-09-05](docs/req/REQ-2026-09-05-os-hooks-de-guard-nao-executam-no-windows-na-maioria-dos-clis-de-agente-e-o-validate-reporta-instalado.md)).
 > **Read [Windows support (partial)](#windows-support-partial) before adopting on Windows.**
 
 ---
@@ -117,8 +118,8 @@ Shared behavior follows the [command contract](docs/cli-parity.md).
 
 ### Windows support (partial)
 
-🚧 **Windows support is partial and in progress. Read this before adopting `trackfw`
-on Windows.**
+🚧 **Windows support is partial. Native Windows hooks are planned but not yet being
+worked on. Read this before adopting `trackfw` on Windows.**
 
 We publish a Windows binary and the npm/pip packages install on Windows. That is not
 the same as the tool working end to end, and we would rather tell you where the edges
@@ -477,7 +478,7 @@ A wave passes only when **all four** built-in checks are green:
 |---|---|
 | `mls_complete` | The wave has at least one ML and every ML is marked `**Status:** ✅` |
 | `acceptance_evidence` | Every ML has a non-empty `**Critérios de aceite:**` block with no unchecked `- [ ]` line |
-| `gates` | Every command declared under the wave's `**Gates da wave:**` fenced block exits 0 — a wave with no such block declares zero gates, and the barrier never invents one |
+| `gates` | Every command declared under the wave's `**Gates da wave:**` fenced block exits 0 — a wave with no such block declares zero gates, and the barrier never invents one. 🔴 Each non-empty, non-comment line runs as a **separate `sh -c`** — there is no shared state between lines; see rule 5 in `docs/cli-parity.md`. |
 | `validate` | `trackfw validate --json` reports `violations: 0` |
 
 ### Exit codes
@@ -891,6 +892,8 @@ trackfw is the only open-source CLI that links ADRs to requirements, requirement
 
 ## Contributing
 
+See [CONTRIBUTING.md](CONTRIBUTING.md) before opening a pull request (the guide is in Portuguese).
+
 ```bash
 git clone https://github.com/kgsaran/trackfw
 cd trackfw

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "trackfw",
-  "version": "9.1.0",
+  "version": "9.2.0",
   "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.",
   "keywords": [
     "cli",
@@ -63,11 +63,11 @@
     "node": ">=18"
   },
   "optionalDependencies": {
-    "@trackfw-bin/darwin-arm64": "9.1.0",
-    "@trackfw-bin/darwin-x64": "9.1.0",
-    "@trackfw-bin/linux-arm64": "9.1.0",
-    "@trackfw-bin/linux-x64": "9.1.0",
-    "@trackfw-bin/win32-arm64": "9.1.0",
-    "@trackfw-bin/win32-x64": "9.1.0"
+    "@trackfw-bin/darwin-arm64": "9.2.0",
+    "@trackfw-bin/darwin-x64": "9.2.0",
+    "@trackfw-bin/linux-arm64": "9.2.0",
+    "@trackfw-bin/linux-x64": "9.2.0",
+    "@trackfw-bin/win32-arm64": "9.2.0",
+    "@trackfw-bin/win32-x64": "9.2.0"
   }
 }