feat: config file max_cached

[dezren39]

codedb/src/mcp.zig

Line 29 in 04a21fb

const MAX_CACHED = 5;

hello can you please make a config file referenced either by

• next to binary
• next to pwd or in repo root
• --config-file flag passed to binary
  and enable changing this number if a user would like

[dezren39]

i'll stop at this and #101, but i could also see this for MAX_NGRAM_LEN

i think the only one i was actively interested in is maybe bumping max_cached but I'm not totally sure how this is setup, is this max_cached for this instantiation of the mcp server or for the system? many days i might have 5 or more worktrees open across 2 projects, some days i may be researching and may get up to or over 5 different repos i'm actively comparing. i don't know exactly if this would cause me problems or not but i was looking into it and intending to play with the settings then found there weren't settings per se unless i wanted to recompile. is this a disk space thing or is the number of cached all loaded into ram or cause a tax on the cpu? i have a large drive and a lot of ram and when i'm not compiling chromium because nix usually i have some free cores.