Problem
Before the package is ever published, its name and the directory it lives in should be corrected — both become permanent the instant a version ships. -core conventionally signals "not directly usable without a binding," but this package is consumed directly and has no binding family, so the suffix misdescribes it. Separately, the registry loader currently owns the KbConfig/loadKbConfig names that the store-level config loader (added in the feature ticket) should hold.
Context
- Pre-publish, so all renames are free. The directory, package name, every
workspace:* consumer, every import, and the skill-helper bundler references must move together.
- The
~/.agents/kb.yaml loader (loadKbConfig/tryLoadKbConfig/KbConfig/KbConfigEntry) loads a registry of KBs, not a single store's config. Renaming it to registry-specific names frees the KbConfig/loadKbConfig names for the store's .kb/config.yaml.
- Isolated as a rename-only change so it carries zero behavior risk and keeps the feature ticket's diff purely about new behavior.
Proposed solution
Rename the package @codeassembly/kb-core → @codeassembly/kb and the directory packages/kb-core → packages/kb, updating every workspace:* consumer, import, and skill-bundler reference. Rename the registry loader and its types to registry-specific names (loadKbRegistry / tryLoadKbRegistry / KbRegistry / KbRegistryEntry). No behavior changes.
Acceptance criteria
Must have
Dependencies
Problem
Before the package is ever published, its name and the directory it lives in should be corrected — both become permanent the instant a version ships.
-coreconventionally signals "not directly usable without a binding," but this package is consumed directly and has no binding family, so the suffix misdescribes it. Separately, the registry loader currently owns theKbConfig/loadKbConfignames that the store-level config loader (added in the feature ticket) should hold.Context
workspace:*consumer, every import, and the skill-helper bundler references must move together.~/.agents/kb.yamlloader (loadKbConfig/tryLoadKbConfig/KbConfig/KbConfigEntry) loads a registry of KBs, not a single store's config. Renaming it to registry-specific names frees theKbConfig/loadKbConfignames for the store's.kb/config.yaml.Proposed solution
Rename the package
@codeassembly/kb-core→@codeassembly/kband the directorypackages/kb-core→packages/kb, updating everyworkspace:*consumer, import, and skill-bundler reference. Rename the registry loader and its types to registry-specific names (loadKbRegistry/tryLoadKbRegistry/KbRegistry/KbRegistryEntry). No behavior changes.Acceptance criteria
Must have
@codeassembly/kb-core→@codeassembly/kb(name andpackages/kbdirectory).workspace:*consumers, imports, and skill-helper bundler references updated; nokb-corereferences remain outside git history.loadKbRegistry/tryLoadKbRegistry/KbRegistry/KbRegistryEntry.kb-corereferences.Dependencies
kb checkfeature).