grepai-search-boosting

Add a search.boost section to .grepai/config.yaml with enabled set to true, then define penalties with factors below 1.0 and bonuses with factors above 1.0. Each entry pairs a path pattern like /tests/ with a numeric factor that multiplies the original search score.

Add penalty patterns matching your test naming conventions, such as /tests/, _test., .spec., or .test., with a factor around 0.5. This halves their scores so production code with similar content ranks above them while tests remain searchable.

Ignoring completely excludes files from the index, while penalizing keeps them searchable at a lower rank. Use ignore for files you never want like node_modules, and penalties for files you rarely need like tests and documentation.

Patterns match against the full file path, so /tests/ matches src/tests/auth.go but not tests.go. Check that your pattern string actually appears in the complete path, including leading and trailing slashes where appropriate.

Yes, bonus factors above 1.0 can push final scores past 1.0, and this is expected behavior. The score is a relative ranking signal, so only the ordering of results matters, not the absolute value.