A snapshot: read at commit 707a04c7ce8 on 2026-10-18T00:06:01Z by majordomus 0.29.0. Nothing on this page is read again. See it live

I2702

A checkout keeps one address across restarts, because its server binds a port derived from the checkout

Where it stands

devtask.issue

Readiness: ready no dependency and no gate holds it; nobody has started it
Status: READY
Can start: startable
Milestone: runtime-lifecycle
Milestone status: ACTIVE
Wave: 1
Waiting on: none
Holds back: none
Behind it in all: 0
Evidence: 0 of 1

Moves

plan.transition

What it is

Objective: Bind a port derived from the repository and worktree identity before falling back to a free one, so that a Streamable HTTP client configuration or a bookmarked UI names an address that survives a restart.
Why: Split from I2131 on 2026-10-14. I2131 made every surface's use count toward the idle timeout, and its desired_state said 'Not done here' of a port derived from the repository and worktree identity, while its acceptance criteria still required it, so it could never close. On 2026-10-09 the live server asked for 8741 and served 61068, an address that changes on every restart. The other deferred question of I2131, whether an entry beyond serve ensure is needed, is decided by ADR 0135 and planned as I2484, and is not carried here. Baseline audit of 2026-10-09 at master 1fb8d6be44, lifecycle gap 9 and drift 10.
Now: DEFAULT_PORT is 8741 (apps/majordomus-cli/src/cli.rs); the first checkout to start takes it and every other is given a free port when http::server::bind (apps/majordomus-cli/src/http/server.rs) cannot have the one asked for, a different one on each restart. docs/MCP.md says a taken port is replaced by a free one and shows :8741 in its examples.
Wanted: A server asks first for a port derived from the repository identity and the worktree it serves, so one checkout asks for the same port on every start and two checkouts of one repository ask for different ones; a port that is taken falls back to a free one and both are logged, as today. docs/MCP.md describes the derived port and the fallback.
Done when: unknown: the record declares no `completion`
Risk: unknown: the record declares no `risk`

Acceptance

Two consecutive starts of one checkout's server bind the same port when it is free
Two checkouts of one repository derive different ports
docs/MCP.md describes the derived port and the fallback

Validation: bin/majordomus plan validatecargo test --test serve_lifecycleMJ_TEST_JOBS=4 bash test/run.sh 190_entry_is_automatic
Evidence required: stable_port_per_checkout_test
Evidence present: unknown: the record carries no `evidence` entries

Scope

Touches: apps/majordomus-cli/src/cli.rsapps/majordomus-cli/src/http/server.rsapps/majordomus-cli/src/commands/serve.rsapps/majordomus-cli/src/commands/env.rsapps/majordomus-cli/tests/serve_lifecycle.rsdocs/MCP.md
Not: The idle timer and what counts as use, which I2131 deliveredA majordomus ui command, which ADR 0135 decided and I2484 plans
Depends on: I2131
Priority: p1
Profile: implementation
Parallel safe: false
Owner: unknown: the record declares no `owner`

The work so far

Branches: none
Merged: none
Commits: 0
Trunk: master
Sessions: none
Created: 2026-10-14
Updated: 2026-10-14
Started: unknown: the record declares no `started_at`
Verified: unknown: the record declares no `verified_at`
Completed: unknown: the record declares no `completed_at`

Synchronisation

Adapter: scripts/github-sync
Repository: unknown: the derived plan's header carries no repository
External issue: unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it
State there: unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it

Findings

Nothing is wrong with these records.