repo-harness 0.6.0 → 0.7.1

package/.agents/skills/repo-harness-chatgpt-browser/SKILL.md

@@ -0,0 +1,106 @@
+---
+name: repo-harness-chatgpt-browser
+description: Use when the user wants Codex to consult their logged-in ChatGPT Web session through repo-harness browser engine for planning, architecture review, PRD critique, or Codex goal generation.
+---
+
+# repo-harness ChatGPT Browser
+
+Use this skill when the user asks to consult ChatGPT Web, GPT Pro, browser GPT, or a logged-in ChatGPT account through repo-harness.
+
+## Rules
+
+1. This uses the user's logged-in ChatGPT Web browser session, not the OpenAI API.
+2. Do not ask for or handle passwords, SSO secrets, 2FA codes, cookies, browser storage, or tokens.
+3. Before a non-dry-run consult, state that it may create or continue a real ChatGPT Web conversation.
+4. Prefer dry-run first when files are involved:
+
+```bash
+repo-harness chatgpt browser-consult --repo . --dry-run --prompt "<prompt>" --file <path>
+```
+
+5. For readiness, run:
+
+```bash
+repo-harness chatgpt browser-doctor --repo .
+```
+
+6. Use browser consult for planning, review, critique, and goal generation. Do not use it as the executor for code edits.
+7. Save useful results into repo-harness artifacts with repo-relative `--write-output` paths such as:
+
+```text
+.ai/harness/handoff/chatgpt-review.md
+.ai/harness/handoff/codex-goal.md
+plans/prds/*.prd.md
+plans/sprints/*.sprint.md
+```
+
+8. If login, captcha, workspace picker, or SSO is required, stop and ask the user to complete it in the browser.
+9. Do not enable remote CDP unless the user explicitly asked for remote browser control and the security boundary is documented.
+10. For MCP usage, require the server to be started with:
+
+```bash
+repo-harness mcp serve --repo . --enable-chatgpt-browser
+```
+
+11. Do not rely on provider stdout `Artifact:` / `Output:` paths being imported. Browser engine session records save prompt, transcript, output, metadata, and trusted provider IDs; ordinary stdout paths are ignored.
+12. Native provider uses the current ChatGPT Web model selection. Do not pass `--model` or `--thinking` with `--provider native`; use Oracle when model selection is required.
+
+## Common Commands
+
+Dry-run consult:
+
+```bash
+repo-harness chatgpt browser-consult \
+  --repo . \
+  --dry-run \
+  --prompt "Review this sprint and return execution risks." \
+  --file plans/sprints/example.sprint.md
+```
+
+Oracle provider consult:
+
+```bash
+repo-harness chatgpt browser-consult \
+  --repo . \
+  --provider oracle \
+  --prompt "Review this PRD and return risks plus a smallest next step." \
+  --file plans/prds/example.prd.md \
+  --write-output .ai/harness/handoff/chatgpt-review.md
+```
+
+Native provider spike:
+
+```bash
+repo-harness chatgpt browser-doctor --repo . --provider native
+repo-harness chatgpt browser-consult \
+  --repo . \
+  --provider native \
+  --browser-channel chrome \
+  --keep-browser \
+  --prompt "Reply exactly OK"
+```
+
+Use native provider only when the user is ready for a visible ChatGPT Web run. If login is required, keep the browser open and have the user complete login manually; do not request or handle credentials.
+
+Read the result:
+
+```bash
+repo-harness chatgpt browser-list --repo .
+repo-harness chatgpt browser-session --repo . <sessionId>
+repo-harness chatgpt browser-open --repo . <sessionId>
+```
+
+Continue from a saved session:
+
+```bash
+repo-harness chatgpt browser-followup \
+  --repo . \
+  --session <sessionId> \
+  --prompt "Challenge the previous result and return the smallest next step."
+```
+
+Plan cleanup before deleting local session records:
+
+```bash
+repo-harness chatgpt browser-cleanup --repo . --status dry_run --limit 20
+```

package/README.es.md

@@ -1,7 +1,7 @@
 # repo-harness
 
 <p align="center">
-  <img src="docs/images/image.png" alt="One next button joining Claude and Codex under repo-harness workflow rules" width="760">
+  <img src="docs/images/repo-harness-gptpro.png" alt="repo-harness architecture and ChatGPT Pro local planner workflow diagram" width="960">
 </p>
 
 `repo-harness` convierte las sesiones de programación con Claude/Codex en un
@@ -56,17 +56,17 @@ 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.6.0
+## Novedades en 0.7.1
 
-- **Transactional adoption plans.** `repo-harness adopt --dry-run --json` ahora
-  emite un operation plan protocol v1 con IDs estables, summary, content hashes
-  y rollback metadata.
-- **Bootstrap files gestionados por el manifest.** Los templates iniciales
-  `docs/spec.md`, `tasks/todos.md`, `tasks/current.md` y `tasks/lessons.md`
-  ahora salen del workflow contract manifest, no de strings locales del planner.
-- **Apply TypeScript experimental.** `repo-harness adopt --experimental-ts-apply`
-  puede aplicar el safe operation subset con atomic writes, target locks,
-  backups y preflight rejection para boundaries self-host no soportadas.
+- **ChatGPT browser engine.** `repo-harness chatgpt browser-*` crea sesiones
+  ChatGPT Web repo-locales con archivos revisados por policy, sin usar OpenAI API.
+- **MCP browser tools opt-in.** `repo-harness mcp serve
+  --enable-chatgpt-browser` expone consult/read/list/continue/open; por defecto
+  estos tools siguen desactivados.
+- **Oracle y native providers.** El engine incluye un Oracle browser wrapper y
+  un spike native vía Chrome instalado + CDP local.
+- **Hosted CI y release smoke.** El repo añade un GitHub CI gate y un tarball
+  install smoke que arranca los binarios empaquetados de `repo-harness`.
 
 ## Qué hace el producto
 
@@ -383,8 +383,8 @@ Guards habituales:
 
 ## Release actual
 
-- npm package: `repo-harness@0.6.0`
-- Generated workflow stamp: `repo-harness@0.6.0+template@0.6.0`
+- npm package: `repo-harness@0.7.1`
+- Generated workflow stamp: `repo-harness@0.7.1+template@0.7.1`
 - GitHub repository: `Ancienttwo/repo-harness`
 - Release history: [`docs/CHANGELOG.md`](docs/CHANGELOG.md)
 

package/README.fr.md

@@ -1,7 +1,7 @@
 # repo-harness
 
 <p align="center">
-  <img src="docs/images/image.png" alt="One next button joining Claude and Codex under repo-harness workflow rules" width="760">
+  <img src="docs/images/repo-harness-gptpro.png" alt="repo-harness architecture and ChatGPT Pro local planner workflow diagram" width="960">
 </p>
 
 `repo-harness` transforme les sessions de code Claude/Codex en workflow
@@ -56,18 +56,17 @@ 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.6.0
+## Nouveautés de la 0.7.1
 
-- **Transactional adoption plans.** `repo-harness adopt --dry-run --json` émet
-  maintenant un operation plan protocol v1 avec IDs stables, summary, content
-  hashes et rollback metadata.
-- **Bootstrap files gérés par le manifest.** Les templates initiaux
-  `docs/spec.md`, `tasks/todos.md`, `tasks/current.md` et `tasks/lessons.md`
-  viennent désormais du workflow contract manifest plutôt que de strings locales
-  au planner.
-- **Apply TypeScript expérimental.** `repo-harness adopt --experimental-ts-apply`
-  peut appliquer le safe operation subset avec atomic writes, target locks,
-  backups et preflight rejection des boundaries self-host non prises en charge.
+- **ChatGPT browser engine.** `repo-harness chatgpt browser-*` crée des sessions
+  ChatGPT Web repo-locales avec des fichiers contrôlés par policy, sans OpenAI API.
+- **MCP browser tools opt-in.** `repo-harness mcp serve
+  --enable-chatgpt-browser` expose consult/read/list/continue/open, désactivés
+  par défaut.
+- **Oracle et native providers.** Le moteur inclut un Oracle browser wrapper et
+  un spike native via Chrome installé et CDP local.
+- **Hosted CI et release smoke.** Le dépôt ajoute un GitHub CI gate et un
+  tarball install smoke qui démarre les binaires packagés `repo-harness`.
 
 ## Ce que fait le produit
 
@@ -388,8 +387,8 @@ Guards courants :
 
 ## Release actuelle
 
-- npm package : `repo-harness@0.6.0`
-- Generated workflow stamp : `repo-harness@0.6.0+template@0.6.0`
+- npm package : `repo-harness@0.7.1`
+- Generated workflow stamp : `repo-harness@0.7.1+template@0.7.1`
 - GitHub repository : `Ancienttwo/repo-harness`
 - Release history : [`docs/CHANGELOG.md`](docs/CHANGELOG.md)
 

package/README.ja.md

@@ -1,7 +1,7 @@
 # repo-harness
 
 <p align="center">
-  <img src="docs/images/image.png" alt="One next button joining Claude and Codex under repo-harness workflow rules" width="760">
+  <img src="docs/images/repo-harness-gptpro.png" alt="repo-harness architecture and ChatGPT Pro local planner workflow diagram" width="960">
 </p>
 
 `repo-harness` は、Claude/Codex のコーディング session を、繰り返し使える
@@ -47,11 +47,12 @@ 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.6.0 の新機能
+## 0.7.1 の新機能
 
-- **Transactional adoption plans。** `repo-harness adopt --dry-run --json` は、安定した ID、summary、content hash、rollback metadata を含む protocol v1 operation plan を出力します。
-- **Manifest-owned bootstrap files。** 初期 `docs/spec.md`、`tasks/todos.md`、`tasks/current.md`、`tasks/lessons.md` templates は、planner-local strings ではなく workflow contract manifest から来るようになりました。
-- **Experimental TypeScript apply。** `repo-harness adopt --experimental-ts-apply` は、atomic writes、target locks、backups、unsupported self-host boundary の preflight rejection を使って safe operation subset を適用できます。
+- **ChatGPT browser engine。** `repo-harness chatgpt browser-*` は、OpenAI API を使わず、policy-checked な repo-local ChatGPT Web consult session を作れます。
+- **Opt-in MCP browser tools。** `repo-harness mcp serve --enable-chatgpt-browser` のときだけ consult/read/list/continue/open tools を公開し、デフォルトでは無効です。
+- **Oracle and native providers。** Oracle browser wrapper と、installed Chrome + local CDP を使う native spike を含みます。
+- **Hosted CI and release smoke。** GitHub CI gate と、packaged `repo-harness` binaries を起動する tarball install smoke を追加しました。
 
 ## repo-harness は何をするか
 
@@ -351,8 +352,8 @@ hook がブロックしたときは、まず terminal の構造化された出
 
 ## 現在の Release
 
-- npm package：`repo-harness@0.6.0`
-- Generated workflow stamp：`repo-harness@0.6.0+template@0.6.0`
+- npm package：`repo-harness@0.7.1`
+- Generated workflow stamp：`repo-harness@0.7.1+template@0.7.1`
 - GitHub repository：`Ancienttwo/repo-harness`
 - Release history：[`docs/CHANGELOG.md`](docs/CHANGELOG.md)
 

package/README.md

@@ -1,7 +1,7 @@
 # repo-harness
 
 <p align="center">
-  <img src="docs/images/image.png" alt="One next button joining Claude and Codex under repo-harness workflow rules" width="760">
+  <img src="docs/images/repo-harness-gptpro.png" alt="repo-harness architecture and ChatGPT Pro local planner workflow diagram" width="960">
 </p>
 
 `repo-harness` turns Claude/Codex coding sessions into a repeatable repo-local
@@ -50,17 +50,42 @@ 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.6.0
+## Human Review Path
 
-- **Transactional adoption plans.** `repo-harness adopt --dry-run --json` now
-  emits a protocol v1 operation plan with stable IDs, summaries, content hashes,
-  and rollback metadata.
-- **Manifest-owned bootstrap files.** The initial `docs/spec.md`,
-  `tasks/todos.md`, `tasks/current.md`, and `tasks/lessons.md` templates now
-  come from the workflow contract manifest instead of planner-local strings.
-- **Experimental TypeScript apply.** `repo-harness adopt --experimental-ts-apply`
-  can apply the safe operation subset with atomic writes, target locks, backups,
-  and preflight rejection for unsupported self-host boundaries.
+Start with `tasks/reviews/<task>.review.md`. The `## Human Review Card` is the
+one-screen decision surface: verdict, change type, intended vs actual files,
+commands passed, external acceptance, residual risk, reviewer action, and
+rollback. Then inspect the active contract, latest trace in
+`.ai/harness/checks/latest.json`, and the changed files. Accept only when the
+review recommends pass, the card verdict is pass, and external acceptance is
+pass, `not_required`, or an explicit manual override.
+
+## Agent Tracking Path
+
+Agents read source artifacts before derived summaries:
+
+| Agent reads first | Human reviews first |
+| --- | --- |
+| Current user prompt and referenced files | `tasks/reviews/<task>.review.md` Human Review Card |
+| `AGENTS.md` / `CLAUDE.md` | Changed files and diff |
+| Active plan in `.ai/harness/active-plan` | Active contract allowed paths and exit criteria |
+| Active contract in `tasks/contracts/` | `.ai/harness/checks/latest.json` and run trace |
+| Latest handoff in `.ai/harness/handoff/` | Residual risks and rollback |
+
+`tasks/current.md` is only an orientation snapshot. If it disagrees with the
+active plan, contract, review, checks, or handoff, the source artifacts win.
+
+## What's New in 0.7.1
+
+- **GPT Pro setup path.** `repo-harness:gptpro_setup` guides
+  `gptpro_browser` browser/session setup and `gptpro_mcp` ChatGPT Connector MCP
+  setup while keeping ChatGPT Pro separate from API quota.
+- **GPT Pro consult path.** `repo-harness:gptpro` presents `gptpro
+  consult/read/continue/open` language over the existing ChatGPT Web browser
+  session engine.
+- **Trace-safe PostBash checks.** PostBash advisory metadata now writes to
+  `.ai/harness/checks/post-bash-latest.json`, leaving `latest.json` reserved for
+  authoritative `repo-harness-run-trace.v1` evidence.
 
 ## What repo-harness Does
 
@@ -74,11 +99,71 @@ target repository so Claude, Codex, and humans can agree on:
 - which checks and review evidence prove the work is done
 - how hooks should warn, block, trace, and hand off work across sessions
 
-It is not an agent gateway, product runtime, database service, or MCP server.
 The product boundary is deliberately boring: inspect a repo, install or refresh
 workflow files, route host events through repo-local hooks, and verify that the
 workflow surfaces stay consistent.
 
+As an optional sidecar, `repo-harness mcp` exposes only workflow artifacts to
+MCP clients. ChatGPT can use it as a planner/reviewer to read state and move an
+idea through PRD, checklist Sprint, and Codex goal handoff artifacts; it does
+not get source-code write access, arbitrary shell execution, or a default Codex
+runner. Codex remains the executor. The generated manual setup guide lives at
+`docs/repo-harness-chatgpt-mcp-setup.md`, and the local CLI handoff is
+`repo-harness mcp prepare-goal --prd <prd> --sprint <sprint>`.
+
+### MCP Connector Quickstart
+
+Use the MCP sidecar when you want ChatGPT to plan against the real repo state
+and Codex to execute the resulting file-backed Sprint.
+
+```bash
+repo-harness mcp setup chatgpt --repo .
+repo-harness mcp serve --repo . --transport http --host 127.0.0.1 --port 8765 --profile planner
+```
+
+Expose that local server through an HTTPS tunnel and create a ChatGPT Connector
+with the `/mcp` URL. The generated guide is written to:
+
+```text
+docs/repo-harness-chatgpt-mcp-setup.md
+```
+
+The human workflow is:
+
+1. ChatGPT reads repo-harness workflow files through MCP.
+2. ChatGPT writes a PRD with `write_prd_from_idea`.
+3. ChatGPT writes a checklist Sprint with `write_checklist_sprint`.
+4. ChatGPT prepares `.ai/harness/handoff/codex-goal.md` with `prepare_codex_goal_from_sprint`.
+5. Codex runs the host-native `/goal` prompt and stages each completed Sprint phase.
+
+Local fallback for the last handoff step:
+
+```bash
+repo-harness mcp prepare-goal --repo . --prd plans/prds/<feature>.prd.md --sprint plans/sprints/<feature>.sprint.md
+```
+
+The agent-facing Skill is installed at:
+
+```text
+.agents/skills/repo-harness-chatgpt-bridge/SKILL.md
+```
+
+That Skill tells Codex how to consume ChatGPT-produced PRD/Sprint/Goal artifacts
+without granting ChatGPT source-code writes or shell execution.
+
+Dev Mode can opt into local agent execution through MCP. This is off by default.
+When the user enables the `orchestrator` profile with the dev runner setting,
+ChatGPT can call `run_agent_goal`, which reads only
+`.ai/harness/handoff/codex-goal.md` and runs the fixed handoff through an
+allowed local CLI such as `codex exec` or `claude -p`.
+
+```bash
+repo-harness mcp serve --repo . --transport http --profile orchestrator --enable-dev-runner --dev-runner-agents codex
+```
+
+This setting is for local Developer Mode only. It is timeout-bounded, audited,
+and not arbitrary shell.
+
 ## How It Works
 
 The design has three layers:
@@ -90,10 +175,11 @@ The design has three layers:
    `.ai/harness/`, helper scripts, and `.ai/hooks/`.
 3. **Host adapters**: user-level `~/.claude/settings.json` and
    `~/.codex/hooks.json` route Claude/Codex events into `repo-harness-hook`.
-   The hook entrypoint exits silently for non-opt-in repos. For opted-in repos,
-   it resolves hooks central-first through the packaged install or
-   `~/.repo-harness/hooks/`, with repo policy able to pin self-host development
-   back to `.ai/hooks/*`.
+
+The hook entrypoint exits silently for non-opt-in repos. For opted-in repos,
+it resolves hooks central-first through the packaged install or
+`~/.repo-harness/hooks/`, with repo policy able to pin self-host development
+back to `.ai/hooks/*`.
 
 For `UserPromptSubmit`, the public adapter contract stays
 `repo-harness-hook UserPromptSubmit --route default`. The CLI route registry
@@ -464,8 +550,8 @@ Most common guards:
 
 ## Current Release
 
-- npm package: `repo-harness@0.6.0`
-- Generated workflow stamp: `repo-harness@0.6.0+template@0.6.0`
+- npm package: `repo-harness@0.7.1`
+- Generated workflow stamp: `repo-harness@0.7.1+template@0.7.1`
 - GitHub repository: `Ancienttwo/repo-harness`
 - Release history: [`docs/CHANGELOG.md`](docs/CHANGELOG.md)
 
@@ -552,6 +638,8 @@ skill discovery compatible while the CLI and hooks own execution:
 - Product planning layer: `repo-harness-prd` (activates `$geju`, then uses Claude-first `claude -p --model opus` drafting with Codex fallback to write upper-layer PRDs in `plans/prds/`)
 - Sprint program layer: `repo-harness-sprint` (ordered sprint backlogs in `plans/sprints/`, each row expanded with `$think` before the contract flow)
 - Goal session layer: `repo-harness-goal` / `repo-harness:goal` (prepares Codex/Claude `/goal` prompts from detailed PRD or Sprint artifacts and asks for those docs when missing)
+- GPT Pro local setup layer: `repo-harness-gptpro-setup` / `repo-harness:gptpro_setup` (guides `gptpro_browser` browser/session setup and `gptpro_mcp` ChatGPT Connector MCP setup while keeping ChatGPT Pro separate from API quota)
+- GPT Pro consult layer: `repo-harness-gptpro` / `repo-harness:gptpro` (uses `gptpro consult/read/continue/open` language while mapping to the local ChatGPT Web browser session engine)
 - Repo workflow actions: `repo-harness-ship`, `repo-harness-init`, `repo-harness-migrate`, `repo-harness-upgrade`, `repo-harness-capability`, `repo-harness-architecture`, `repo-harness-handoff`, `repo-harness-deploy`, `repo-harness-repair`, `repo-harness-check`
 - Branch project creation command: `repo-harness-scaffold`
 

package/README.zh-CN.md

@@ -1,7 +1,7 @@
 # repo-harness
 
 <p align="center">
-  <img src="docs/images/image.png" alt="One next button joining Claude and Codex under repo-harness workflow rules" width="760">
+  <img src="docs/images/repo-harness-gptpro-cn.png" alt="repo-harness x GPT Pro 本地 Planner Agent 推广图" width="960">
 </p>
 
 `repo-harness` 把 Claude/Codex 的 AI 编程会话变成可复用、可恢复、可检查的
@@ -43,16 +43,40 @@ 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.6.0 新特性
+## Human Review Path
 
-- **事务型 adoption plan。** `repo-harness adopt --dry-run --json` 现在输出
-  protocol v1 operation plan，包含稳定 ID、summary、content hash 和 rollback metadata。
-- **Manifest-owned bootstrap 文件。** 初始 `docs/spec.md`、`tasks/todos.md`、
-  `tasks/current.md`、`tasks/lessons.md` 模板改由 workflow contract manifest 管理，
-  不再放在 planner 本地字符串里。
-- **实验性 TypeScript apply。** `repo-harness adopt --experimental-ts-apply`
-  可以执行 safe operation subset，并使用 atomic write、target lock、backup 和
-  unsupported self-host boundary preflight。
+先读 `tasks/reviews/<task>.review.md`。`## Human Review Card` 是一屏决策面：
+verdict、change type、预期/实际改动文件、已通过命令、external acceptance、
+残余风险、reviewer action 和 rollback。然后检查 active contract、
+`.ai/harness/checks/latest.json` 里的 latest trace，以及实际 diff。只有当 review
+recommend pass、card verdict 为 pass，且 external acceptance 为 pass、not_required
+或明确 manual override 时，才进入 closeout。
+
+## Agent Tracking Path
+
+Agent 先读 source artifacts，再读派生摘要：
+
+| Agent reads first | Human reviews first |
+| --- | --- |
+| 当前用户 prompt 和引用文件 | `tasks/reviews/<task>.review.md` 的 Human Review Card |
+| `AGENTS.md` / `CLAUDE.md` | changed files 和 diff |
+| `.ai/harness/active-plan` 指向的 active plan | active contract 的 allowed paths 和 exit criteria |
+| `tasks/contracts/` 下的 active contract | `.ai/harness/checks/latest.json` 和 run trace |
+| `.ai/harness/handoff/` 下的 latest handoff | 残余风险和 rollback |
+
+`tasks/current.md` 只是 orientation snapshot。如果它和 active plan、contract、
+review、checks 或 handoff 冲突，以 source artifacts 为准。
+
+## 0.7.1 新特性
+
+- **ChatGPT browser engine。** `repo-harness chatgpt browser-*` 可以用
+  policy-checked 文件输入创建 repo-local ChatGPT Web consult session，不走 OpenAI API。
+- **Opt-in MCP browser tools。** `repo-harness mcp serve
+  --enable-chatgpt-browser` 才会暴露 consult/read/list/continue/open 工具，默认关闭。
+- **Oracle 和 native provider。** Browser engine 支持 Oracle browser wrapper，
+  也支持基于本机已安装 Chrome CDP 的 logged-in ChatGPT Web spike。
+- **Hosted CI 和 release smoke。** 仓库新增 GitHub CI gate，并用 tarball install
+  smoke 验证 packaged `repo-harness` binaries 能启动。
 
 ## 产品做什么
 
@@ -418,8 +442,8 @@ hook block 工作时，先看 terminal 里的结构化输出。核心字段是
 
 ## 当前 Release
 
-- npm package：`repo-harness@0.6.0`
-- Generated workflow stamp：`repo-harness@0.6.0+template@0.6.0`
+- npm package：`repo-harness@0.7.1`
+- Generated workflow stamp：`repo-harness@0.7.1+template@0.7.1`
 - GitHub repository：`Ancienttwo/repo-harness`
 - Release history：[`docs/CHANGELOG.md`](docs/CHANGELOG.md)
 

package/SKILL.md

@@ -145,6 +145,8 @@ contract files:
 - `repo-harness-prd`: generate an upper-layer PRD in `plans/prds/`
 - `repo-harness-sprint`: plan a sprint backlog in `plans/sprints/` from a PRD or source spec, then expand each row with `$think` before the task-contract flow
 - `repo-harness-goal` / `repo-harness:goal`: prepare a Codex/Claude `/goal` prompt from detailed PRD or Sprint artifacts; request those documents before starting when missing
+- `repo-harness-gptpro-setup` / `repo-harness:gptpro_setup`: guide `gptpro_browser` ChatGPT Web browser/session setup and `gptpro_mcp` ChatGPT Connector MCP setup without treating GPT Pro as API quota
+- `repo-harness-gptpro` / `repo-harness:gptpro`: consult or continue GPT Pro through the local ChatGPT Web browser/session bridge while presenting `gptpro consult/read/continue/open` wording over the underlying `browser-*` engine commands
 
 Internal steps such as `hooks-init`, `docs-init`, and `create-project-dirs` are
 not public commands. They stay behind `init`, `scaffold`, `migrate`, and