Problem
Connection catalog authority already lives in Runtime Policy (connection-catalog.json). Host bootstrap, config import/export, Desktop, CLI, and Eval all go through that catalog.
FileConnectionStore still maintains a second file, llm-connections.json:
packages/storage/src/connection-store.ts — createConnectionStore / createConnectionStoreForFilepackages/storage/src/relay-profile-store.ts — write helper used only by that storepackages/storage/src/__tests__/connection-store.test.ts
There is no production reader. Host never opens the file. createConnectionStoreForFile has zero callers. The remaining writers are an e2e seeder and a Computer Use script:
apps/desktop/src/main/e2e-fixture/scenarios-settings.ts still writes llm-connections.jsonscripts/computer-use/real-model.mjs still copies or creates that file through createConnectionStore
README still documents llm-connections.json as current workspace layout. After #2749 removed connection v1 compatibility, the leftover store cannot migrate or serve old files. Those files are already inert.
This is a second connection authority that product code no longer consults. Keeping it forces tests, scripts, and docs to stay in sync with a dead path.
Desired outcome
One connection file authority: the Runtime Policy catalog. The old store, its export, its tests, and the leftover writers disappear. Existing llm-connections.json files stay on disk as inert user data; Maka does not import them.
Alternatives or workarounds
Keep the store as a silent importer for pre-catalog files. That path has no Host reader today, so it cannot actually import those files.
Acceptance
Non-goals
Related
Verified on main at eea5cd870.
Relevant code:
packages/storage/src/connection-store.tspackages/storage/src/runtime-policy/connection-catalog-document.tspackages/runtime-host/src/server/bootstrap-runtime-policy.tsapps/desktop/src/main/e2e-fixture/scenarios-settings.tsscripts/computer-use/real-model.mjs
This issue was identified during a simplification audit and prepared with AI assistance (Pi / grok-4.6). A human contributor reviewed the analysis and owns the submission.
Problem
Connection catalog authority already lives in Runtime Policy (
connection-catalog.json). Host bootstrap, config import/export, Desktop, CLI, and Eval all go through that catalog.FileConnectionStorestill maintains a second file,llm-connections.json:packages/storage/src/connection-store.ts—createConnectionStore/createConnectionStoreForFilepackages/storage/src/relay-profile-store.ts— write helper used only by that storepackages/storage/src/__tests__/connection-store.test.tsThere is no production reader. Host never opens the file.
createConnectionStoreForFilehas zero callers. The remaining writers are an e2e seeder and a Computer Use script:apps/desktop/src/main/e2e-fixture/scenarios-settings.tsstill writesllm-connections.jsonscripts/computer-use/real-model.mjsstill copies or creates that file throughcreateConnectionStoreREADME still documents
llm-connections.jsonas current workspace layout. After #2749 removed connection v1 compatibility, the leftover store cannot migrate or serve old files. Those files are already inert.This is a second connection authority that product code no longer consults. Keeping it forces tests, scripts, and docs to stay in sync with a dead path.
Desired outcome
One connection file authority: the Runtime Policy catalog. The old store, its export, its tests, and the leftover writers disappear. Existing
llm-connections.jsonfiles stay on disk as inert user data; Maka does not import them.Alternatives or workarounds
Keep the store as a silent importer for pre-catalog files. That path has no Host reader today, so it cannot actually import those files.
Acceptance
connection-store.ts,relay-profile-store.ts, their tests, and the./connection-storeexport are removedwriteConnectionsstops writingllm-connections.json; if a fixture still needs connection rows, it seedsconnection-catalog.json/ the live Runtime Policy writerscripts/computer-use/real-model.mjsseeds catalog + credential vault instead ofllm-connections.jsonllm-connections.jsonas current layoutllm-connections.jsonNon-goals
llm-connections.jsonfilesconnection-catalog.json, credential vault, or Host bootstrapRelated
Verified on
mainateea5cd870.Relevant code:
packages/storage/src/connection-store.tspackages/storage/src/runtime-policy/connection-catalog-document.tspackages/runtime-host/src/server/bootstrap-runtime-policy.tsapps/desktop/src/main/e2e-fixture/scenarios-settings.tsscripts/computer-use/real-model.mjsThis issue was identified during a simplification audit and prepared with AI assistance (Pi / grok-4.6). A human contributor reviewed the analysis and owns the submission.