Proposal: add configurable ai-index generation options

[KimHyeongRae0]

ai-index.json currently hardcodes chunk size and keyword count. I propose exposing aiIndex.maxChunkLength and aiIndex.maxKeywords, preserving defaults. I can send a typed/docs/test PR after direction is confirmed.

[rubenmarcus]

Thanks @KimHyeongRae0 — this is a sensible addition and the defaults you proposed work for us. Please go ahead with the PR.

Confirmed API shape:

aiIndex?: {
  maxChunkLength?: number;  // default 2000
  maxKeywords?: number;     // default 10
};

Resolved to non-optional values in ResolvedAeoConfig. No validation needed — sub-1 values produce sensible behavior (maxKeywords: 0 → empty array; maxChunkLength: 0 → one chunk per paragraph).

Files to touch:

src/types.ts — add aiIndex to both AeoConfig and ResolvedAeoConfig, following the existing nested-object pattern (look at widget/schema)
src/core/utils.ts — add defaulting in resolveConfig (same ?. + || pattern as the other sub-objects)
src/core/ai-index.ts — drop the = 2000 default from chunkContent, add maxKeywords param to extractKeywords, thread config.aiIndex.* through both generateAIIndex (lines 69, 71, 118, 119) and collectAIIndexEntries (line 50, which also chunks/extracts keywords for content-dir files — easy to miss)
What we'd like in the PR:

Tests in src/core/utils.test.ts: empty-config default + partial-override
Tests in src/core/ai-index.test.ts: custom maxChunkLength produces expected chunk count + custom maxKeywords caps the array length

Brief mention in any user-facing docs (if you spot one)

Looking forward to it

[rubenmarcus]

PR #46 implements this exactly to spec — both options wired through, defaults preserved, two new tests, plus a docs update in configuration.mdx. Greptile passed and flagged only two non-blocking P2s (validateConfig warning for sub-1 values + a small doc wording tweak). Closing this once #46 merges. Thanks @KimHyeongRae0. 🙏