feat: rewrite replace chg and LLM entity augment chg and couple bugs#198
feat: rewrite replace chg and LLM entity augment chg and couple bugs#198asteier2026 wants to merge 4 commits into
Conversation
Greptile SummaryThis PR restructures the replacement step so direct identifiers are substituted programmatically before the LLM ever sees the text, removing the
Confidence Score: 5/5The refactoring is well-scoped and properly tested; all changed paths produce correct outputs for the happy path and the no-replace-entities passthrough. The pre-replace logic is correct and the longest-first sort prevents substring collisions. The warning logic across _get_replace_pairs and _apply_direct_replacements covers all missing-map and unmatched-entity cases without false positives. Schema changes are additive-relaxation only and are consistent with the stated motivation of preventing record loss. rewrite_generation.py — the double parse of COL_SENSITIVITY_DISPOSITION on the empty-pairs path is worth cleaning up, but it has no correctness impact. Important Files Changed
|
Co-authored-by: greptile-apps[bot] <165735046+greptile-apps[bot]@users.noreply.github.com>
Co-authored-by: greptile-apps[bot] <165735046+greptile-apps[bot]@users.noreply.github.com>
Changes include:
UPDATE: we will be closing this PR shortly. It was broken down into:
#205
This just deals with latent reason length
#206
This one just removes the validate on meaningUnitAspect
#207
This one is the enhanced augment for tricky entities
#208
This one is just making replace programmatic