ktx/packages/cli/test/context/memory
Andrey Avtomonov a02fcab487 fix(ingest): honor storage.git.auto_commit and memory.auto_commit
Both documented flags were read only for status display; every ingest path
squash-committed to main unconditionally, so setting either to false was a
silent no-op (the reported symptom: 'Memory ingest (external_ingest): ...'
commits despite memory.auto_commit: false).

Gate the commit at the squash-merge onto main — the one point where ingest work
becomes a permanent commit (intermediate session-worktree commits must still
happen for the squash to collapse). When auto-commit is off, apply the squash to
main's working tree and leave it staged instead of committing, so the run is
never silently discarded:

- GitService.stageSquashMergeIntoMain: shares the merge core with
  squashMergeIntoMain but stops before committing and returns the staged tree
  SHA (a valid diff/read ref).
- memory.auto_commit gates MemoryAgentService (its DB writes are eager, so the
  staged files stay consistent); the commit-message job is skipped.
- storage.git.auto_commit gates IngestBundleRunner; the wiki index is reconciled
  from the staged tree via the existing syncFromCommit (git diff/show accept a
  write-tree ref), and SL reindex already reads from files.

Config descriptions now state precisely what each flag gates and the staged
semantics when false.
2026-06-09 12:44:58 +02:00
..
local-memory.test.ts test: split cli tests from source tree (#216) 2026-05-26 08:49:05 +02:00
memory-agent.service.ingest.test.ts fix(ingest): honor storage.git.auto_commit and memory.auto_commit 2026-06-09 12:44:58 +02:00
memory-agent.service.test.ts fix(ingest): honor storage.git.auto_commit and memory.auto_commit 2026-06-09 12:44:58 +02:00
memory-runs.test.ts test: split cli tests from source tree (#216) 2026-05-26 08:49:05 +02:00
memory-runtime-assets.test.ts test: split cli tests from source tree (#216) 2026-05-26 08:49:05 +02:00