repo-harness 0.7.3 → 0.7.4

package/README.es.md

@@ -85,7 +85,7 @@ artifacts.
 ## Novedades
 
 Las notas de versión viven en [`docs/CHANGELOG.md`](docs/CHANGELOG.md). La línea
-actual es `0.7.3`.
+actual es `0.7.4`.
 
 ## Cómo funciona
 
@@ -419,8 +419,8 @@ Guards habituales:
 
 ## Release actual
 
-- npm package: `repo-harness@0.7.3`
-- Generated workflow stamp: `repo-harness@0.7.3+template@0.7.3`
+- npm package: `repo-harness@0.7.4`
+- Generated workflow stamp: `repo-harness@0.7.4+template@0.7.4`
 - GitHub repository: `Ancienttwo/repo-harness`
 - Release history: [`docs/CHANGELOG.md`](docs/CHANGELOG.md)
 

package/README.fr.md

@@ -85,7 +85,7 @@ l'emportent.
 ## Nouveautés
 
 Les notes de version vivent dans [`docs/CHANGELOG.md`](docs/CHANGELOG.md). La
-ligne actuelle est `0.7.3`.
+ligne actuelle est `0.7.4`.
 
 ## Comment ça marche
 
@@ -424,8 +424,8 @@ Guards courants :
 
 ## Release actuelle
 
-- npm package : `repo-harness@0.7.3`
-- Generated workflow stamp : `repo-harness@0.7.3+template@0.7.3`
+- npm package : `repo-harness@0.7.4`
+- Generated workflow stamp : `repo-harness@0.7.4+template@0.7.4`
 - GitHub repository : `Ancienttwo/repo-harness`
 - Release history : [`docs/CHANGELOG.md`](docs/CHANGELOG.md)
 

package/README.ja.md

@@ -75,7 +75,7 @@ review、checks、handoff と食い違う場合は、source artifacts を優先
 ## What's New
 
 リリースノートは [`docs/CHANGELOG.md`](docs/CHANGELOG.md) にあります。現在の
-ラインは `0.7.3` です。
+ラインは `0.7.4` です。
 
 ## 仕組み
 
@@ -398,8 +398,8 @@ hook がブロックしたときは、まず terminal の構造化された出
 
 ## 現在の Release
 
-- npm package：`repo-harness@0.7.3`
-- Generated workflow stamp：`repo-harness@0.7.3+template@0.7.3`
+- npm package：`repo-harness@0.7.4`
+- Generated workflow stamp：`repo-harness@0.7.4+template@0.7.4`
 - GitHub repository：`Ancienttwo/repo-harness`
 - Release history：[`docs/CHANGELOG.md`](docs/CHANGELOG.md)
 

package/README.md

@@ -78,7 +78,7 @@ active plan, contract, review, checks, or handoff, the source artifacts win.
 ## What's New
 
 Release notes live in [`docs/CHANGELOG.md`](docs/CHANGELOG.md). The current line
-is `0.7.3`.
+is `0.7.4`.
 
 ## How It Works
 
@@ -493,8 +493,8 @@ Most common guards:
 
 ## Current Release
 
-- npm package: `repo-harness@0.7.3`
-- Generated workflow stamp: `repo-harness@0.7.3+template@0.7.3`
+- npm package: `repo-harness@0.7.4`
+- Generated workflow stamp: `repo-harness@0.7.4+template@0.7.4`
 - GitHub repository: `Ancienttwo/repo-harness`
 - Release history: [`docs/CHANGELOG.md`](docs/CHANGELOG.md)
 

package/README.zh-CN.md

@@ -69,7 +69,7 @@ review、checks 或 handoff 冲突，以 source artifacts 为准。
 
 ## What's New
 
-Release notes 见 [`docs/CHANGELOG.md`](docs/CHANGELOG.md)，当前版本线是 `0.7.3`。
+Release notes 见 [`docs/CHANGELOG.md`](docs/CHANGELOG.md)，当前版本线是 `0.7.4`。
 
 ## 工作原理
 
@@ -437,8 +437,8 @@ hook block 工作时，先看 terminal 里的结构化输出。核心字段是
 
 ## 当前 Release
 
-- npm package：`repo-harness@0.7.3`
-- Generated workflow stamp：`repo-harness@0.7.3+template@0.7.3`
+- npm package：`repo-harness@0.7.4`
+- Generated workflow stamp：`repo-harness@0.7.4+template@0.7.4`
 - GitHub repository：`Ancienttwo/repo-harness`
 - Release history：[`docs/CHANGELOG.md`](docs/CHANGELOG.md)
 

package/assets/skill-commands/repo-harness-gptpro/SKILL.md

@@ -36,22 +36,45 @@ Use GPT Pro language with the user. Treat the `browser-*` command names as imple
    `stamp="$(date -u +%Y%m%dT%H%M%SZ)"; slug="<short-purpose>"; mkdir -p .ai/harness/handoff/gptpro; out=".ai/harness/handoff/gptpro/gptpro-${stamp}-${slug}.md"; repo-harness chatgpt browser-consult --repo <repo> --provider oracle --model gpt-5.5-pro --heartbeat 59 --title "gptpro-${stamp}-${slug}" --prompt <prompt> --write-output "$out"`
 10. Use `--dry-run` first when attaching files, then run the real consult only after the prompt bundle and allowed paths are clear.
 11. For GPT Pro reviews or acceptance checks, resolve the recorded ChatGPT MCP server name from `repo-harness mcp doctor --repo <repo> --json` or `.repo-harness/mcp.local.json` (`chatgpt.serverName`). Treat `chatgpt.serverNameConfigured:false` or a missing `chatgpt.serverName` as setup-incomplete, then route to `repo-harness:gptpro_setup` before an MCP read-back review. Do not substitute a user-specific hard-coded MCP name.
-12. When the user asks for a reasoning mode, pass repo-harness `--thinking <light|standard|extended|heavy>` only after `browser-doctor --provider oracle` reports `browserThinkingTime:true`; repo-harness maps it to Oracle `--browser-thinking-time`.
-13. For long GPT Pro analysis tasks, keep Oracle heartbeat enabled at 59 seconds unless the user explicitly disables it; repo-harness streams heartbeat/diagnostic lines to stderr and reserves stdout for final JSON.
-14. Report the GPT Pro result with: session id, timestamped output path, conversation URL if present, whether it was a new consult or follow-up, and any visible-browser blocker.
+12. When MCP read-back is required, pass the recorded server name as an explicit ChatGPT app preselect: `serverName="$(repo-harness mcp doctor --repo <repo> --json | jq -r '.chatgpt.serverName // empty')"` and add `--chatgpt-app "$serverName"` to `browser-consult` or `browser-followup`. If the command fails with `ORACLE_APP_PRESELECT_UNSUPPORTED`, the selected Oracle binary cannot click the ChatGPT app selector yet; report that as a browser-trigger blocker instead of relying on prompt text like `@serverName`.
+13. When the user asks for a reasoning mode, pass repo-harness `--thinking <light|standard|extended|heavy>` only after `browser-doctor --provider oracle` reports `browserThinkingTime:true`; repo-harness maps it to Oracle `--browser-thinking-time`.
+14. For long GPT Pro analysis tasks, expect detailed Pro Extended planning/review runs to take 15 minutes or more. Do not treat elapsed time as failure while the session is still alive; wait for a final answer or a concrete browser, login, capture, or tool-call failure.
+15. Keep Oracle heartbeat enabled at 59 seconds unless the user explicitly disables it; repo-harness streams heartbeat/diagnostic lines to stderr and reserves stdout for final JSON. Heartbeat lines like `no thinking status detected yet` are progress diagnostics, not a blocker by themselves.
+16. Report the GPT Pro result with: session id, timestamped output path, conversation URL if present, whether it was a new consult or follow-up, and any visible-browser blocker.
 
 ## MCP Read-Back Acceptance
 
 When asking GPT Pro to review repo updates, include an explicit acceptance requirement in the prompt:
 
 - Use the recorded ChatGPT MCP server name from `chatgpt.serverName` to read the current repo state before producing findings or a merge/readiness verdict.
+- Before a Pro MCP attempt, open ChatGPT Settings -> Connectors for the recorded server name, run Refresh or Scan Tools, verify the expected Action is listed, then start a fresh chat and select the Connector from `+` -> More.
 - Read at least the changed-file list or status, the relevant diffs or changed files, and any requested session/handoff artifacts through that recorded MCP server; pasted summaries are context, not sufficient evidence.
 - Include a short `MCP Read Evidence` section in the final answer naming the recorded MCP server, the reads performed, and the files, diffs, or artifacts inspected.
 - If the recorded MCP server name is missing, or `mcp doctor --json` reports `chatgpt.serverNameConfigured:false`, route to `repo-harness:gptpro_setup` so initialization can record it before review.
 - If the recorded MCP server is unavailable, blocked, stale, or cannot read the requested paths, classify the result as blocked or partial instead of issuing a merge-ready verdict.
 - A prompt that asks ChatGPT to use the recorded MCP server is not sufficient by itself; the ChatGPT conversation must expose the app/action schema. If the conversation reports that the app is not exposed, use a fresh app-enabled conversation or a GitHub PR/diff evidence source instead of claiming MCP read-back evidence.
+- For Pro runs, the normal tool-call runtime UI may not appear the way it does for other models because Pro uses a sandbox/process flow. In the visible ChatGPT Web UI, click the assistant's `Thinking` / `Thought for ...` disclosure to open the right-side process pane. Use that pane to confirm whether Pro actually emitted a `Called tool` event for the selected app, which action it chose, or whether it only reasoned inside the sandbox without invoking MCP.
+- Treat `Called tool` with an action/result, or an equivalent captured tool-call transcript, as the only accepted MCP invocation evidence. Reject connector selection, assistant self-report, plausible JSON, and sandbox shell exploration as proof.
+- Classify Pro outcomes explicitly: `invocation_verified` for a real tool call, `approval_pending` for a real confirmation prompt, `surface_blocked` for sandbox-only reasoning or `app_unavailable` with no tool event, and `bundle_fallback` when Pro reviews a local evidence bundle instead of reading through MCP.
 - Do not ask GPT Pro to retrieve secrets, cookies, browser storage, ignored private operations state, or other denied paths through the recorded MCP server.
 
+## Pro Surface Fallback
+
+- When Pro is `surface_blocked`, stop retrying the same connector prompt after one explicit-tool retry. Do not delete/recreate the Connector as the first response to a Pro-only dispatch failure.
+- Reuse the existing local GPT Pro/Oracle handoff path. Build a bounded evidence bundle from local files, diffs, checks, and known external findings, then ask Pro for a plan or review over that bundle.
+- The fallback prompt must include a provenance header:
+
+```yaml
+source: local_repo_harness_bundle
+pro_invoked_mcp: false
+working_tree: clean | dirty
+included_paths: [...]
+omitted_or_truncated: [...]
+```
+
+- Tell Pro that anything outside the bundle is unknown. Codex executes and verifies locally, then creates a fresh post-change bundle for another Pro review if needed.
+- Distinguish permissions: repo-scope setup is repo-bound; broad repo discovery requires explicit user-scope setup with full-disk read. Do not recommend full-disk read by default.
+
 ## Research Promotion
 
 - Treat `.ai/harness/handoff/gptpro/*.md` as raw local GPT Pro evidence. These files are timestamped and ignored so repeated reviews do not collide or pollute tracked workflow handoff files.

package/assets/skill-version.json

@@ -1,6 +1,6 @@
 {
-  "version": "0.7.3",
-  "templateVersion": "0.7.3",
+  "version": "0.7.4",
+  "templateVersion": "0.7.4",
   "skillName": "repo-harness",
   "contractId": "tasks-first-harness-v1",
   "compatibility": {
@@ -155,6 +155,10 @@
     {
       "version": "0.7.3",
       "description": "Compacts package-dispatched helper migration, preserves ChatGPT MCP bind settings, and hardens Codex delegation lifecycle retries"
+    },
+    {
+      "version": "0.7.4",
+      "description": "Adds user-scope ChatGPT MCP full-disk repo discovery, GPT Pro Connector read-back safeguards, and package-dispatched architecture helper fixes while retiring compact adopt root wrappers"
     }
   ],
   "generatedProjectStamp": {

package/assets/templates/helpers/architecture-queue.sh

@@ -71,26 +71,59 @@ index_file="docs/architecture/index.md"
 requests_dir="docs/architecture/requests"
 event_file=".ai/harness/architecture/events.jsonl"
 
+helper_sibling() {
+  local helper_name="$1"
+  local helper_dir=""
+  if [[ -n "${REPO_HARNESS_HELPER_SOURCE_PATH:-}" ]]; then
+    helper_dir="$(dirname "$REPO_HARNESS_HELPER_SOURCE_PATH")"
+  fi
+  if [[ -n "$helper_dir" && -f "$helper_dir/$helper_name" ]]; then
+    printf '%s\n' "$helper_dir/$helper_name"
+    return 0
+  fi
+  return 1
+}
+
 architecture_event() {
+  local sibling=""
   if command -v bun >/dev/null 2>&1 && [[ -f "scripts/architecture-event.ts" ]]; then
     bun scripts/architecture-event.ts "$@"
     return $?
   fi
+  sibling="$(helper_sibling architecture-event.ts || true)"
+  if command -v bun >/dev/null 2>&1 && [[ -n "$sibling" ]]; then
+    bun "$sibling" "$@"
+    return $?
+  fi
   return 127
 }
 
 architecture_event_required() {
-  if ! command -v bun >/dev/null 2>&1; then
-    echo "architecture-queue: bun is required for $command_name" >&2
-    return 127
-  fi
-  if [[ ! -f "scripts/architecture-event.ts" ]]; then
-    echo "architecture-queue: missing scripts/architecture-event.ts" >&2
+  if ! architecture_event safe-token --value probe >/dev/null 2>&1; then
+    echo "architecture-queue: missing architecture-event helper" >&2
     return 127
   fi
   return 0
 }
 
+capability_resolver() {
+  local sibling=""
+  if command -v bun >/dev/null 2>&1 && [[ -f "scripts/capability-resolver.ts" ]]; then
+    bun scripts/capability-resolver.ts "$@"
+    return $?
+  fi
+  sibling="$(helper_sibling capability-resolver.ts || true)"
+  if command -v bun >/dev/null 2>&1 && [[ -n "$sibling" ]]; then
+    bun "$sibling" "$@"
+    return $?
+  fi
+  return 127
+}
+
+capability_resolver_available() {
+  capability_resolver list --format json >/dev/null 2>&1
+}
+
 json_escape() {
   local value="$1"
   value="${value//\\/\\\\}"
@@ -404,7 +437,7 @@ status_command() {
       return 0
       ;;
     strict)
-      if ! command -v bun >/dev/null 2>&1 || [[ ! -f "scripts/architecture-event.ts" || ! -f "scripts/capability-resolver.ts" ]]; then
+      if ! architecture_event_required >/dev/null 2>&1 || ! capability_resolver_available; then
         echo "[ArchitectureQueue] strict gate failed: missing queue dependencies" >&2
         return 1
       fi
@@ -440,15 +473,15 @@ record_command() {
     exit 0
   fi
 
-  if ! command -v bun >/dev/null 2>&1 || [[ ! -f "scripts/architecture-event.ts" ]]; then
-    echo "[ArchitectureQueue] WARN: bun and scripts/architecture-event.ts are required to record $rel_path; skipping advisory queue update"
+  if ! architecture_event_required >/dev/null 2>&1; then
+    echo "[ArchitectureQueue] WARN: architecture-event helper is required to record $rel_path; skipping advisory queue update"
     exit 0
   fi
 
   capability_match=""
-  if [[ -f "scripts/capability-resolver.ts" ]]; then
+  if capability_resolver_available; then
     resolver_stderr="$(mktemp)"
-    if ! capability_match="$(bun scripts/capability-resolver.ts match --path "$rel_path" --format json 2>"$resolver_stderr")"; then
+    if ! capability_match="$(capability_resolver match --path "$rel_path" --format json 2>"$resolver_stderr")"; then
       [[ -n "$capability_match" ]] && echo "$capability_match" >&2
       cat "$resolver_stderr" >&2
       rm -f "$resolver_stderr"
@@ -475,7 +508,7 @@ record_command() {
     matched_prefix="$(json_get "$capability_match" "matched_prefix")"
     capability_id="$(json_get "$capability_match" "capability_id")"
     capability_resolved="true"
-  elif [[ ! -f "scripts/capability-resolver.ts" ]]; then
+  elif ! capability_resolver_available; then
     functional_block="$(match_functional_block "$rel_path")"
     matched_prefix="$functional_block"
     capability_id="$(safe_token "$functional_block")"

package/assets/templates/helpers/check-architecture-sync.sh

@@ -90,6 +90,19 @@ try {
   printf '%s' "${value:-$default_value}"
 }
 
+helper_sibling() {
+  local helper_name="$1"
+  local helper_dir=""
+  if [[ -n "${REPO_HARNESS_HELPER_SOURCE_PATH:-}" ]]; then
+    helper_dir="$(dirname "$REPO_HARNESS_HELPER_SOURCE_PATH")"
+  fi
+  if [[ -n "$helper_dir" && -f "$helper_dir/$helper_name" ]]; then
+    printf '%s\n' "$helper_dir/$helper_name"
+    return 0
+  fi
+  return 1
+}
+
 severity_rank() {
   case "$(printf '%s' "${1:-}" | tr '[:upper:]' '[:lower:]')" in
     critical) printf '4' ;;
@@ -198,17 +211,51 @@ case "$mode" in
     ;;
 esac
 
-if [[ ! -x "scripts/architecture-queue.sh" ]]; then
+run_architecture_queue() {
+  local sibling=""
+  if [[ -x "scripts/architecture-queue.sh" ]]; then
+    bash scripts/architecture-queue.sh "$@"
+    return $?
+  fi
+  sibling="$(helper_sibling architecture-queue.sh || true)"
+  if [[ -n "$sibling" ]]; then
+    bash "$sibling" "$@"
+    return $?
+  fi
+  return 127
+}
+
+architecture_queue_available() {
+  [[ -x "scripts/architecture-queue.sh" ]] && return 0
+  helper_sibling architecture-queue.sh >/dev/null 2>&1 && return 0
+  return 1
+}
+
+run_capability_resolver() {
+  local sibling=""
+  if command -v bun >/dev/null 2>&1 && [[ -f "scripts/capability-resolver.ts" ]]; then
+    bun scripts/capability-resolver.ts "$@"
+    return $?
+  fi
+  sibling="$(helper_sibling capability-resolver.ts || true)"
+  if command -v bun >/dev/null 2>&1 && [[ -n "$sibling" ]]; then
+    bun "$sibling" "$@"
+    return $?
+  fi
+  return 127
+}
+
+if ! architecture_queue_available; then
   if [[ "$mode" == "strict" ]]; then
-    echo "[ArchitectureSync] strict gate failed: missing scripts/architecture-queue.sh" >&2
+    echo "[ArchitectureSync] strict gate failed: missing architecture-queue helper" >&2
     exit 1
   fi
-  echo "[ArchitectureSync] WARN: missing scripts/architecture-queue.sh; skipping advisory freshness gate" >&2
+  echo "[ArchitectureSync] WARN: missing architecture-queue helper; skipping advisory freshness gate" >&2
   exit 0
 fi
 
-if ! bash scripts/architecture-queue.sh reindex --check >/dev/null; then
-  echo "[ArchitectureSync] architecture request index is stale; run bash scripts/architecture-queue.sh reindex" >&2
+if ! run_architecture_queue reindex --check >/dev/null; then
+  echo "[ArchitectureSync] architecture request index is stale; run repo-harness run architecture-queue reindex" >&2
   exit 1
 fi
 
@@ -221,12 +268,12 @@ if [[ "$mode" == "off" ]]; then
   exit 0
 fi
 
-if ! command -v bun >/dev/null 2>&1 || [[ ! -f "scripts/capability-resolver.ts" ]]; then
+if ! run_capability_resolver list --format json >/dev/null 2>&1; then
   if [[ "$mode" == "strict" ]]; then
-    echo "[ArchitectureSync] strict gate failed: missing bun or scripts/capability-resolver.ts" >&2
+    echo "[ArchitectureSync] strict gate failed: missing capability-resolver helper" >&2
     exit 1
   fi
-  echo "[ArchitectureSync] WARN: missing bun or scripts/capability-resolver.ts; skipping advisory freshness gate" >&2
+  echo "[ArchitectureSync] WARN: missing capability-resolver helper; skipping advisory freshness gate" >&2
   exit 0
 fi
 
@@ -240,7 +287,7 @@ if [[ -z "$changed_files" ]]; then
   exit 0
 fi
 
-matches_json="$(printf '%s\n' "$changed_files" | bun scripts/capability-resolver.ts match --paths-from - --format json)"
+matches_json="$(printf '%s\n' "$changed_files" | run_capability_resolver match --paths-from - --format json)"
 capabilities="$(
   MATCHES_JSON="$matches_json" node -e '
 const matches = JSON.parse(process.env.MATCHES_JSON || "[]");

package/assets/templates/helpers/check-context-files.sh

@@ -15,7 +15,7 @@ fi
 issues=0
 files="$(
   find . \
-    \( -path './.git' -o -path './node_modules' -o -path './_ref' -o -path './_ops' -o -path './.worktrees' \) -prune -o \
+    \( -path './.git' -o -path './node_modules' -o -path './_ref' -o -path './_ops' -o -path './.worktrees' -o -path './.video-agent-refactor-backup' -o -path './.ai/harness/archive' -o -path './.ai/harness/backups' -o -path './.repo-harness' \) -prune -o \
     -type f \( -name 'AGENTS.md' -o -name 'CLAUDE.md' \) -print \
     | sort
 )"
@@ -29,8 +29,9 @@ scan_pattern() {
   local label="$1"
   local regex="$2"
   local match
+  local benign_negative='(never|do not|don'\''t|must not|should not)[^:;.!?]*(print|show|copy|upload|send|read|cat)'
 
-  match="$(printf '%s\n' "$files" | xargs grep -Eni "$regex" 2>/dev/null | head -1 || true)"
+  match="$(printf '%s\n' "$files" | xargs grep -Eni "$regex" 2>/dev/null | grep -Eiv "$benign_negative" | head -1 || true)"
   if [[ -n "$match" ]]; then
     echo "[ContextScan] ${label}: ${match}"
     issues=$((issues + 1))

package/docs/repo-harness-chatgpt-browser-engine.md

@@ -101,6 +101,15 @@ The wrapper maps repo-harness input to `oracle --engine browser --browser-archiv
 
 The oracle binary is resolved in a fixed, auditable order — `--oracle-bin`, then `REPO_HARNESS_ORACLE_BIN`, then repo-local `node_modules/.bin/oracle`, then `oracle` on `PATH`. A missing binary fails with `ORACLE_NOT_INSTALLED`; explicitly configured binaries (`--oracle-bin` or `REPO_HARNESS_ORACLE_BIN`) fail closed when invalid and do not silently fall through to the next source. repo-harness never implicitly downloads or `npx`-executes an unpinned oracle. `browser-doctor --provider oracle --json` runs `--help`, `--debug-help`, `--version`, plus an isolated `--browser-thinking-time` dry-run parser probe, and reports `installed`, resolved `binary`, `version`, `nodeCompatible`, a `capabilities` map (`browserEngine`, `writeOutput`, `browserFollowup`, `sessionFollowup`, `browserArchive`, `browserModelStrategy`, `browserCookiePath`, `browserThinkingTime`, `chatgptUrl`, `heartbeat`), and opt-in `agent_actions` when a GPT Pro setup repair can install, upgrade, or re-point the selected pinned external CLI; `status:"ready"` requires every capability for every flag repo-harness may send at runtime.
 
+When a ChatGPT MCP Connector app must be active for read-back, use `--chatgpt-app <serverName>` with the server name recorded by `repo-harness mcp doctor --repo <repo> --json` under `chatgpt.serverName`. repo-harness maps that to Oracle `--browser-app <serverName>` so Oracle selects the composer app before submitting the prompt. This is an opt-in capability: it is reported under `oracle.optionalCapabilities.browserAppPreselect` and is required only when `--chatgpt-app` is present. If the selected Oracle binary lacks `--browser-app`, the run fails before prompt submission with `ORACLE_APP_PRESELECT_UNSUPPORTED`; do not rely on plain prompt text such as `@serverName` as evidence that ChatGPT exposed MCP tools.
+
+App selection and tool availability are separate gates. `--chatgpt-app` only
+selects the Connector in the composer; ChatGPT can still see a stale scanned
+tool schema. If a run proves the app is selected but ChatGPT reports a specific
+tool unavailable, compare the live MCP `/mcp` `tools/list` against the
+Connector's visible tools and use ChatGPT Connector **Scan Tools** to refresh the
+schema.
+
 Long Oracle browser runs default to `--heartbeat 59`. repo-harness streams Oracle diagnostics and heartbeat lines to stderr while preserving stdout for the final JSON payload, so humans and agents get a periodic liveness signal without breaking automation that parses command output.
 
 Oracle browser mode supports model selection through `--model` and thinking intensity through `--browser-thinking-time <light|standard|extended|heavy>`. repo-harness maps its `--thinking` value directly to that Oracle browser flag after doctor has verified parser support. Oracle also supports `--browser-manual-login`, but repo-harness intentionally does not send it on the bound-profile path because it skips cookie copy and would make the selected Chrome profile cookie DB non-authoritative.

package/package.json

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

package/scripts/architecture-queue.sh

@@ -71,26 +71,59 @@ index_file="docs/architecture/index.md"
 requests_dir="docs/architecture/requests"
 event_file=".ai/harness/architecture/events.jsonl"
 
+helper_sibling() {
+  local helper_name="$1"
+  local helper_dir=""
+  if [[ -n "${REPO_HARNESS_HELPER_SOURCE_PATH:-}" ]]; then
+    helper_dir="$(dirname "$REPO_HARNESS_HELPER_SOURCE_PATH")"
+  fi
+  if [[ -n "$helper_dir" && -f "$helper_dir/$helper_name" ]]; then
+    printf '%s\n' "$helper_dir/$helper_name"
+    return 0
+  fi
+  return 1
+}
+
 architecture_event() {
+  local sibling=""
   if command -v bun >/dev/null 2>&1 && [[ -f "scripts/architecture-event.ts" ]]; then
     bun scripts/architecture-event.ts "$@"
     return $?
   fi
+  sibling="$(helper_sibling architecture-event.ts || true)"
+  if command -v bun >/dev/null 2>&1 && [[ -n "$sibling" ]]; then
+    bun "$sibling" "$@"
+    return $?
+  fi
   return 127
 }
 
 architecture_event_required() {
-  if ! command -v bun >/dev/null 2>&1; then
-    echo "architecture-queue: bun is required for $command_name" >&2
-    return 127
-  fi
-  if [[ ! -f "scripts/architecture-event.ts" ]]; then
-    echo "architecture-queue: missing scripts/architecture-event.ts" >&2
+  if ! architecture_event safe-token --value probe >/dev/null 2>&1; then
+    echo "architecture-queue: missing architecture-event helper" >&2
     return 127
   fi
   return 0
 }
 
+capability_resolver() {
+  local sibling=""
+  if command -v bun >/dev/null 2>&1 && [[ -f "scripts/capability-resolver.ts" ]]; then
+    bun scripts/capability-resolver.ts "$@"
+    return $?
+  fi
+  sibling="$(helper_sibling capability-resolver.ts || true)"
+  if command -v bun >/dev/null 2>&1 && [[ -n "$sibling" ]]; then
+    bun "$sibling" "$@"
+    return $?
+  fi
+  return 127
+}
+
+capability_resolver_available() {
+  capability_resolver list --format json >/dev/null 2>&1
+}
+
 json_escape() {
   local value="$1"
   value="${value//\\/\\\\}"
@@ -404,7 +437,7 @@ status_command() {
       return 0
       ;;
     strict)
-      if ! command -v bun >/dev/null 2>&1 || [[ ! -f "scripts/architecture-event.ts" || ! -f "scripts/capability-resolver.ts" ]]; then
+      if ! architecture_event_required >/dev/null 2>&1 || ! capability_resolver_available; then
         echo "[ArchitectureQueue] strict gate failed: missing queue dependencies" >&2
         return 1
       fi
@@ -440,15 +473,15 @@ record_command() {
     exit 0
   fi
 
-  if ! command -v bun >/dev/null 2>&1 || [[ ! -f "scripts/architecture-event.ts" ]]; then
-    echo "[ArchitectureQueue] WARN: bun and scripts/architecture-event.ts are required to record $rel_path; skipping advisory queue update"
+  if ! architecture_event_required >/dev/null 2>&1; then
+    echo "[ArchitectureQueue] WARN: architecture-event helper is required to record $rel_path; skipping advisory queue update"
     exit 0
   fi
 
   capability_match=""
-  if [[ -f "scripts/capability-resolver.ts" ]]; then
+  if capability_resolver_available; then
     resolver_stderr="$(mktemp)"
-    if ! capability_match="$(bun scripts/capability-resolver.ts match --path "$rel_path" --format json 2>"$resolver_stderr")"; then
+    if ! capability_match="$(capability_resolver match --path "$rel_path" --format json 2>"$resolver_stderr")"; then
       [[ -n "$capability_match" ]] && echo "$capability_match" >&2
       cat "$resolver_stderr" >&2
       rm -f "$resolver_stderr"
@@ -475,7 +508,7 @@ record_command() {
     matched_prefix="$(json_get "$capability_match" "matched_prefix")"
     capability_id="$(json_get "$capability_match" "capability_id")"
     capability_resolved="true"
-  elif [[ ! -f "scripts/capability-resolver.ts" ]]; then
+  elif ! capability_resolver_available; then
     functional_block="$(match_functional_block "$rel_path")"
     matched_prefix="$functional_block"
     capability_id="$(safe_token "$functional_block")"

package/scripts/check-architecture-sync.sh

@@ -90,6 +90,19 @@ try {
   printf '%s' "${value:-$default_value}"
 }
 
+helper_sibling() {
+  local helper_name="$1"
+  local helper_dir=""
+  if [[ -n "${REPO_HARNESS_HELPER_SOURCE_PATH:-}" ]]; then
+    helper_dir="$(dirname "$REPO_HARNESS_HELPER_SOURCE_PATH")"
+  fi
+  if [[ -n "$helper_dir" && -f "$helper_dir/$helper_name" ]]; then
+    printf '%s\n' "$helper_dir/$helper_name"
+    return 0
+  fi
+  return 1
+}
+
 severity_rank() {
   case "$(printf '%s' "${1:-}" | tr '[:upper:]' '[:lower:]')" in
     critical) printf '4' ;;
@@ -198,17 +211,51 @@ case "$mode" in
     ;;
 esac
 
-if [[ ! -x "scripts/architecture-queue.sh" ]]; then
+run_architecture_queue() {
+  local sibling=""
+  if [[ -x "scripts/architecture-queue.sh" ]]; then
+    bash scripts/architecture-queue.sh "$@"
+    return $?
+  fi
+  sibling="$(helper_sibling architecture-queue.sh || true)"
+  if [[ -n "$sibling" ]]; then
+    bash "$sibling" "$@"
+    return $?
+  fi
+  return 127
+}
+
+architecture_queue_available() {
+  [[ -x "scripts/architecture-queue.sh" ]] && return 0
+  helper_sibling architecture-queue.sh >/dev/null 2>&1 && return 0
+  return 1
+}
+
+run_capability_resolver() {
+  local sibling=""
+  if command -v bun >/dev/null 2>&1 && [[ -f "scripts/capability-resolver.ts" ]]; then
+    bun scripts/capability-resolver.ts "$@"
+    return $?
+  fi
+  sibling="$(helper_sibling capability-resolver.ts || true)"
+  if command -v bun >/dev/null 2>&1 && [[ -n "$sibling" ]]; then
+    bun "$sibling" "$@"
+    return $?
+  fi
+  return 127
+}
+
+if ! architecture_queue_available; then
   if [[ "$mode" == "strict" ]]; then
-    echo "[ArchitectureSync] strict gate failed: missing scripts/architecture-queue.sh" >&2
+    echo "[ArchitectureSync] strict gate failed: missing architecture-queue helper" >&2
     exit 1
   fi
-  echo "[ArchitectureSync] WARN: missing scripts/architecture-queue.sh; skipping advisory freshness gate" >&2
+  echo "[ArchitectureSync] WARN: missing architecture-queue helper; skipping advisory freshness gate" >&2
   exit 0
 fi
 
-if ! bash scripts/architecture-queue.sh reindex --check >/dev/null; then
-  echo "[ArchitectureSync] architecture request index is stale; run bash scripts/architecture-queue.sh reindex" >&2
+if ! run_architecture_queue reindex --check >/dev/null; then
+  echo "[ArchitectureSync] architecture request index is stale; run repo-harness run architecture-queue reindex" >&2
   exit 1
 fi
 
@@ -221,12 +268,12 @@ if [[ "$mode" == "off" ]]; then
   exit 0
 fi
 
-if ! command -v bun >/dev/null 2>&1 || [[ ! -f "scripts/capability-resolver.ts" ]]; then
+if ! run_capability_resolver list --format json >/dev/null 2>&1; then
   if [[ "$mode" == "strict" ]]; then
-    echo "[ArchitectureSync] strict gate failed: missing bun or scripts/capability-resolver.ts" >&2
+    echo "[ArchitectureSync] strict gate failed: missing capability-resolver helper" >&2
     exit 1
   fi
-  echo "[ArchitectureSync] WARN: missing bun or scripts/capability-resolver.ts; skipping advisory freshness gate" >&2
+  echo "[ArchitectureSync] WARN: missing capability-resolver helper; skipping advisory freshness gate" >&2
   exit 0
 fi
 
@@ -240,7 +287,7 @@ if [[ -z "$changed_files" ]]; then
   exit 0
 fi
 
-matches_json="$(printf '%s\n' "$changed_files" | bun scripts/capability-resolver.ts match --paths-from - --format json)"
+matches_json="$(printf '%s\n' "$changed_files" | run_capability_resolver match --paths-from - --format json)"
 capabilities="$(
   MATCHES_JSON="$matches_json" node -e '
 const matches = JSON.parse(process.env.MATCHES_JSON || "[]");