repo-harness 0.5.2 → 0.5.3

package/README.es.md

@@ -56,12 +56,11 @@ En un repositorio adoptado, la superficie se mantiene pequeña:
 | `tasks/contracts/`, `tasks/reviews/` y `.ai/harness/checks/` | Scope, verificación y evidencia de review para probar que el trabajo terminó. |
 | `.ai/harness/handoff/` y `tasks/current.md` | Session journal y estado resumible, derivados de workflow artifacts en vez de chat memory. |
 
-## Novedades en 0.5.2
+## Novedades en 0.5.3
 
-- **Tooling advisories más silenciosos.** Los update checks de SessionStart usan por defecto un timestamp cache semanal, para que los avisos de Waza y CodeGraph no aparezcan en cada sesión.
-- **Safety hooks locales revisados.** `repo-harness security scan` separa active findings y reviewed exceptions; los hooks user-level warning-only necesitan exact command match, y los comandos de alto riesgo siguen activos.
-- **Setup checks más limpios.** `repo-harness setup check --check-updates` trata el skip de DB de gbrain fast-mode como readiness aceptado, pero mantiene visibles los warnings reales de gbrain.
-- **Cross-review más resistente.** El skill bundled `claude-review` puede recuperar resultados print-mode con stdout vacío desde los transcripts de sesión de Claude Code.
+- **Runtime updates con versión fija.** `repo-harness update --version <version>` ahora instala el package `repo-harness@<version>` solicitado, en vez de ser interceptado por el shortcut global de versión de la CLI.
+- **Version shortcut preservado.** `repo-harness --version` y `repo-harness -V` siguen mostrando la versión de la CLI cuando se usan en el nivel superior.
+- **Patch-only surface.** No cambian hook routes, setup checks, security scan ni workflow contracts, salvo el fix del option del comando update.
 
 ## Qué hace el producto
 
@@ -378,8 +377,8 @@ Guards habituales:
 
 ## Release actual
 
-- npm package: `repo-harness@0.5.2`
-- Generated workflow stamp: `repo-harness@0.5.2+template@0.5.2`
+- npm package: `repo-harness@0.5.3`
+- Generated workflow stamp: `repo-harness@0.5.3+template@0.5.3`
 - GitHub repository: `Ancienttwo/repo-harness`
 - Release history: [`docs/CHANGELOG.md`](docs/CHANGELOG.md)
 

package/README.fr.md

@@ -56,12 +56,11 @@ Dans un dépôt adopté, la surface à comprendre reste volontairement réduite
 | `tasks/contracts/`, `tasks/reviews/` et `.ai/harness/checks/` | Scope, vérification et preuves de review pour démontrer que le travail est terminé. |
 | `.ai/harness/handoff/` et `tasks/current.md` | Session journal et état resumable dérivés des workflow artifacts plutôt que de la chat memory. |
 
-## Nouveautés de la 0.5.2
+## Nouveautés de la 0.5.3
 
-- **Tooling advisories plus calmes.** Les checks update de SessionStart utilisent désormais un cache timestamp d'une semaine par défaut, afin que les advisories Waza et CodeGraph restent utiles sans apparaître à chaque session.
-- **Safety hooks locaux reviewés.** `repo-harness security scan` sépare les active findings des reviewed exceptions, avec exact command match pour les hooks user-level warning-only ; les commandes à haut risque restent actives.
-- **Setup checks plus propres.** `repo-harness setup check --check-updates` traite le skip DB de gbrain fast-mode comme un état readiness accepté, tout en gardant les vrais warnings gbrain visibles.
-- **Cross-review plus robuste.** Le skill bundled `claude-review` peut récupérer les résultats print-mode à stdout vide depuis les transcripts de session Claude Code.
+- **Runtime updates épinglés.** `repo-harness update --version <version>` installe maintenant le package `repo-harness@<version>` demandé au lieu d'être intercepté par le raccourci global de version de la CLI.
+- **Version shortcut préservé.** `repo-harness --version` et `repo-harness -V` continuent d'afficher la version CLI lorsqu'ils sont utilisés au niveau supérieur.
+- **Patch-only surface.** Aucun changement de hook route, setup check, security scan ou workflow contract au-delà du fix de l'option du command update.
 
 ## Ce que fait le produit
 
@@ -382,8 +381,8 @@ Guards courants :
 
 ## Release actuelle
 
-- npm package : `repo-harness@0.5.2`
-- Generated workflow stamp : `repo-harness@0.5.2+template@0.5.2`
+- npm package : `repo-harness@0.5.3`
+- Generated workflow stamp : `repo-harness@0.5.3+template@0.5.3`
 - GitHub repository : `Ancienttwo/repo-harness`
 - Release history : [`docs/CHANGELOG.md`](docs/CHANGELOG.md)
 

package/README.ja.md

@@ -47,12 +47,11 @@ Agent に完全な PRD または Sprint を渡せば、あとは review and `nex
 | `tasks/contracts/`, `tasks/reviews/`, `.ai/harness/checks/` | 作業完了を証明する scope、verification、review evidence。 |
 | `.ai/harness/handoff/` と `tasks/current.md` | chat memory ではなく workflow artifacts から派生する session journal と resumable status。 |
 
-## 0.5.2 の新機能
+## 0.5.3 の新機能
 
-- **静かな tooling advisory。** SessionStart update check はデフォルトで 1 週間の timestamp cache を使い、Waza と CodeGraph の advisory が毎 session で出続けないようにしました。
-- **Reviewed local safety hooks。** `repo-harness security scan` は active findings と reviewed exceptions を分離し、user-level warning-only hook は exact command match の場合だけ reviewed 扱いにします。高リスク command は引き続き active です。
-- **Cleaner setup checks。** `repo-harness setup check --check-updates` は gbrain fast-mode DB skip を受け入れ済み readiness として扱い、実際の gbrain warning はそのまま表示します。
-- **Resilient cross-review。** bundled `claude-review` skill は Claude Code print-mode の stdout が空でも session transcript から最終出力を復旧できます。
+- **Pinned runtime updates。** `repo-harness update --version <version>` は、top-level CLI version shortcut に横取りされず、指定された `repo-harness@<version>` package をインストールするようになりました。
+- **Version shortcut preserved。** `repo-harness --version` と `repo-harness -V` は、top level で使った場合は引き続き CLI version を出力します。
+- **Patch-only surface。** update command option fix 以外に、hook route、setup check、security scan、workflow contract の動作変更はありません。
 
 ## repo-harness は何をするか
 
@@ -352,8 +351,8 @@ hook がブロックしたときは、まず terminal の構造化された出
 
 ## 現在の Release
 
-- npm package：`repo-harness@0.5.2`
-- Generated workflow stamp：`repo-harness@0.5.2+template@0.5.2`
+- npm package：`repo-harness@0.5.3`
+- Generated workflow stamp：`repo-harness@0.5.3+template@0.5.3`
 - GitHub repository：`Ancienttwo/repo-harness`
 - Release history：[`docs/CHANGELOG.md`](docs/CHANGELOG.md)
 

package/README.md

@@ -50,19 +50,15 @@ In an adopted repo, the surface area is intentionally small:
 | `tasks/contracts/`, `tasks/reviews/`, and `.ai/harness/checks/` | Scope, verification, and review evidence for proving the work is done. |
 | `.ai/harness/handoff/` and `tasks/current.md` | Session journal and resumable status, derived from workflow artifacts instead of chat memory. |
 
-## What's New in 0.5.2
-
-- **Quieter tooling advisories.** SessionStart update checks now use a weekly
-  timestamp cache by default, so Waza and CodeGraph advisories stay useful
-  without firing on every new agent session.
-- **Reviewed local safety hooks.** `repo-harness security scan` separates
-  active findings from reviewed exceptions, using exact command matches for
-  user-level warning-only hooks while keeping high-risk commands blocking.
-- **Cleaner setup checks.** `repo-harness setup check --check-updates` now
-  treats gbrain fast-mode DB skips as accepted readiness and keeps real gbrain
-  warnings visible.
-- **More resilient cross-review.** The bundled `claude-review` skill can recover
-  empty-stdout print-mode results from Claude Code session transcripts.
+## What's New in 0.5.3
+
+- **Pinned runtime updates.** `repo-harness update --version <version>` now
+  installs the requested `repo-harness@<version>` package instead of being
+  intercepted by the top-level CLI version shortcut.
+- **Version shortcut preserved.** `repo-harness --version` and
+  `repo-harness -V` still print the CLI version when used at the top level.
+- **Patch-only surface.** No hook route, setup check, security scan, or workflow
+  contract behavior changes beyond the update command option fix.
 
 ## What repo-harness Does
 
@@ -459,8 +455,8 @@ Most common guards:
 
 ## Current Release
 
-- npm package: `repo-harness@0.5.2`
-- Generated workflow stamp: `repo-harness@0.5.2+template@0.5.2`
+- npm package: `repo-harness@0.5.3`
+- Generated workflow stamp: `repo-harness@0.5.3+template@0.5.3`
 - GitHub repository: `Ancienttwo/repo-harness`
 - Release history: [`docs/CHANGELOG.md`](docs/CHANGELOG.md)
 

package/README.zh-CN.md

@@ -43,17 +43,14 @@ handoff、检查结果和 review evidence 写回项目文件，让下一个 agen
 | `tasks/contracts/`、`tasks/reviews/`、`.ai/harness/checks/` | 证明完成所需的 scope、verification 和 review evidence。 |
 | `.ai/harness/handoff/` 和 `tasks/current.md` | session journal 与可恢复状态，从 workflow artifacts 派生，而不是依赖聊天记忆。 |
 
-## 0.5.2 新特性
-
-- **更安静的 tooling advisory。** SessionStart update check 默认使用一周
-  timestamp cache，Waza 和 CodeGraph advisory 不会每个新 session 都触发。
-- **可审阅的本地 safety hooks。** `repo-harness security scan` 会把 active
-  findings 与 reviewed exceptions 分开；user-level warning-only hooks 必须 exact
-  command match，高风险命令仍然保持 active。
-- **更干净的 setup check。** `repo-harness setup check --check-updates` 会把
-  gbrain fast-mode DB skip 当成已接受的 readiness 状态，同时保留真实 gbrain warning。
-- **更稳的 cross-review。** bundled `claude-review` skill 可以从 Claude Code
-  session transcript 恢复 print-mode 空 stdout 的最终输出。
+## 0.5.3 新特性
+
+- **可 pin 的 runtime update。** `repo-harness update --version <version>` 现在会
+  安装指定的 `repo-harness@<version>` package，不再被顶层 CLI version shortcut 抢占。
+- **保留 version shortcut。** `repo-harness --version` 和 `repo-harness -V` 在顶层使用时
+  仍然输出 CLI version。
+- **Patch-only surface。** 除 update command option 修复外，hook route、setup check、
+  security scan 和 workflow contract 行为不变。
 
 ## 产品做什么
 
@@ -413,8 +410,8 @@ hook block 工作时，先看 terminal 里的结构化输出。核心字段是
 
 ## 当前 Release
 
-- npm package：`repo-harness@0.5.2`
-- Generated workflow stamp：`repo-harness@0.5.2+template@0.5.2`
+- npm package：`repo-harness@0.5.3`
+- Generated workflow stamp：`repo-harness@0.5.3+template@0.5.3`
 - GitHub repository：`Ancienttwo/repo-harness`
 - Release history：[`docs/CHANGELOG.md`](docs/CHANGELOG.md)
 

package/assets/skill-version.json

@@ -1,6 +1,6 @@
 {
-  "version": "0.5.2",
-  "templateVersion": "0.5.2",
+  "version": "0.5.3",
+  "templateVersion": "0.5.3",
   "skillName": "repo-harness",
   "contractId": "tasks-first-harness-v1",
   "retiredAliases": [
@@ -135,6 +135,10 @@
     {
       "version": "0.5.2",
       "description": "Adds weekly tooling-update advisory caching, reviewed security exceptions, gbrain fast-doctor warning handling, and Claude review transcript recovery"
+    },
+    {
+      "version": "0.5.3",
+      "description": "Fixes repo-harness update --version so the update command can install a pinned package version without being intercepted by the top-level CLI version flag"
     }
   ],
   "generatedProjectStamp": {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "repo-harness",
-  "version": "0.5.2",
+  "version": "0.5.3",
   "description": "Installs, migrates, audits, and repairs repo-local agentic development harnesses",
   "license": "MIT",
   "repository": {

package/src/cli/index.ts

@@ -54,7 +54,7 @@ export function buildProgram(): Command {
   program
     .name('repo-harness')
     .description('Make Claude/Codex work resumable, reviewable, and repo-local')
-    .version(CLI_VERSION)
+    .addHelpText('after', '\nGlobal shortcuts:\n  -V, --version  output the version number')
     .exitOverride();
 
   program
@@ -421,9 +421,18 @@ export function buildProgram(): Command {
   return program;
 }
 
+export async function runCli(argv: string[] = process.argv): Promise<void> {
+  const args = argv.slice(2);
+  if (args.length === 1 && (args[0] === '--version' || args[0] === '-V')) {
+    console.log(CLI_VERSION);
+    return;
+  }
+  await buildProgram().parseAsync(argv);
+}
+
 if (import.meta.main) {
   try {
-    await buildProgram().parseAsync(process.argv);
+    await runCli(process.argv);
   } catch (err) {
     const e = err as { exitCode?: number; message?: string };
     if (typeof e.exitCode === 'number') process.exit(e.exitCode);