@mnemonik/shared 1.0.0 → 5.75.3

package/src/usageGuide.ts

@@ -4,14 +4,15 @@
  * This is the SINGLE SOURCE OF TRUTH for the usage guide.
  * Shared usage guide content imported by the server.
  *
- * Version: 2.80
- * Updated: 2026-02-20 - Aligned with instructions/rules/skill v2.80
+ * Version: 2.82
+ * Updated: 2026-05-27 - Doc-truth-contract-rebuild: teach authority-backed
+ *          truth findings and keep legacy coupling drift diagnostic only.
  *
  * This guide focuses on HOW to use Mnemonik effectively, not WHAT tools exist.
  * Tool schemas already tell agents what's available - they need the workflow.
  */
 
-export const USAGE_GUIDE = `# Mnemonik Workflow Guide (v2.80)
+export const USAGE_GUIDE = `# Mnemonik Workflow Guide (v2.82)
 
 ## Workflow
 
@@ -28,7 +29,7 @@ session_bootstrap → memory_search → file_context → [work] → memory_add
 ### Before editing files
 - file_context: fetch memories for the file — call for EVERY file you edit
 - memory_search: second search scoped to file/module if needed
-- docs(action: 'links'): check doc couplings for the file
+- mnemonik.docs({ action: 'links' }): check doc couplings for the file
 
 ### During implementation
 - memory_get: retrieve specific memory by id
@@ -40,8 +41,7 @@ session_bootstrap → memory_search → file_context → [work] → memory_add
 - memory_add: save decisions, outcomes, patterns, bug root causes
 - memory_state: reinforce (memory helped), supersede (replace outdated), deprecate, penalize, dispute
 - tasks: mark tasks in progress or complete
-- docs(action: 'drift'): check for stale documentation after code changes
-- docs(action: 'resolve'): mark stale docs as fixed after updating them
+- mnemonik.docs({ action: 'status' }): view doc-truth health (legacy coupling counts are diagnostic only — do not act on them as drift)
 
 ### Diagnostics
 - doctor: when tool calls fail or behavior is inconsistent
@@ -67,7 +67,7 @@ Never tell the user significant work is done without calling memory_add first in
 - Long sessions: re-run memory_search after switching topics
 - Conflicting info: use memory_state to supersede/dispute
 - High-impact changes: save memory immediately after verification
-- When file_context returns linkedDocs with driftStatus 'stale': update docs then docs(action: 'resolve')
+- Act on docTruthFindings/_docDrift only when the finding has authority, observed mismatch, and agentAction='update_doc'; linkedDocs and stale-coupling counts are legacy diagnostics
 
 ## Anti-fade (every ~10 tool calls)