[p-diogo]

Re-created from #669 on 2026-10-31. GitHub Support is removing the pull-request refs of every PR opened before the 2026-10-25 history rewrite (private-data purge), which would leave #669 without a diff. Branch and content are unchanged; the earlier discussion stays on #669.

What

PRD-04 DEP-3 (F2), Part A: core only (refs internal #537). This adds the new module rust/totalreclaw-core/src/dedup_context.rs. build_dedup_context(topical, pinned, recent, cap) -> String renders the "Existing memories" block the extraction prompt receives:

• the header is byte-identical to today's inline block in Hermes, the OpenClaw plugin and MCP;
• one [ID: <fact id>] <text> line per memory, pinned first, then topical, then recent;
• every line-break character in an id or text (the str.splitlines set: LF, CR, VT, FF, FS/GS/RS, NEL, U+2028, U+2029) becomes one space, so a stored fact cannot forge an extra [ID: …] line;
• duplicate fact ids keep the first occurrence;
• at most cap lines (default 30); "" when nothing survives.

It only formats. Choosing what goes in each section (all pins, top-20 topical, 10 newest) is the caller's job, in Part B.

Bindings: WASM buildDedupContext(topicalJson, pinnedJson, recentJson, cap?), PyO3 build_dedup_context(topical_json, pinned_json, recent_json, cap=30) (JSON in, String out). WASM throws on a negative, fractional, NaN or infinite cap instead of coercing it.

Parity

tests/parity/fixtures/dedup-context-v1.json holds 16 cases. generate-dedup-context-v1.py writes it from an independent Python reference implementation. Three suites check it:

• Rust: cargo test dedup_context (18 tests)
• WASM: tests/parity/dedup-context-parity.test.ts (new step in CI job cross-language-parity)
• PyO3: python/tests/test_dedup_context_parity.py (CI job python-tests)

Spec deviation

Enclave spec §4.6 sketches Vec<Claim>. The v0 Claim has no id, and each line must carry the on-chain fact id that the LLM echoes back as existingFactId. The element type is therefore DedupContextItem { id, text }.

Not in this PR

• No version bump. The coordinator opens the core 2.7.0 line.
• Part B (the Hermes adapter in agent/lifecycle.py, plus fetchers in operations.py / client.py) is not written yet. It needs a published core with build_dedup_context.
• No client calls the new function yet, so merging this changes no runtime behaviour.

Review log

• 2026-11-03: merged main (core 2.6.1, Python 2.5.3, fix(hermes): fast pre-turn recall; keep provider on after pairing #703, fix(python): end Harrier inputs with <eos> so semantic recall works #708). Conflicts only in ci.yml and the core CHANGELOG; both sides kept.
• 2026-11-03: addressed the feat(core): topical dedup context — build_dedup_context + WASM/PyO3 bindings (PRD-04 DEP-3, Part A) #669 review follow-ups (caller contract in the module doc, negative cap from JS, PyO3 non-array ValueError test, generator strip vs Rust trim) and widened line collapsing to Unicode line breaks. The 14 original vectors are unchanged; two cases were added.

🤖 Generated with Claude Code