Skip to content

Release 2.1.54 (2026-11-02)

Documentation

  • add the paad-delegate path, with today's path as fallback (#878)
  • docs(paad-doctrine): add the delegate path, with today's path as fallback

Rounds in both modes dispatch paad:paad-delegate when the session has it loaded, with the validated delegate prompts, and keep today's prompts and checks as the fallback path, each round recording its path. The shared procedure moves into the common core: the selection rule, the delegate's result and output checks, the fail-closed security-section cut, screening on both paths, and the guards that run on both paths. Output checks match fixed keywords without regard to case. The never-adopted paad-config fallback section is retired.

  • docs(paad-policy): record unattended mode, the fleet checkout and the fallback path

Records the --plugin-dir override and how it is turned on and off, the Lima-only rule, the two paths, the fleet checkout's rules and its validation gate (also for switching to a released paad), the accepted risks, and the deviations-register rows the delegate path retires. No paad/config file is adopted in either mode.

  • docs(skills): point design review and the agentic-review gate at the doctrine's path selection

  • docs(paad-doctrine): tighten the delegate path's order, pauses and private details

The checks after a review run before anything is written to the state directory on both paths. A blocked result's reason, Defaults applied lines and Config not followed paths go to the human in the terminal, with only counts in public records. A delegate must announce the version paad-policy records as validated. The dismiss ruling is defined for blocked and uncuttable results, round subdirectories are cleared or never reused on re-runs, a kept uncuttable result records its hash, pushback's Outside the spec field is checked and screened, and the skills name the details-file hashing.

  • docs(paad-policy): make the fork override the standing arrangement and record the validated delegate version

The override and fleet checkout are permanent: the fork tracks upstream and runs ahead of it, every move of fleet (including a sync) passes the validation gate, and fleet moves only when no review is running. The fallback retires once the delegate is reliably available rather than at a paad release. The backlog row applies on both paths, and the report-reading paragraph is scoped to the fallback path.

  • docs(paad-doctrine): settle the delegate path's edge cases after a review

Defines what is written when a check after the review fails, what a blocked result is checked for and how it stops, the cut's line matching, one numbering rule for details files in both modes, a check of the ignored paad directories after each delegate review, and how a run after a blocked round is numbered. The validated-version check and policy say what the check does and does not cover. Policy section 1 limits the version warning to the fallback path, and epic-create lists each never-re-run exit.

  • docs(paad-doctrine): close the remaining gaps in the delegate path's exits and the fleet gate

Defines when a review counts as returned, what is kept and recorded when a blocked result also fails a check, how a pre-dispatch failure or a reported write stops a round, that a differing state-directory hash takes precedence, discard lines as a count whenever any candidate was security-class in both modes, the ignored paad directories checked before dispatch too, the counts-line labels among the keywords, and the Options field's lines. epic-create checks the hash before the cut and stops on pre-dispatch failures; issue-implement names the kept-whole case. paad-policy fixes the order of a fleet move and its gate.

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