Skip to content

Release 2.1.279 (2026-10-29)

Documentation

  • bring the site docs in line with the final steering and settings model (#3804)
  • docs(site): bring the site docs in line with the final steering and settings model

Present-tense the Claude config ownership page now that epic 558 has landed, record the cold-rebuild result for the plugin reconcile step, describe the CLAUDE.md template region and 200-line budget in Consuming Repo Setup and Getting Started, and fix a broken CI Architecture anchor in the config audit page.

  • docs(site): describe the CLAUDE.md layout in Getting Started and link the full section

  • docs(site): separate the agent VM plugin observation from the dated platform facts

  • docs(site): state the local-settings guard's reach precisely in Consuming Repo Setup

  • describe the agentic-review gate and fix the security-records recipe (#3808)

  • docs(site): describe the agentic-review gate in the implement path

issue-implement now passes an advisory agentic-review gate before handoff (epic vergil-project/.github#568). The issues standard says so briefly and links to the paad review doctrine for the rules. Ref #3721

  • docs(site): trim the gate paragraph and match the security-records guide to the doctrine

The issues standard now only names the advisory gate and links to the doctrine. The security-records guide described an older agentic-review recipe that recorded every security finding at collection and split fixed ones into the task; the doctrine records only findings not fixed, at the end of the round, never on the task. Ref #3721

  • docs(site): tighten the gate wording and the security-records exceptions

Say the gate runs, and what advisory means for it. The guide's policy now names the one exception to one record per finding, and the review section's intro lists only the commands its recipes use. Ref #3721

  • describe human-gated design-review rounds in the epic-create pipeline (#3811) The issues standard now lists the spec pushback, plan pushback and alignment rounds and links to mode 1 of the paad review doctrine. The security-records guide links to the doctrine's single severity table instead of copying it, and its design-review recipe matches the doctrine: only new and repair findings are recorded, and a rejected finding's intake issue is closed as not planned. Ref #3719

Features

  • add a --plugin-dir override read from ~/.config/vergil/plugin-dirs.toml (#3843)
  • feat(vrg-vm): add a --plugin-dir override read from ~/.config/vergil/plugin-dirs.toml

vrg-vm session reads plugin_dirs from a hand-made host file and adds --plugin-dir for each entry to the claude launch on Lima, after --model. Each directory is checked in the guest before exec, and a missing one fails the launch. A malformed file fails every launch; a cloud session runs the installed plugins and prints a Lima-only notice. Ref #3824.

  • fix(vrg-vm): skip plugin-dir guest checks when listing sessions; report an unreadable override file

Listing sessions (no --label, --resume or --fresh) starts no claude, so a plugin directory missing in the guest no longer blocks it; the guard still fails every claude launch. An unreadable, directory-typed or non-UTF-8 plugin-dirs.toml now raises PluginDirsError naming the file instead of escaping as a traceback. Docs and tests updated.

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