feat(memory-fixer): add duplicate-detection phase; correct stale canonical pointer + reporting model (v2.2.0) #139

Merged

mumuni-bot merged 1 commits from fix/memory-fixer-duplicate-detection-20260926 into master

2026-09-27 02:16:45 +00:00

Author	SHA1	Message	Date
Mumuni	c460ef905c	feat(memory-fixer): add duplicate-detection phase; correct stale canonical pointer + reporting model (v2.2.0) PR Pipeline — Authorize → Validate → Review → Merge / auth (pull_request) Successful in 8s Details PR Pipeline — Authorize → Validate → Review → Merge / validate (pull_request) Successful in 2s Details PR Pipeline — Authorize → Validate → Review → Merge / lint (pull_request) Successful in 9s Details PR Pipeline — Authorize → Validate → Review → Merge / ai-review (pull_request) Successful in 4s Details PR Pipeline — Authorize → Validate → Review → Merge / gate (pull_request) Successful in 0s Details Level 1 gains phase 5, duplicate-node detection: runs memory_dup_detect.py (read-only) and reports clusters by verdict. - WRITER-DEFECT (run_family): one task creating a node per run -> writer fix, never merge (per-run nodes are the audit trail) - SAFE-MERGE: identical bodies, still needs an explicit Kwame decision - HUMAN-DECISION: same subject, bodies differ -> connect, never merge Replaces the naive '>70% title overlap' duplicate rule, which false-positives on distinct work: four client workflows (#357-#361) and two machines' migrations (#1792/#1793) score high on titles with bodies 0.1-0.3 apart. Also corrected in the same pass: - the 'canonical copy' pointer named /root/.hermes/contracts/memory-fixer-v3.md, which does not exist on kagentz (no /root access); the job's instruction set is inline in ~/.hermes/cron/jobs.json - 'reports to Kwame via this Zulip DM' described the pre-2026-09-21 model; the report is DROPped to the gate (comms_drop.py) and exit 0 means QUEUED, not sent - added a Checks line so a skipped phase 5 is visible in the report	2026-09-26 19:32:36 +00:00

Author

SHA1

Message

Date

Mumuni

c460ef905c

feat(memory-fixer): add duplicate-detection phase; correct stale canonical pointer + reporting model (v2.2.0)

PR Pipeline — Authorize → Validate → Review → Merge / auth (pull_request) Successful in 8s

Details

PR Pipeline — Authorize → Validate → Review → Merge / validate (pull_request) Successful in 2s

Details

PR Pipeline — Authorize → Validate → Review → Merge / lint (pull_request) Successful in 9s

Details

PR Pipeline — Authorize → Validate → Review → Merge / ai-review (pull_request) Successful in 4s

Details

PR Pipeline — Authorize → Validate → Review → Merge / gate (pull_request) Successful in 0s

Details

Level 1 gains phase 5, duplicate-node detection: runs
memory_dup_detect.py (read-only) and reports clusters by verdict.

- WRITER-DEFECT (run_family): one task creating a node per run -> writer
  fix, never merge (per-run nodes are the audit trail)
- SAFE-MERGE: identical bodies, still needs an explicit Kwame decision
- HUMAN-DECISION: same subject, bodies differ -> connect, never merge

Replaces the naive '>70% title overlap' duplicate rule, which false-positives
on distinct work: four client workflows (#357-#361) and two machines'
migrations (#1792/#1793) score high on titles with bodies 0.1-0.3 apart.

Also corrected in the same pass:
- the 'canonical copy' pointer named /root/.hermes/contracts/memory-fixer-v3.md,
  which does not exist on kagentz (no /root access); the job's instruction set is
  inline in ~/.hermes/cron/jobs.json
- 'reports to Kwame via this Zulip DM' described the pre-2026-09-21 model; the
  report is DROPped to the gate (comms_drop.py) and exit 0 means QUEUED, not sent
- added a Checks line so a skipped phase 5 is visible in the report

2026-09-26 19:32:36 +00:00