Problem
When creating entries via the `kb_create` MCP tool, files are placed at the KB root directory instead of the appropriate subdirectory for their type. For example, `backlog_item` entries should go in `kb/backlog/` but instead land in `kb/`.
Observed with 8 entries created via MCP — all landed at root:
All have `type: backlog_item` and should have been placed in `kb/backlog/`.
Expected Behavior
`kb_create` should respect the KB's directory conventions. If the KB has a directory structure that maps types to subdirectories (e.g., `backlog_item` → `backlog/`, `adr` → `adrs/`, `component` → `components/`), new entries should be placed accordingly.
Likely Cause
The MCP tool handler for `kb_create` probably builds the file path from just `kb_root / f"{entry_id}.md"` without consulting the type-to-directory mapping. The CLI `pyrite create` command may have the same issue or may handle it differently.
Fix
Check how the storage layer resolves file paths for new entries. The type → directory mapping likely exists somewhere (kb.yaml type definitions, or convention-based) but isn't being consulted during MCP create.