@tachikomagundam/abathur 0.2.5 → 0.2.7

package/graders/historian/run-scenario.sh

@@ -20,6 +20,22 @@
 set -euo pipefail
 unit_id="${1:?usage: run-scenario.sh <unitId> <scenario-file> [repoRoot]}"
 scenario_file="${2:?usage: run-scenario.sh <unitId> <scenario-file> [repoRoot]}"
+# Per-unit hook dispatch (s19 autopsy 2026-09-25): a unit may own a hook script
+# run-scenario-<NN>.sh that wraps THIS agent stage plus an instrumented poststage
+# (e.g. the R6-termb 蜂判 for scenario-19). The registered runCommand is one
+# genome-global string, so the dispatch lives here rather than in the spec: when
+# this unit owns a hook and we are not already running inside it (recursion guard
+# set on the way in), defer to the hook. Units without a hook — and every caller
+# that passes an id with no matching file — fall through byte-identical (F1).
+_here="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
+case "$unit_id" in
+  scenario-*)
+    _hook="$_here/run-scenario-${unit_id#scenario-}.sh"
+    if [ -f "$_hook" ] && [ -z "${ABATHUR_HOOK_INNER:-}" ]; then
+      exec env ABATHUR_HOOK_INNER=1 bash "$_hook" "$@"
+    fi
+    ;;
+esac
 [ -f "$scenario_file" ] || { echo "run-scenario: missing scenario file $scenario_file" >&2; exit 2; }
 [ -n "${ABATHUR_TRANSCRIPT:-}" ] || { echo "run-scenario: ABATHUR_TRANSCRIPT not set" >&2; exit 2; }
 key="${ABATHUR_WIKI_KEY_FILE:-}"

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tachikomagundam/abathur",
-  "version": "0.2.5",
+  "version": "0.2.7",
   "description": "Evolution harness: observe failures, mutate, re-bench, select — human-gated promotion, offline lineage bundles.",
   "author": "TachikomaGundam",
   "type": "module",

package/plugin/abathur-command.md

@@ -9,7 +9,7 @@ top-level command (`genome`, `run`, `status`, `bundle`, `graft`, `self-eval`,
 with `command` set to the first word and `extra` set to the remaining tokens,
 then report the CLI exit code (0 ok / 1 blocked decision / 2 cannot-answer)
 and the relevant lines of its output. If no request was given, call the tool
-with `command: "--help"` and summarize the command list. `promote` and
-`tombstone` cannot be called through the tool at all — the tool refuses them.
+with `command: "--help"` and summarize the command list. `promote`,
+`tombstone` and `retract` cannot be called through the tool at all — the tool refuses them.
 They are human gates that belong to a terminal: if the user asks for one,
-tell them to run `abathur promote …` / `abathur tombstone …` there.
+tell them to run `abathur promote …` / `abathur tombstone …` / `abathur retract …` there.

package/plugin/abathur.ts

@@ -1,4 +1,4 @@
-// abathur-opencode-plugin v0.2.5
+// abathur-opencode-plugin v0.2.7
 // Official opencode plugin adapter for the abathur evolution harness.
 // Registers ONE agent tool, `abathur`, that shells out to the abathur CLI —
 // argv-only (node:child_process execFile, never a shell), top-level commands
@@ -29,7 +29,7 @@ const TIMEOUT_MS = 120_000;
 const MAX_OUTPUT_BYTES = 64 * 1024;
 
 /** The seven tool-reachable top-level commands plus --help. Anything else is refused locally.
- * promote/tombstone are human gates and deliberately terminal-only (0.2.1): not reachable here. */
+ * promote/tombstone/retract are human gates and deliberately terminal-only (0.2.1/0.2.7): not reachable here. */
 const ALLOWED_COMMANDS: readonly string[] = [
   "genome",
   "run",
@@ -133,10 +133,10 @@ top-level command (\`genome\`, \`run\`, \`status\`, \`bundle\`, \`graft\`, \`sel
 with \`command\` set to the first word and \`extra\` set to the remaining tokens,
 then report the CLI exit code (0 ok / 1 blocked decision / 2 cannot-answer)
 and the relevant lines of its output. If no request was given, call the tool
-with \`command: "--help"\` and summarize the command list. \`promote\` and
-\`tombstone\` cannot be called through the tool at all — the tool refuses them.
+with \`command: "--help"\` and summarize the command list. \`promote\`,
+\`tombstone\` and \`retract\` cannot be called through the tool at all — the tool refuses them.
 They are human gates that belong to a terminal: if the user asks for one,
-tell them to run \`abathur promote …\` / \`abathur tombstone …\` there.
+tell them to run \`abathur promote …\` / \`abathur tombstone …\` / \`abathur retract …\` there.
 `;
 
 export default {
@@ -168,7 +168,7 @@ export default {
           "(0 ok, 1 blocked decision, 2 cannot-answer). Honest privilege note: this " +
           "tool carries bash-equivalent privilege — `run` and `genome` legitimately " +
           "spawn mutator/engine binaries by design — so the allowlist limits typos " +
-          "and UX, not capability. `promote` and `tombstone` are deliberately NOT " +
+          "and UX, not capability. `promote`, `tombstone` and `retract` are deliberately NOT " +
           "reachable here: they are human gates, run in a terminal.",
         args: {
           command: tool.schema