Distinguish memory baseline regressions from growth in support guidance

The latest memory report is about a higher steady baseline, not a leak. Keep steady regressions actionable, separate unlike process ages and CPU savings from RSS recovery, and preserve existing evidence without another restart, downgrade or profile. Keep the shipped guides, optional intake and regression controls aligned.

Contract-Neutral: Clarifies interpretation of existing memory reports and documentation only; no runtime, API, route, collection recipe, label synchronizer or subsystem contract changes.
Change-source: pulse-maintainer

.github/scripts/issue-version-triage.test.cjs

@@ -627,6 +627,17 @@ for (const [name, field] of [
     assert.match(attachment, /summarise only relevant counters after local review/);
   });
 
+  test(`baseline memory regressions need no continuing growth or restart: ${name}`, () => {
+    const attachment = evidenceField();
+    assert.match(attachment, /higher steady baseline from growth during one uninterrupted run/);
+    assert.match(attachment, /worth reporting even if usage stays flat/);
+    assert.match(attachment, /already available versions, uptime, workload and enabled collectors\/features/);
+    assert.match(attachment, /not proof of recovery compared with a days-old run/);
+    assert.match(attachment, /Unknown context is valid/);
+    assert.match(attachment, /do not restart, downgrade or change features to create a comparison/);
+    assert.doesNotMatch(attachment, /required: true|render:/);
+  });
+
   test(`guest memory comparisons retain optional target and sample context: ${name}`, () => {
     const attachment = evidenceField();
     assert.match(attachment, /For CPU, memory or disk-write reports about Pulse itself/);