[Pearcekieser]

Problem

TitleGenerator.generateAndPersist starts its ephemeral thread with threadStart({cwd, ephemeral: true}) and no config. Codex then loads the user's config.toml and starts every server in [mcp_servers] for that thread. The title turn uses an output schema and no tools, so those processes do nothing. A user with ten configured servers pays ten extra processes per titled session.

#629 releases the title thread after the turn, so these processes exit 60 s later instead of living until codex-acp exits. It does not stop them from starting. This PR is the other half and does not depend on #629.

Change

• Before the ephemeral thread/start, TitleGenerator reads the effective config for the session's cwd with config/read and passes config: {mcp_servers: {<name>: {enabled: false}, ...}} for every configured name.
• With no configured servers, or when config/read fails, the thread starts as before, with no config. Title generation stays best-effort.
• The names come from the effective config only. Codex merges the thread config onto the loaded layers, so mcp_servers: {} disables nothing. Disabling a name no layer defines fails the whole thread/start with invalid transport in mcp_servers.<name>, so a hard-coded list or a union of all layers would be unsafe.

Tests

• TitleGenerator.test.ts: the title thread is started with each configured server disabled, with no config when none is configured, and with no config when config/read fails. The first test fails without the change.
• npm run typecheck and npm run build pass. npm test: 1869 passed, 36 skipped, 1 failed. The failure is JsonSnapshot.test.ts > leaves values nested thousands deep to JSON.stringify, which fails the same way on main (636b082) on this host.
• Real Codex 0.160.1 against a local fake Responses provider, with 2 recording MCP servers in config.toml and 3 sessions on one codex-acp process. Each session sent session/new with a session MCP server, one prompt and session/close:

build	title-thread MCP starts	left after all sessions closed (+75 s)	titles written
main	6	6, until codex-acp exits	3
#629	6	0, each exits 60 s after the title turn	3
this PR	0	0	3
this PR + #629	0	0	3

In every run the main thread's servers started and stopped the same way, 60 s after session/close.

• Direct codex app-server probe of thread/start {ephemeral: true} with 2 configured servers: no config started 2, {"mcp_servers": {}} started 2, nested {name: {enabled: false}} started 0, the dotted mcp_servers.<name>.enabled form started 0, and an undefined name failed thread/start with -32600.

Related to #628 and #629.