Skip to content

Release 2.1.56 (2026-11-02)

Documentation

  • sweep the docs for paad unattended mode (#892)
  • docs(paad): describe the delegate requirement and the build/ exception in the site docs

The skills page gains a section on what a session needs for paad review rounds: the delegate, the plugin-dirs override and how to turn it on, the Lima-only limit, and where agent state lives. issue-implement notes that the agentic-review gate cannot run on a cloud VM. The hooks page and the doctrine state the worktree convention's build/ exception, and the policy's register records running the fork's tree. Ref #820.

  • docs(issue-implement): say the agentic-review gate pauses on a cloud VM and qualify the read-only comments

The skill's cloud section, the site page's issue-implement paragraph and the README row say the gate needs a Lima session, and that on a cloud VM the human accepts the branch unreviewed or moves the task. The two worktree hooks' comments say read-only for source, with the build/ exception. Ref #820.

  • docs(issue-implement): say issue-implement runs in a Lima session

The agentic-review gate cannot run on a cloud VM, so the skill's cloud section, the site page and the README say to run the skill in a Lima session, and that a task started on a cloud VM is implemented again there, since its branch is not pushed before report-ready. The README row links the site's paad review rounds section. Ref #820.

  • docs(issue-implement): stop in Preflight when the session cannot dispatch the paad delegate

issue-implement now checks for paad:paad-delegate before creating a worktree. Without it the agentic-review gate cannot run, so the skill stops, posts nothing on the issue and tells the human to start a Lima session with the fleet's paad checkout loaded. The skill's cloud section and the site page say a cloud VM stops there. Ref #820.

Features

  • allow Write and Edit anywhere in the main clone's ignored build/ (#896)
  • feat(hooks): allow Write and Edit anywhere in the main clone's build/

The worktree write hook now allows any target that normalises to a path inside the main clone's ignored build/ scratch directory, not only build/.vergil-state/, matching the worktree convention's build/ exception. Paths that leave build/ through .. or a symlink, or through a build that is itself a symlink, are still denied. Tests, the hooks page, the README, the design spec and doctrine section 1.5 follow; the state-directory checks are unchanged.

  • fix(hooks): allow only git-ignored paths under the main clone's build/

A Write or Edit under build/ is allowed only when git check-ignore reports the target ignored; a non-zero result or a git failure denies it. Adds tests for a build/ the repo does not ignore and for a tracked file under build/, and notes the rule on the hooks page and in the design spec.

  • fix(hooks): isolate the write-guard tests from user git config and cover a failed ignore check

The hook's tests now run git with no global or system config and a scratch HOME, so only each scratch repo's .gitignore decides what is ignored, and add a row where git check-ignore fails, asserting a deny for that reason. The hook's comment and deny message say plainly that git does not report the path ignored. Doctrine section 1.5 and the design spec's denial and edge-case lists now state the ignored-only rule for build/.

  • test(hooks): assert the reason on the write-guard's build/ deny rows

The rows for a build/ that is not ignored and a tracked file under build/ now also check the deny reason, so each passes only on the deny it is meant to exercise.

CI Evidence: All gates passed — full audit bundle available. Download →