Phase 2 of docs/prds/archie-core-v2-architecture.md. Current worktree lifecycle is fresh-clone-per-task with status-driven cleanup, no TTL. Add persistent volume support with TTL-based expiry to avoid repeated full clones for repeated work on the same repo.
Acceptance Criteria
Container/worktree storage can persist across tasks for the same repo up to a configured TTL, with automatic cleanup after expiry.
Imported from beads archie-core-1786637499292-362-8b520db8 · GitHub #383 · type feature · priority P2 · created 2026-08-08 · closed 2026-08-08
Phase 2 of docs/prds/archie-core-v2-architecture.md. Current worktree lifecycle is fresh-clone-per-task with status-driven cleanup, no TTL. Add persistent volume support with TTL-based expiry to avoid repeated full clones for repeated work on the same repo.
### Acceptance Criteria
Container/worktree storage can persist across tasks for the same repo up to a configured TTL, with automatic cleanup after expiry.
---
_Imported from beads `archie-core-1786637499292-362-8b520db8` · GitHub #383 · type feature · priority P2 · created 2026-08-08 · closed 2026-08-08_
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Phase 2 of docs/prds/archie-core-v2-architecture.md. Current worktree lifecycle is fresh-clone-per-task with status-driven cleanup, no TTL. Add persistent volume support with TTL-based expiry to avoid repeated full clones for repeated work on the same repo.
Acceptance Criteria
Container/worktree storage can persist across tasks for the same repo up to a configured TTL, with automatic cleanup after expiry.
Imported from beads
archie-core-1786637499292-362-8b520db8· GitHub #383 · type feature · priority P2 · created 2026-08-08 · closed 2026-08-08