fix(cli): resolve DB identity on delegated worktree updates (#746)#841
fix(cli): resolve DB identity on delegated worktree updates (#746)#841paarthsikka wants to merge 1 commit into
Conversation
…-dev#746) - Strip REPOWISE_DB_URL from os.environ during delegated run_update so it honors the copied DB - Add atomic try/except rollbacks to seed staging and rename phases - Guard sweep_stale_seed_backups with an mtime staleness check - Pass full=False instead of full=force to prevent re-embedding everything on update - Skip updating entirely when dry_run=True to prevent bogus output - Persist --coverage setting explicitly provided in init to config.yaml
|
✅ Health: 7.6 (unchanged) 📋 At a glance Files & modules (2)
🩹 Review priority (files here with the most recent bug-fix history — defects cluster, so review these first)
🔎 More signals (2)🔥 Hotspots touched (3)
🔗 Hidden coupling (1 file)
📊 Full report · ⭐ Star Repowise · 📥 Install bot · Last updated 2026-07-14 21:11 UTC |
Summary
.repowisereplacement with multi-pass atomic rollbacks to prevent corrupted partial directory states upon failure.--coverageflag persists successfully duringinitacross full-state rewrites, locked down with a new integration test.Related Issues
Fixes #746
Builds on #747
Test Plan
pytest)ruff check .)npm run build) (if frontend changes)Checklist