Skip to content

Release 2.1.36 (2026-06-14)

Bug fixes

  • self-heal poisoned uv cache in the in-VM tooling install (#1657) vrg-vm session runs 'uv tool install --reinstall vergil-tooling' inside the VM. --reinstall removes the existing tool before reinstalling, so when the uv cache holds a corrupt artifact (e.g. a zero-byte wheel METADATA left by an unclean VM stop) the reinstall fails after removal and the VM is left with no tooling — permanently bricking the session until the cache is cleared by hand.

Wrap the uv tool install invocation (install and update paths) in a helper that, on failure, clears the VM uv cache and retries once, so a poisoned cache self-recovers. Also make try_update_tooling stop reporting success when nothing is installed: warn and continue only if a working version remains, otherwise abort loudly with a recovery hint.

Documentation

  • add vergil-forge local host design (#1655) Design for a new standalone repo that stands up and operates a persistent, local-first Forgejo instance on owned hardware — the Phase 0 prerequisite of the forge-abstraction strategy (#1521).

Captures the Lima service VM running Forgejo + Postgres on host-mounted data, the Postgres-over-SQLite decision (parallel-agent write concurrency), the Forgejo/Codeberg duality and per-repo solo/shared roles, a config-driven off-box backup target that transitions GitHub to Codeberg, host-local v1 networking, and the vrg-forge lifecycle CLI. Defers shared-repo sync, Codeberg backup, TLS, and CI runners as named later phases.