geneseed 4.6.0 → 4.7.0

package/CHANGELOG.md

@@ -8,6 +8,17 @@ label. For the capability ↔ spec map, see [SHIPPED.md](SHIPPED.md).
 
 ## [Unreleased]
 
+## [4.7.0] — 2026-10-17
+
+Minor: the Deletion Is Deliberate gate stops asking on worktree removal.
+
+### Upgrade notes
+- Run `geneseed rebuild-all` once after updating so installed hooks and OpenCode plugins pick up the change.
+- OpenCode: an `opencode.json` written by an earlier version keeps the four `git worktree remove … -f`/`--force` keys under `permission.bash`. Geneseed no longer claims them, so it neither removes nor reports them; delete them by hand to stop the prompt.
+
+### Changed
+- **`git worktree remove --force` no longer asks.** Removing a worktree is routine agent housekeeping, so the *Deletion Is Deliberate* gate now lets `worktree remove -f`/`--force` through like a plain `worktree remove`, on every host: the Claude Code/OpenClaude/Bob git-gate, OpenCode's permission globs and the guard plugin's warning. Every other destructive git form is gated as before.
+
 ## [4.6.0] — 2026-10-17
 
 Minor: a refactor and cleanup pass over everything since 3.15.0, and the nine gate and counter bugs it turned up.

package/SHIPPED.md

@@ -20,7 +20,7 @@ historical references, not files distributed with the repo.
 > **On version numbers.** [`harness.config.json`](harness.config.json)'s `version` is a
 > human-readable label only. The canonical identity of an installed harness is the
 > **source fingerprint** stamped in `.geneseed-version` (see `geneseed version`), not the
-> string. Current label: **4.6.0**.
+> string. Current label: **4.7.0**.
 
 ## Capabilities
 

package/adapters/opencode/plugins/geneseed-guard.js

@@ -228,7 +228,6 @@ const SHELL_WARN_RE = [
   /\bgit\s+switch\b[^\n]*\s(-[a-zA-Z]*f\b|--force\b|--discard-changes\b)/,
   /\bgit\s+restore\b(?:(?![^\n]*--staged\b)|(?=[^\n]*--staged\b)(?=[^\n]*--worktree\b))/,
   /\bgit\s+stash\s+(drop|clear)\b/,
-  /\bgit\s+worktree\b[^\n]*\bremove\b[^\n]*(-[a-zA-Z]*f\b|--force\b)/,
   /\bgit\s+reflog\b[^\n]*\bexpire\b/,
   /\bgit\s+gc\b[^\n]*--prune\b/,
 ]

package/harness.config.json

@@ -2,5 +2,5 @@
   "_comment": "version is a human-readable release label only; the canonical identity of an installed harness is the source fingerprint stamped in .geneseed-version (see `harness version`), not this string.",
   "theme": "neutral",
   "product": "Geneseed",
-  "version": "4.6.0"
+  "version": "4.7.0"
 }

package/js/hosts/hooks.mjs

@@ -90,11 +90,14 @@ const GIT_GATE_RE = /\bgit\b[^\n]*\b(?:commit|push)\b/;
 // chase — add them if a probe ever shows one in real use), `checkout -f`/`--force` and
 // `switch -f`/`--force`/`--discard-changes`
 // (git's own `-h` lists `-f, --force` AND a separate `--discard-changes` for switch — both
-// discard uncommitted work the same way `checkout --` does), `worktree remove --force`/`-f`
-// (can discard an uncommitted worktree), `reflog expire` and `gc --prune=now` (delete the
-// reflog/dangling-commit safety net recovery depends on), and `push :branch`/`push --delete`
-// (deletes a remote branch — the colon form needs a space before the `:` so `push origin
-// HEAD:main`, an ordinary refspec, is not caught).
+// discard uncommitted work the same way `checkout --` does), `reflog expire` and `gc
+// --prune=now` (delete the reflog/dangling-commit safety net recovery depends on), and `push
+// :branch`/`push --delete` (deletes a remote branch — the colon form needs a space before the
+// `:` so `push origin HEAD:main`, an ordinary refspec, is not caught).
+//
+// `worktree remove --force`/`-f` is deliberately NOT here (user decision, 2026-10-17): removing
+// a worktree is routine agent housekeeping, so it passes like a plain `worktree remove`. The
+// OpenCode guard's `SHELL_WARN_RE` and `LAW_IV_BASH` (js/hosts/settings.mjs) dropped it too.
 //
 // `restore` and `stash drop`/`stash clear` are carved OUT of the shared `\bgit\b[^\n]*\b(…)`
 // wrapper above and anchored to the verb position instead (`git`, an optional `-C <path>`, then
@@ -106,7 +109,7 @@ const GIT_GATE_RE = /\bgit\b[^\n]*\b(?:commit|push)\b/;
 // combination DOES discard working-tree changes, unlike `--staged` alone) while still deferring
 // on `--staged` alone.
 const DESTRUCTIVE_GIT_RE =
-  /\bgit\b[^\n]*\b(?:reset\b[^\n]*\s--hard\b|clean\b[^\n]*\s(?:-[a-zA-Z]*f|--force\b)|branch\b[^\n]*\s(?:-D\b|--delete\b[^\n]*--force\b|--force\b[^\n]*--delete\b)|checkout\s+--\s|checkout\b[^\n]*\s(?:-[a-zA-Z]*f\b|--force\b)|switch\b[^\n]*\s(?:-[a-zA-Z]*f\b|--force\b|--discard-changes\b)|worktree\b[^\n]*\bremove\b[^\n]*(?:-[a-zA-Z]*f\b|--force\b)|reflog\b[^\n]*\bexpire\b|gc\b[^\n]*--prune\b|push\b[^\n]*(?:\s--force|\s-[a-zA-Z]*f\b|\s\+\S|\s--delete\b|\s:\S))|\bgit(?:\s+-C\s+\S+)*\s+restore\b(?:(?![^\n]*--staged\b)|(?=[^\n]*--staged\b)(?=[^\n]*--worktree\b))|\bgit(?:\s+-C\s+\S+)*\s+stash\s+(?:drop|clear)\b/;
+  /\bgit\b[^\n]*\b(?:reset\b[^\n]*\s--hard\b|clean\b[^\n]*\s(?:-[a-zA-Z]*f|--force\b)|branch\b[^\n]*\s(?:-D\b|--delete\b[^\n]*--force\b|--force\b[^\n]*--delete\b)|checkout\s+--\s|checkout\b[^\n]*\s(?:-[a-zA-Z]*f\b|--force\b)|switch\b[^\n]*\s(?:-[a-zA-Z]*f\b|--force\b|--discard-changes\b)|reflog\b[^\n]*\bexpire\b|gc\b[^\n]*--prune\b|push\b[^\n]*(?:\s--force|\s-[a-zA-Z]*f\b|\s\+\S|\s--delete\b|\s:\S))|\bgit(?:\s+-C\s+\S+)*\s+restore\b(?:(?![^\n]*--staged\b)|(?=[^\n]*--staged\b)(?=[^\n]*--worktree\b))|\bgit(?:\s+-C\s+\S+)*\s+stash\s+(?:drop|clear)\b/;
 
 // `loopExempt` — a WHITELIST, not the blacklist this replaced. A false ask costs one prompt; a
 // false allow publishes. So the exemption holds only when the ENTIRE command is built from

package/js/hosts/settings.mjs

@@ -103,11 +103,16 @@ const consentRuleOn = (d, excluded = []) =>
  * like `-d`, so it is deliberately NOT a key here; `-D --force`/`--delete -f`/`-d --force`/
  * `-df` are the same act again and are a known ceiling this does not chase); `checkout
  * -f`/`--force` and `switch -f`/`--force`/`--discard-changes` (git's own `switch -h` lists
- * `-f, --force` and `--discard-changes` as two separate options); `worktree remove -f`/`--force` (both
- * flag-then-path and path-then-flag order); `reflog expire`; `gc --prune` (matched bare, since
- * a `--prune` with no `=now` still eventually prunes); and `push *--delete*` / `push * :*` (a
- * literal space before the colon, so `push origin HEAD:main`, an ordinary refspec, does not
- * match).
+ * `-f, --force` and `--discard-changes` as two separate options); `reflog expire`; `gc
+ * --prune` (matched bare, since a `--prune` with no `=now` still eventually prunes); and `push
+ * *--delete*` / `push * :*` (a literal space before the colon, so `push origin HEAD:main`, an
+ * ordinary refspec, does not match).
+ *
+ * `git worktree remove -f`/`--force` was a key here and was REMOVED (user decision, 2026-10-17:
+ * worktree removal is routine housekeeping, not a Law IV deletion). Removal from this list also
+ * removes the four globs from `OWNED_BASH`, so an `opencode.json` written before keeps them —
+ * neither taken back nor reported as stranded, since Geneseed no longer claims them. Its user
+ * deletes them by hand (the CHANGELOG upgrade note says so).
  *
  * `git restore` is DELIBERATELY NOT HERE. Its rule is "ask unless `--staged` appears ALONE" —
  * `--staged --worktree` together still discards the working tree — and a glob has no negation,
@@ -128,8 +133,6 @@ const LAW_IV_BASH = ['git push --force*', 'git push -f*', 'git push *--force*',
   'git checkout -f*', 'git checkout * -f*', 'git checkout --force*', 'git checkout * --force*',
   'git switch -f*', 'git switch * -f*', 'git switch --force*', 'git switch * --force*',
   'git switch --discard-changes*', 'git switch * --discard-changes*',
-  'git worktree remove -f*', 'git worktree remove --force*',
-  'git worktree remove * -f*', 'git worktree remove * --force*',
   'git reflog expire*', 'git gc --prune*', 'git gc * --prune*',
   'git stash drop*', 'git stash clear*',
   'git push *--delete*', 'git push * :*'];

package/package.json

@@ -1,7 +1,7 @@
 {
   "//": "Every field here is argued and gated in tests/unit/package_manifest.test.mjs. `files`, `bin` and `engines` each have a test that fails when reality drifts from this file; `version` mirrors harness.config.json and is gated too. Read that docblock before editing this one.",
   "name": "geneseed",
-  "version": "4.6.0",
+  "version": "4.7.0",
   "description": "A portable, theme-able harness you implant once and use everywhere to grow a disciplined AI coding agent.",
   "keywords": [
     "ai",