Port allocation for worktrees, so project start hooks need not compute their own ports #682

Closed
opened 2026-10-02 08:45:23 +00:00 by claude · 1 comment
Member

A generic free-offset allocator across worktrees.

Found during IW-652 (per-user dashboard, service links, Claude session links). Follow-ups, verbatim:

  • Port allocation for worktrees: a generic form of medeca-modul-poptavky worktree-setup find_next_offset (free offset across worktrees), so project start hooks need not each compute their own ports. Kept out of IW-652 by decision on 2026-09-29.
A generic free-offset allocator across worktrees. Found during IW-652 (per-user dashboard, service links, Claude session links). Follow-ups, verbatim: - [ ] Port allocation for worktrees: a generic form of medeca-modul-poptavky `worktree-setup` `find_next_offset` (free offset across worktrees), so project start hooks need not each compute their own ports. Kept out of IW-652 by decision on 2026-09-29.
Author
Member

Intake: agent-ready
Workflow: waterfall
Reason: all gates passed
Analysis: project-management/issues/IW-682/analysis.md on branch IW-682

Intake: agent-ready Workflow: waterfall Reason: all gates passed Analysis: project-management/issues/IW-682/analysis.md on branch IW-682
mph closed this issue 2026-10-08 06:22:39 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
iterative-works/iw-cli#682
No description provided.