Release 2.1.28 (2026-07-08)¶

Documentation¶

add post-merge validation doctrine (#592) Extend epic-create with the validation task type: what it is (not PR-workable, closes only on PASS, gates rollup by staying open, blocked-by its deps), the judgment doctrine for when to add one (cold rebuild / live-lab / deploy smoke test; infra epics get a cold-rebuild validation by default), granularity (1:1 / epoch / epic bookend), and creation via vrg-issue-create --kind validation with the generic author-defined precondition scaffold. Seed infra cold-rebuild validations at epic-creation time. Part of epic vergil-project/.github#115. Ref #589.
discover/create validation follow-ons + redirect (#593) Teach issue-implement the post-merge validation concept: (1) a preflight redirect — a validation-labelled issue is run via issue-validate, not implemented here; (2) discover-and-create — when pipeline tests cannot prove acceptance (needs a cold rebuild / live-lab / deploy check after merge), mint a validation follow-on blocked-by this task; (3) never declare the task or epic done while a validation is outstanding. Part of epic vergil-project/.github#115. Ref #590.

add issue-validate skill (#594) New skill for the execution half of the post-merge validation framework: run a validation-labelled issue's checklist and record the result. Preflight confirms USER + the validation label; a preconditions gate runs first (block-not-fabricate on failure); the checklist runs against the live target; the result is a comment with a load-bearing 'Outcome: PASS/FAIL' line (the contract vrg-epic-audit reads). PASS closes the issue (epic rolls up); FAIL holds it open and files fix task(s). No worktree, no commits, no PR — deliberately contrasted with issue-implement. Part of epic vergil-project/.github#115. Ref #591.