harness-for-rea 0.1.0 → 0.1.2

package/dist/main.js

@@ -76524,8 +76524,78 @@ function applyPatch(dataDir, id, sourceRoot) {
   return changes.map((c) => c.path);
 }
 
-// raw:C:/Users/prode/harness-for-rea/sandbox/specialist-base/AGENTS.md
-var AGENTS_default = "# Operating guide \u2014 the specialist as a harness of REA\r\n\r\nYou analyse with REA, the reverse engineering MCP server attached to this session. Its tools are\r\nnamed `mcp__rea__<tool>`. This guide says how you use them. REA's own skill says what each tool is\r\nfor. Read `/opt/hfr/rea-skill/SKILL.md` before your first REA call, and its `references/` when a\r\ntarget needs them.\r\n\r\n## The environment\r\n\r\n- REA is already connected and its catalog is fixed. Never run `rea setup`, `rea update` or\r\n  `npx rea-agents`, and never ask for a restart. The skill's \"connect only when needed\" steps do\r\n  not apply here.\r\n- These engines are installed and REA finds them:\r\n  - Ghidra 12.1.4 (`$GHIDRA_INSTALL_DIR`) with JDK 21 (`$JAVA_HOME`);\r\n  - jadx-headless-mcp (`$REA_JADX_MCP_JAR`);\r\n  - Apktool (`$REA_APKTOOL_COMMAND`).\r\n- Hopper, JEB, IDA, Frida, ADB and the macOS tools are not available. Do not try them.\r\n- You are root with a shell and the internet. Install another tool only when REA cannot answer\r\n  the question, and say so in the report.\r\n- `/work` holds the files you were given. Keep everything you extract, build or export in\r\n  `/root/out`, which the task keeps, or in `/tmp`, never in `/work`.\r\n\r\n## How an analysis runs\r\n\r\n1. Call `binary_session {}` once to see what this server can do.\r\n2. Turn the objective into a checklist of the questions you must answer.\r\n3. Route the target before analysing it. The input decides the first tool:\r\n   - an ASAR or Electron app goes to `analyze_javascript_application`;\r\n   - an APK goes to `inspect_android_package`;\r\n   - a .NET assembly goes to `inspect_managed_artifact`;\r\n   - firmware goes to `inspect_firmware_regions`;\r\n   - an archive goes to `open_binary` and `inspect_artifact`;\r\n   - a native binary goes to `open_binary`.\r\n4. Work summary first. Request `detail: \"summary\"`, then page what was retained with\r\n   `inspect_analysis_view` and its `parent_evidence_id`. Never repeat an identical call: reuse the\r\n   session's state.\r\n5. Corroborate every claim with the kind of evidence it needs. Static analysis never shows what\r\n   happened at run time; only a run or a capture does.\r\n6. Keep a finding ledger as you go: each conclusion, its evidence IDs, its authority and\r\n   confidence, how far you searched, and what remains unknown.\r\n7. Before finishing:\r\n   - Export the evidence bundle with `export_evidence_bundle` to `/root/out/evidence/`. REA's\r\n     ledger lives in its process and is gone when this run ends.\r\n   - Close the target with `close_binary`.\r\n   - Mark each checklist question answered, partial or unresolved.\r\n\r\n## Unknowns\r\n\r\n- Record every question you cannot settle with `record_unknown`: what would settle it, and the\r\n  evidence for and against. Do not guess.\r\n- Revise an unknown with `update_unknown` against its current revision. On a revision conflict,\r\n  read it again rather than retrying.\r\n- Call an unknown resolved only after `verify_unknown_resolution` confirms the evidence behind it.\r\n\r\n## Evidence rules\r\n\r\n- Missing evidence is never proof that something is absent or does not happen.\r\n- Mark a value as estimated only after you looked for it, and say where you looked.\r\n- Label every claim as an observation, an inference or an unknown.\r\n- Cite REA's identifiers verbatim: `ev_` and 64 hex digits for evidence, `unk_` and 64 hex digits\r\n  for unknowns.\r\n\r\nIn the report's Evidence section, write one line per claim, in one of these forms:\r\n\r\n```\r\n- <path>:<start line>-<end line> \u2014 <claim>    a range of a text file in /work\r\n- <path>@0x<address> \u2014 <claim>                an address in a binary in /work\r\n- ev_<64 hex> \u2014 <claim>                        an REA evidence record\r\n- unk_<64 hex> \u2014 <what is still unknown>      an REA unknown\r\n```\r\n";
+// raw:/home/runner/work/harness-for-rea/harness-for-rea/sandbox/specialist-base/AGENTS.md
+var AGENTS_default = `# Operating guide \u2014 the specialist as a harness of REA
+
+You analyse with REA, the reverse engineering MCP server attached to this session. Its tools are
+named \`mcp__rea__<tool>\`. This guide says how you use them. REA's own skill says what each tool is
+for. Read \`/opt/hfr/rea-skill/SKILL.md\` before your first REA call, and its \`references/\` when a
+target needs them.
+
+## The environment
+
+- REA is already connected and its catalog is fixed. Never run \`rea setup\`, \`rea update\` or
+  \`npx rea-agents\`, and never ask for a restart. The skill's "connect only when needed" steps do
+  not apply here.
+- These engines are installed and REA finds them:
+  - Ghidra 12.1.4 (\`$GHIDRA_INSTALL_DIR\`) with JDK 21 (\`$JAVA_HOME\`);
+  - jadx-headless-mcp (\`$REA_JADX_MCP_JAR\`);
+  - Apktool (\`$REA_APKTOOL_COMMAND\`).
+- Hopper, JEB, IDA, Frida, ADB and the macOS tools are not available. Do not try them.
+- You are root with a shell and the internet. Install another tool only when REA cannot answer
+  the question, and say so in the report.
+- \`/work\` holds the files you were given. Keep everything you extract, build or export in
+  \`/root/out\`, which the task keeps, or in \`/tmp\`, never in \`/work\`.
+
+## How an analysis runs
+
+1. Call \`binary_session {}\` once to see what this server can do.
+2. Turn the objective into a checklist of the questions you must answer.
+3. Route the target before analysing it. The input decides the first tool:
+   - an ASAR or Electron app goes to \`analyze_javascript_application\`;
+   - an APK goes to \`inspect_android_package\`;
+   - a .NET assembly goes to \`inspect_managed_artifact\`;
+   - firmware goes to \`inspect_firmware_regions\`;
+   - an archive goes to \`open_binary\` and \`inspect_artifact\`;
+   - a native binary goes to \`open_binary\`.
+4. Work summary first. Request \`detail: "summary"\`, then page what was retained with
+   \`inspect_analysis_view\` and its \`parent_evidence_id\`. Never repeat an identical call: reuse the
+   session's state.
+5. Corroborate every claim with the kind of evidence it needs. Static analysis never shows what
+   happened at run time; only a run or a capture does.
+6. Keep a finding ledger as you go: each conclusion, its evidence IDs, its authority and
+   confidence, how far you searched, and what remains unknown.
+7. Before finishing:
+   - Export the evidence bundle with \`export_evidence_bundle\` to \`/root/out/evidence/\`. REA's
+     ledger lives in its process and is gone when this run ends.
+   - Close the target with \`close_binary\`.
+   - Mark each checklist question answered, partial or unresolved.
+
+## Unknowns
+
+- Record every question you cannot settle with \`record_unknown\`: what would settle it, and the
+  evidence for and against. Do not guess.
+- Revise an unknown with \`update_unknown\` against its current revision. On a revision conflict,
+  read it again rather than retrying.
+- Call an unknown resolved only after \`verify_unknown_resolution\` confirms the evidence behind it.
+
+## Evidence rules
+
+- Missing evidence is never proof that something is absent or does not happen.
+- Mark a value as estimated only after you looked for it, and say where you looked.
+- Label every claim as an observation, an inference or an unknown.
+- Cite REA's identifiers verbatim: \`ev_\` and 64 hex digits for evidence, \`unk_\` and 64 hex digits
+  for unknowns.
+
+In the report's Evidence section, write one line per claim, in one of these forms:
+
+\`\`\`
+- <path>:<start line>-<end line> \u2014 <claim>    a range of a text file in /work
+- <path>@0x<address> \u2014 <claim>                an address in a binary in /work
+- ev_<64 hex> \u2014 <claim>                        an REA evidence record
+- unk_<64 hex> \u2014 <what is still unknown>      an REA unknown
+\`\`\`
+`;
 
 // src/main/sandbox/prompt.ts
 var WORK = "/work";
@@ -95712,8 +95782,8 @@ function lockDataFolder(dataDir, app, pid = process.pid, isAlive = alive) {
 }
 var ATTEMPTS = 20;
 var PAUSE_MS = 50;
-var UNREADABLE_STALE_MS = 2000;
-var GUARD_STALE_MS = 5000;
+var UNREADABLE_STALE_MS = 5000;
+var GUARD_STALE_MS = 1e4;
 function pause() {
   Atomics.wait(new Int32Array(new SharedArrayBuffer(4)), 0, 0, PAUSE_MS);
 }
@@ -129366,8 +129436,11 @@ class SandboxService {
     this.onChange = onChange;
   }
   set(patch) {
-    this.current = { ...this.current, ...patch };
-    this.onChange(this.current);
+    const next = { ...this.current, ...patch };
+    const changed = JSON.stringify(next) !== JSON.stringify(this.current);
+    this.current = next;
+    if (changed)
+      this.onChange(this.current);
     return this.current;
   }
   async status() {
@@ -129419,9 +129492,14 @@ class LoginService {
       error: this.error
     };
   }
+  pushed = "";
   changed() {
     const s = this.current();
-    this.onChange(s);
+    const key = JSON.stringify(s);
+    if (key !== this.pushed) {
+      this.pushed = key;
+      this.onChange(s);
+    }
     return s;
   }
   async refresh() {
@@ -130293,7 +130371,7 @@ var package_default = {
   name: "harness-for-rea",
   productName: "Harness for REA",
   private: true,
-  version: "0.1.0",
+  version: "0.1.2",
   description: "Desktop app where an OpenRouter orchestrator delegates deep analysis to a sandboxed Claude Code specialist.",
   license: "MIT",
   main: "./out/main/index.js",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "harness-for-rea",
-  "version": "0.1.0",
+  "version": "0.1.2",
   "description": "Terminal UI of Harness for REA: an orchestrator that delegates deep analysis to a sandboxed Claude Code specialist.",
   "license": "MIT",
   "type": "module",

package/sandbox/specialist/Dockerfile

@@ -1,42 +1,42 @@
-# The specialist image: the pinned base pulled from GHCR (adr:0012-pull-the-specialists-base-image-from-ghcr)
-# plus the pinned Claude Code CLI for Linux, verified at build time against the release manifest,
-# whose gpg signature is checked against Anthropic's release key
-# (adr:0006-run-the-specialist-inside-a-container-per-task, specs/task-sandbox R2.6). Built locally,
-# so the binary is never redistributed.
-
-ARG BASE
-
-FROM debian:bookworm-slim AS verify
-ARG CLAUDE_CODE_VERSION
-ARG REPOSITORY=https://downloads.claude.ai/claude-code-releases
-ARG RELEASE_SIGNER_URL=https://downloads.claude.ai/keys/claude-code.asc
-# The fingerprint published on Claude Code's setup page.
-ARG FINGERPRINT=31DDDE24DDFAB679F42D7BD2BAA929FF1A7ECACE
-ARG PLATFORM=linux-x64
-
-RUN apt-get update \
- && apt-get install -y --no-install-recommends ca-certificates curl gnupg jq \
- && rm -rf /var/lib/apt/lists/*
-
-WORKDIR /verify
-RUN test -n "$CLAUDE_CODE_VERSION" \
- && export GNUPGHOME="$(mktemp -d)" \
- && curl -fsSL "$RELEASE_SIGNER_URL" -o key.asc \
- && gpg --batch --import key.asc \
- && curl -fsSL "$REPOSITORY/$CLAUDE_CODE_VERSION/manifest.json" -o manifest.json \
- && curl -fsSL "$REPOSITORY/$CLAUDE_CODE_VERSION/manifest.json.sig" -o manifest.json.sig \
- && gpg --batch --status-fd 1 --verify manifest.json.sig manifest.json > status.txt \
- && grep -E "^\[GNUPG:\] VALIDSIG .* $FINGERPRINT$|^\[GNUPG:\] VALIDSIG $FINGERPRINT " status.txt \
- && test "$(jq -r .version manifest.json)" = "$CLAUDE_CODE_VERSION" \
- && checksum="$(jq -r --arg p "$PLATFORM" '.platforms[$p].checksum' manifest.json)" \
- && echo "$checksum" | grep -Eq '^[0-9a-f]{64}$' \
- && curl -fsSL "$REPOSITORY/$CLAUDE_CODE_VERSION/$PLATFORM/claude" -o claude \
- && echo "$checksum  claude" | sha256sum -c - \
- && chmod 0755 claude
-
-FROM ${BASE}
-ARG BASE
-ARG CLAUDE_CODE_VERSION
-LABEL hfr.claude-code="$CLAUDE_CODE_VERSION" hfr.base="$BASE"
-
-COPY --from=verify /verify/claude /usr/local/bin/claude
+# The specialist image: the pinned base pulled from GHCR (adr:0012-pull-the-specialists-base-image-from-ghcr)
+# plus the pinned Claude Code CLI for Linux, verified at build time against the release manifest,
+# whose gpg signature is checked against Anthropic's release key
+# (adr:0006-run-the-specialist-inside-a-container-per-task, specs/task-sandbox R2.6). Built locally,
+# so the binary is never redistributed.
+
+ARG BASE
+
+FROM debian:bookworm-slim AS verify
+ARG CLAUDE_CODE_VERSION
+ARG REPOSITORY=https://downloads.claude.ai/claude-code-releases
+ARG RELEASE_SIGNER_URL=https://downloads.claude.ai/keys/claude-code.asc
+# The fingerprint published on Claude Code's setup page.
+ARG FINGERPRINT=31DDDE24DDFAB679F42D7BD2BAA929FF1A7ECACE
+ARG PLATFORM=linux-x64
+
+RUN apt-get update \
+ && apt-get install -y --no-install-recommends ca-certificates curl gnupg jq \
+ && rm -rf /var/lib/apt/lists/*
+
+WORKDIR /verify
+RUN test -n "$CLAUDE_CODE_VERSION" \
+ && export GNUPGHOME="$(mktemp -d)" \
+ && curl -fsSL "$RELEASE_SIGNER_URL" -o key.asc \
+ && gpg --batch --import key.asc \
+ && curl -fsSL "$REPOSITORY/$CLAUDE_CODE_VERSION/manifest.json" -o manifest.json \
+ && curl -fsSL "$REPOSITORY/$CLAUDE_CODE_VERSION/manifest.json.sig" -o manifest.json.sig \
+ && gpg --batch --status-fd 1 --verify manifest.json.sig manifest.json > status.txt \
+ && grep -E "^\[GNUPG:\] VALIDSIG .* $FINGERPRINT$|^\[GNUPG:\] VALIDSIG $FINGERPRINT " status.txt \
+ && test "$(jq -r .version manifest.json)" = "$CLAUDE_CODE_VERSION" \
+ && checksum="$(jq -r --arg p "$PLATFORM" '.platforms[$p].checksum' manifest.json)" \
+ && echo "$checksum" | grep -Eq '^[0-9a-f]{64}$' \
+ && curl -fsSL "$REPOSITORY/$CLAUDE_CODE_VERSION/$PLATFORM/claude" -o claude \
+ && echo "$checksum  claude" | sha256sum -c - \
+ && chmod 0755 claude
+
+FROM ${BASE}
+ARG BASE
+ARG CLAUDE_CODE_VERSION
+LABEL hfr.claude-code="$CLAUDE_CODE_VERSION" hfr.base="$BASE"
+
+COPY --from=verify /verify/claude /usr/local/bin/claude