REQ-NFR-065
Worktree provisioning on claim completes within 5 seconds for repos up to 1 GB
What
Worktree provisioning on claim SHALL complete within 5 seconds for a repo of up to 1 GB on local disk.
Why
Inside the claim transaction, holding it open longer risks lease-expiry collisions and pessimistic lock contention; agents notice latency on board claims.
How
Pre-warm a per-project repo cache at /var/lib/aipm/repos/<project_uuid> (refreshed by a scheduled fetch) so claim-time work is git worktree add only; avoid full clones on the hot path.
Done when
Benchmark: claim a board item on a 1 GB repo on local disk, measure end-to-end; p95 <= 5 s. Larger repos may exceed; documented as a known limit.
Out of scope
Repos > 1 GB (sized projects); remote forge worktrees.
Category
performance
established project management guidelines Mapping
Worktree provisioning latency is a resource-availability quality target.