mind v6.2.8 — exhaustive hardening audit

A full line-by-line audit of the code, tests, benchmarks, documentation, release metadata, and rendered presentation. Every behavioral fix was reproduced against v6.2.7 first.

Highlights:

• concurrent edges now merge per directional pair; reinforcement deltas and once-per-day edge decay are serialized under the graph lock
• atomic replacement uses unique O_EXCL temp files, completes short writes, fsyncs before rename, and fsyncs the directory on POSIX
• hostile live/on-disk state, timestamps, histories, metadata, and journal reads are repaired or bounded consistently
• why <id> scans the full journal for targeted provenance; link events belong to both endpoints; reads refuse symlinks
• exported memories are collapsed, guard-escaped, data-labeled, and paired with explicit privacy/untrusted-content guidance
• recall and working-memory tie-breaking are deterministic and usage-driven; CLI arity/path behavior is strict
• the stale competitor scorecard was replaced with a neutral scope comparison based on current official documentation

Verification:

• PR CI: 9/9 green; merged main CI: 9/9 green
• 213/213 unit tests
• full fuzz: 420/420
• multilingual: 24/24; discrimination: 12/12
• 180-day soak: 15/15 core survival, 0/256 stale junk, 7/8 hot core slots
• mutation sample: 47/120 killed (39%), with all survivors printed for triage
• 20/20 repeated concurrency stress rounds

mind.py sha256: b3e944ce9103bd5e353e09a12f434721cb274bc919326361039104889c6c5e03