feat: surface pro memory context

Author: logi-cmd

docs/PROJECT_STATE.md

@@ -1,6 +1,6 @@
 # Project State
 
-Last updated: 2026-04-14 (Pro cleanup event status visibility)
+Last updated: 2026-04-14 (Pro proof memory context visibility)
 
 ## Canonical build docs
 
@@ -18,7 +18,7 @@ Strategy, market, pricing, and older design docs still matter, but if there is a
 
 ## Current Version
 
-**v0.19.4** - OSS Pro visibility bundle release: `check --json` exposes installed Pro proof plans and proof recipe summaries at the top level, and `pro status` plus `check --review` render Pro proof-memory, proof memory health, cleanup history, proof recipes, learned proof, learned proof scoring, proof workbench next actions, stale recipe warnings, proof recipe next actions, proof closure summaries, reusable proof commands, reusable evidence paths, and prioritized proof-surface wording when available.
+**v0.19.4** - OSS Pro visibility bundle release: `check --json` exposes installed Pro proof plans, proof recipe summaries, and proof memory context at the top level, and `pro status` plus `check --review` render Pro proof-memory, proof memory health, cleanup history, proof memory context, proof recipes, learned proof, learned proof scoring, proof workbench next actions, stale recipe warnings, proof recipe next actions, proof closure summaries, reusable proof commands, reusable evidence paths, and prioritized proof-surface wording when available.
 
 ## Goal
 
@@ -63,6 +63,7 @@ Pivot from a CLI-only merge gate to an agent-native runtime with system-level au
 - Post-v0.19.4 draft update: Pro status and cleanup resolution now checks the target repo `node_modules` before falling back to the OSS package location, so global OSS installs can still activate a project-local Pro package.
 - Post-v0.19.4 draft update: `check --json` now adds a top-level `proofRecipe` summary when Pro provides learned proof evidence, including memory health penalty and warning fields. `check --review` also renders the Pro-provided memory health penalty and warning without moving scoring logic into OSS.
 - Post-v0.19.4 draft update: agent-guardrails pro status now renders Pro-provided cleanup event history, including cleanup event count, last cleanup time, recent cleanup summary, affected commands, and archive reasons.
+- Post-v0.19.4 draft update: `check --json` now adds a top-level `proofMemoryContext` summary when Pro explains recent proof-memory cleanup. `check --review` renders the same context, archived commands, cleanup reasons, and go-live impact without moving memory-change logic into OSS.
 
 ## Strategic Direction Update (2026-04-07)
 

lib/commands/check.js

@@ -194,6 +194,23 @@ function summarizeProProofRecipe(proofPlan = {}) {
   };
 }
 
+function summarizeProofMemoryContext(proofPlan = {}) {
+  const context = proofPlan.proofWorkbench?.memoryContext;
+  if (!context) {
+    return null;
+  }
+
+  return {
+    state: context.state || "unknown",
+    summary: context.summary || null,
+    appliedAt: context.appliedAt || null,
+    archivedCount: context.archivedCount ?? null,
+    archivedCommands: context.archivedCommands || [],
+    reasons: context.reasons || [],
+    goLiveImpact: context.goLiveImpact || null
+  };
+}
+
 function buildCheckResult({
   config,
   policy,
@@ -282,6 +299,7 @@ function buildCheckResult({
     goLiveDecision: review.goLiveDecision ?? null,
     proofPlan: review.proofPlan ?? null,
     proofRecipe: summarizeProProofRecipe(review.proofPlan),
+    proofMemoryContext: summarizeProofMemoryContext(review.proofPlan),
     preset: config.preset,
     diffSource: baseRef ? `git diff ${baseRef}...HEAD` : "working tree",
     baseRef,
@@ -608,6 +626,19 @@ function printProDeepSignals(review) {
     if (proofWorkbenchScore) {
       console.log(`- Proof workbench score: ${proofWorkbenchScore}`);
     }
+    const memoryContext = proofWorkbench.memoryContext;
+    if (memoryContext?.summary) {
+      console.log(`- Proof memory context: ${memoryContext.summary}`);
+      if ((memoryContext.archivedCommands ?? []).length > 0) {
+        console.log(`- Archived commands: ${memoryContext.archivedCommands.slice(0, 5).join(", ")}`);
+      }
+      if ((memoryContext.reasons ?? []).length > 0) {
+        console.log(`- Cleanup reasons: ${memoryContext.reasons.slice(0, 3).join(" | ")}`);
+      }
+      if (memoryContext.goLiveImpact) {
+        console.log(`- Memory impact: ${memoryContext.goLiveImpact}`);
+      }
+    }
   }
 
   const prioritizedSurface = formatPrioritizedProofSurface(review?.proofPlan);

tests/check.test.js

@@ -154,7 +154,14 @@ function withMockInstalledPro(callback) {
     "        nextAction: 'Run `npm test` first because this repo reused it 2x for this proof pattern (high confidence; reused 2x, fresh recipe).',",
     "        command: 'npm test',",
     "        confidenceLevel: 'high',",
-    "        recommendationScore: 95",
+    "        recommendationScore: 95,",
+    "        memoryContext: {",
+    "          state: 'recent_cleanup',",
+    "          summary: 'Memory changed because cleanup archived 1 stale or failed proof recipe. Affected command: npm test.',",
+    "          archivedCommands: ['npm test'],",
+    "          reasons: ['stale 200 days; failed 4x'],",
+    "          goLiveImpact: 'Current proof recommendations use active trusted proof memory and avoid stale or repeatedly failed recipes that were archived by cleanup.'",
+    "        }",
     "      },",
     "      impactSurfaces: [",
     "        { surface: 'validation', title: 'Validation proof', stepCount: 1, blockingCount: 1, memoryPressure: 3 }",
@@ -809,6 +816,10 @@ async function checkPrintsJsonWithInstalledPro() {
     assert.equal(parsed.proofRecipe.memoryHealthPenalty, 35);
     assert.match(parsed.proofRecipe.memoryHealthWarning, /unreliable/);
     assert.match(parsed.proofPlan.proofWorkbench.nextAction, /Run `npm test` first/);
+    assert.equal(parsed.proofMemoryContext.state, "recent_cleanup");
+    assert.match(parsed.proofMemoryContext.summary, /cleanup archived 1 stale or failed proof recipe/);
+    assert.deepEqual(parsed.proofMemoryContext.archivedCommands, ["npm test"]);
+    assert.match(parsed.proofMemoryContext.goLiveImpact, /active trusted proof memory/);
     assert.equal(parsed.proofPlan.impactSurfaces[0].surface, "validation");
     assert.ok(parsed.runtime.nextActions.some((item) => item.includes("[Pro] [HIGH]")));
     assert.deepEqual(parsed.review.contextQuality.suggestedFiles, ["src/auth/service.js", "tests/auth/service.test.js"]);
@@ -861,6 +872,10 @@ async function checkPrintsGoLiveVerdictWithInstalledPro() {
     assert.match(output, /exact command match; stale freshness penalty -15; memory health penalty -35; effective score 50/);
     assert.match(output, /Proof workbench: Run `npm test` first because this repo reused it 2x/);
     assert.match(output, /Proof workbench score: high confidence, recommendation 95/);
+    assert.match(output, /Proof memory context: Memory changed because cleanup archived 1 stale or failed proof recipe/);
+    assert.match(output, /Archived commands: npm test/);
+    assert.match(output, /Cleanup reasons: stale 200 days; failed 4x/);
+    assert.match(output, /Memory impact: Current proof recommendations use active trusted proof memory/);
     assert.match(output, /Prioritized proof surface: Validation proof \(1 blocking, memory pressure 3\)/);
   } finally {
     delete process.env.AGENT_GUARDRAILS_CHANGED_FILES;