Skip to content

Release 2.1.128 (2026-07-12)

Documentation

  • document the epic model, compliance invariants, and finite-epic relocation (#2281) Add an Epics section to the github-issues standard (epic label; finite vs perpetual/ad-hoc epics; the /.github home rule; the retired standing alias; managed task -> Closes -> rollup; the vrg-epic-audit invariants) and rewrite the stale sub-issue linking section to use vrg-issue-create and vrg-epic-link since raw gh api is blocked for agents.

Add issue transfer to the documented vrg-gh issue allowlist in the permission model, and rewrite the epic-home visibility-flip runbook to relocate a finite epic via intra-org vrg-gh issue transfer (pinning the source with -R), relinking reflink-only children with vrg-epic-link and verifying with vrg-epic-audit.

  • document intake queues, epic bookends, and epic-create workflow (#2284) Fill the epic/task model coverage gaps from epic vergil-project/.github#85 in the versioned site docs (standards/github-issues.md):

  • Add an Intake queues section: the three input shapes (triage/idea/research), their .github routing, and vrg-triage-create --kind; add an Intake item definition.

  • Add a Creating an epic subsection describing the epic-create orchestrator workflow and its four-stage interaction doctrine (interactive brainstorming/pushback/alignment; automated writing-plans).
  • Add The bookend convention subsection: docs-first opening bookend, documentation-review + follow-on-brainstorm closing bookends, every epic >= 2 tasks, closure gated by the review task via the existing rollup.
  • Mention vrg-adhoc-epic ensure alongside the --epic adhoc sentinel.

Also link the orphaned epic-home-visibility-flip guide into the mkdocs nav.

Features

  • resume a VM session by exact name (--resume NAME) (#2285) Add '--resume NAME' to 'vrg-vm session', resolving a session by its exact display name instead of a slot number. Epic-renamed titles (e.g. 'epic-85-centralize-epics-adhoc') do not fit the '::' slot scheme and fall out of the slot map, so name-based resume is the only way to reconnect to them directly — pasting the name shown on screen after a VM rebuild lands straight back in that session.

The host flag is mutually exclusive with --slot/--fork/--fresh and threads to the in-VM resolver as --resume-name; a new pure-logic select_by_name() does an exact-name lookup, reusing the module's existing liveness-then-recency collision rule for the /clear-rotation case where two session ids share a title. No match refuses; no staleness sweep or prompt runs on an explicitly named resume.