Repository navigation
[ponytail] Remove unreachable adaptive chunking #117
Description
Activity
PR: #128
Tests: 137 files / 1798 tests before → 136 files / 1780 tests after. Removed: tests/semantic/adaptive-chunker.test.ts (18 cases, all on the deleted module). Build green both sides. Real-DB check: fixed 25/5 boundaries identical to the persisted chunk_metadata rows for 8/8 conversations; all 1,322 stored rows already had NULL avg_density.
Skipped (nothing to do): chunking-contract.test.ts has no adaptive-only cases (kept all five); ENGRAM_CHUNKING_STRATEGY was never in the env templates or ensureServiceEnvFile; no --chunking flag or chunkingStrategy pass-through existed in src/interfaces/cli or src/dream beyond smoke.ts; no ADR in decisions/ mentions adaptive chunking (plans/ got the superseded note instead).
- added a commit that references this issue
on Sep 21, 2026
Cut
Remove adaptive chunking. It is unreachable: no caller sets
chunkingStrategy: "adaptive", the daemon passes{tier: "auto"}, smoke and the CLI pass"fixed", andconfig.dream.chunkingStrategy(fromENGRAM_CHUNKING_STRATEGY) is loaded but never threaded intoextractFromConversation.Findings
src/semantic/adaptive-chunker.ts(~245 lines with the items below)cfg.chunkingStrategy === "adaptive"ternaries insrc/semantic/extractor.ts:541chunkingStrategyfromExtractionConfig,src/_core/types/index.ts:132andsrc/_core/config/index.ts:129ENGRAM_CHUNKING_STRATEGYfromCLAUDE.md,README.md,.envtemplates andensureServiceEnvFiletests/contracts/chunking-contract.test.tscases that only cover the adaptive pathVerification
npm run buildandnpm run test:rungreen before and after.engram extracton a real conversation still produces the same fixed chunks.