@bookedsolid/rea 0.26.1 → 0.28.0

package/dist/policy/types.d.ts

@@ -169,6 +169,37 @@ export interface ReviewPolicy {
      * a `rea.push_gate.verdict_flip` audit event and overwrite the cache.
      */
     cache_ttl_ms?: number;
+    /**
+     * 0.28.0 helix-029 — path-scoped finding filter. Gitignore-style
+     * globs against repo-relative paths. Findings whose `file` matches
+     * any glob in this list are filtered OUT before the verdict is
+     * computed, but are still emitted on stderr (so the operator can
+     * file them upstream). Useful for downstream consumers of rea who
+     * cannot patch rea-managed paths but should not be blocked from
+     * pushing while waiting on an upstream fix.
+     *
+     * Setting this list also enables `auto_exclude_managed` by default —
+     * paths from `.rea/install-manifest.json` are excluded in addition
+     * to whatever globs are listed here. Pass `auto_exclude_managed:
+     * false` to opt out and rely on `exclude_paths` alone.
+     *
+     * Empty (or unset) → no filtering, pre-0.28.0 behavior.
+     *
+     * The audit shape is unchanged; the gate emits a
+     * `filtered_findings_count` counter into the audit metadata so
+     * operators can grep `rea.push_gate.reviewed` to see how many
+     * findings were suppressed without re-parsing prose.
+     */
+    exclude_paths?: string[];
+    /**
+     * 0.28.0 helix-029 — derived default. When `exclude_paths` is set,
+     * defaults to `true` — paths from `.rea/install-manifest.json` are
+     * excluded in addition to the explicit globs. Set explicitly to
+     * `false` to rely only on `exclude_paths`. When `exclude_paths` is
+     * unset, this field is a no-op (no filter is active in the first
+     * place).
+     */
+    auto_exclude_managed?: boolean;
     /**
      * Local-first review enforcement (0.26.0+ — CTO directive 2026-05-05).
      *

package/hooks/_lib/cmd-segments.sh

@@ -162,6 +162,11 @@ _rea_unwrap_at_depth() {
   local _unwrap_sep
   _unwrap_sep=$'\x1c\x1d'
   local masked
+  # shellcheck disable=SC1078
+  # SC1078 fires inside the awk program because shellcheck's bash parser
+  # cannot model awk's nested-quote semantics (`'\''` here is the
+  # bash-to-awk single-apostrophe escape pattern, not an unclosed shell
+  # string). Verified false-positive — the awk program parses cleanly.
   masked=$(printf '%s%s' "$cmd" "$_unwrap_sep" | awk '
     BEGIN { RS = "\034\035" }
     {
@@ -527,6 +532,11 @@ _rea_split_segments() {
   # records; the existing pipeline then quote-masks and splits each
   # record independently. Inner payload anchors trigger words for the
   # `any_segment_*` checks downstream.
+  # shellcheck disable=SC1078
+  # SC1078 fires inside the awk program because shellcheck's bash parser
+  # cannot model awk's nested-quote semantics (`'\''` here is the
+  # bash-to-awk single-apostrophe escape pattern, not an unclosed shell
+  # string). Verified false-positive — the awk program parses cleanly.
   _rea_unwrap_nested_shells "$cmd" \
     | awk '
         BEGIN {

package/hooks/blocked-paths-bash-gate.sh

@@ -105,6 +105,18 @@ if [ "$sandbox_status" -ne 0 ] || [ "$sandbox_check" != "ok" ]; then
   exit 2
 fi
 
+# 0.28.0 helix-027 (bash total-lockout postmortem) — version-probe per
+# shim. See protected-paths-bash-gate.sh for the full rationale; this
+# shim mirrors the behavior to detect a stale CLI before payload reach.
+probe_out=$("${REA_ARGV[@]}" hook scan-bash --help 2>&1)
+probe_status=$?
+if [ "$probe_status" -ne 0 ] || ! printf '%s' "$probe_out" | grep -q -e 'scan-bash' -e '--mode'; then
+  printf 'rea: this shim requires the `rea hook scan-bash` subcommand (introduced in 0.23.0).\n' >&2
+  printf 'The resolved CLI at %s does not implement it.\n' "$RESOLVED_CLI_PATH" >&2
+  printf 'Run `pnpm install` (or `npm install`) to sync the CLI to the version this shim expects.\n' >&2
+  exit 2
+fi
+
 payload=$(cat)
 if [ -z "$payload" ]; then
   exit 0

package/hooks/protected-paths-bash-gate.sh

@@ -183,6 +183,27 @@ if [ "$sandbox_status" -ne 0 ] || [ "$sandbox_check" != "ok" ]; then
   exit 2
 fi
 
+# 0.28.0 helix-027 (bash total-lockout postmortem) — version-probe per
+# shim. The 0.23.0+ scan-bash subcommand is required; if the resolved
+# CLI is older than 0.23.0 it will refuse with "unknown command" and the
+# shim's exit-code dispatch lands on the catch-all "exit 2" branch
+# WITHOUT explaining why. That was the symptom that locked Jake's
+# helix workspace out of every Bash tool until he ran `pnpm install`.
+#
+# The probe runs `rea hook scan-bash --help` once per shim invocation
+# (~30 LOC) and refuses with an actionable message if the subcommand
+# does not exist. Probe failure is fail-closed (exit 2) — same posture
+# the rest of the shim takes — but the message tells the operator
+# exactly what to do (`pnpm install`).
+probe_out=$("${REA_ARGV[@]}" hook scan-bash --help 2>&1)
+probe_status=$?
+if [ "$probe_status" -ne 0 ] || ! printf '%s' "$probe_out" | grep -q -e 'scan-bash' -e '--mode'; then
+  printf 'rea: this shim requires the `rea hook scan-bash` subcommand (introduced in 0.23.0).\n' >&2
+  printf 'The resolved CLI at %s does not implement it.\n' "$RESOLVED_CLI_PATH" >&2
+  printf 'Run `pnpm install` (or `npm install`) to sync the CLI to the version this shim expects.\n' >&2
+  exit 2
+fi
+
 # Capture stdin once and forward it to the CLI.
 payload=$(cat)
 if [ -z "$payload" ]; then

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@bookedsolid/rea",
-  "version": "0.26.1",
+  "version": "0.28.0",
   "description": "Agentic governance layer for Claude Code — policy enforcement, hook-based safety gates, audit logging, and Codex-integrated adversarial review for AI-assisted projects",
   "license": "MIT",
   "author": "Booked Solid Technology <oss@bookedsolid.tech> (https://bookedsolid.tech)",
@@ -46,6 +46,7 @@
     "profiles/",
     "templates/",
     "scripts/",
+    "data/",
     ".husky/",
     "LICENSE",
     "README.md",