fix/memory-ci-rebased
main
PR #16 (security & integration hardening) had an outdated CI workflow that conflicted with the unified pattern deployed to main.
Rebased PR #16 from main, resolved workflow conflict by keeping the unified pattern:
All security & integration improvements from original PR #16 are preserved:
Updated to match unified pattern (same as riotpiao.com, homelab-frontend, Poimen workflows):
## Code Changes (from original PR #16) Security & integration improvements: - Temporal filtering: semantic_retriever.rs (fact_invalid_at, event_time) - Answer validation: query_router.rs (6-signal multi-signal validation) - GRM context → facts: fact_extractor.rs + ingest_pipeline.rs - Speaker extraction first: entity_extractor.rs (Zep alignment) - Memorability gate: memorability_gate.rs - Community metrics: community_metrics.rs - Answer validator: answer_validator.rs ## CI Workflow (unified pattern from main) Standardized to match all repos: - test job: all branches + PRs (cargo test/check) - build-push job: main push only (docker build + push) - Install Node.js before checkout - Install docker only in build-push - Proper secrets handling (FORGEJO_REGISTRY_USER, TOKEN)
No dependencies set.
The note is not visible to the blocked user.
Problem
PR #16 (security & integration hardening) had an outdated CI workflow that conflicted with the unified pattern deployed to main.
Solution
Rebased PR #16 from main, resolved workflow conflict by keeping the unified pattern:
Code Changes
All security & integration improvements from original PR #16 are preserved:
CI Workflow
Updated to match unified pattern (same as riotpiao.com, homelab-frontend, Poimen workflows):
Pull request closed