Say what to store, not where it goes

[razor-x]

Summary

Storing a value meant knowing the key it lives under. Callers wrote config.delete('current_workspace_id') and config.set(`${auth.endpoint}.pat`, token), and the three writes that always go together needed a storeEndpoint helper to keep them together.

The config now answers in the CLI's own terms:

config.setEndpoint(endpoint)        // and the legacy key, and the stale workspace
config.getToken(endpoint)           // hides the per-endpoint key
config.setToken(endpoint, token)
config.unsetToken(endpoint)         // and any un-namespaced token left behind
config.getWorkspace()
config.setWorkspace(workspaceId)
config.unsetWorkspace()
config.getUseRemoteApiDefs()
config.setUseRemoteApiDefs(value)

Every key lives in config/values.ts and is read by config/seam-config.ts alone. Nothing else in the CLI names one.

What moved

• New config/seam-config.ts — SeamConfig, over any ConfigStore. The rules that were spread across callers live here: tokens are keyed per endpoint; getEndpoint falls back to the legacy server key; setEndpoint drops that key and the workspace that belonged to the old endpoint; unsetToken also drops the un-namespaced token an older CLI wrote.
• getConfigStore → getConfig — what the CLI holds is its configuration, not a key/value store. ConfigStore stays as the storage underneath, which PersistentConfigStore and the memory store implement.
• context.ts — resolveAuth reads three methods, and its readString moves into the config, which is the only place that needs it.
• auth/operations.ts — every write is a method call, and storeEndpoint is gone: what it did belongs to setEndpoint.
• rootPaths — seamPaths moves into the config module. Where the CLI keeps its files is config's business, and blueprint/source-npm.ts reads the cache directory from there rather than deriving the same root a second time.

Tests

test/auth/operations.test.ts and test/context.test.ts build a createMemoryConfig() and assert through the same methods, so they no longer restate the storage layout.

Two assertions deliberately still reach for the store, because what they check is invisible above it: that logging out drops an un-namespaced token, and that selecting an endpoint drops the legacy key. Those tests construct createSeamConfig(createMemoryConfigStore(…)) and assert on the store.

157 tests pass.

---

Generated by Claude Code