Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds structured ingest traceability to
atomicmemory-coreso benchmark and debugging workflows can inspect why each fact was stored, skipped, updated, or deleted.This change:
ingest_trace_idon ingest responses when tracing is enabledINGEST_TRACE_DIRTesting
dotenv -e .env.test -- pnpm exec tsc --noEmitdotenv -e .env.test -- pnpm test src/services/__tests__/ingest-trace-branches.test.ts src/services/__tests__/ingest-trace.test.ts src/__tests__/memory-route-config-override.test.ts src/services/__tests__/retrieval-trace.test.ts src/__tests__/config-partition.test.ts src/__tests__/route-validation.test.ts --reporter verbosedotenv -e .env.test -- npm testdotenv -e .env -- pnpm buildfallow(still reports pre-existing repo-wide duplication/complexity debt outside this PR; no auto-fixes available)Notes
performStoreVerbatimwrite-security behavior is intentionally not changed here; this PR is scoped to observability and trace-contract hardening.