[maxmad64bis]

⚠️ base-red inherited: #15306

Summary

The Auto-Combo guide names the quality factor but doesn't say the tracker behind it lives in memory and empties on restart. The tracker keeps its state in a process cache, so after a restart each candidate reads as unseen and scores a neutral 0.5 until fresh observations land. The guide now states this right after the factor table, so a restart that resets scores to neutral reads as expected behavior instead of a fault.

Related Issues

• No linked issue — reproduced on the release base

Target Branch

• Base is the active release/v3.8.x branch (the highest open release/v*), not main
• New feature? From 3.8.55 on it is held with the v4-feature label for the v4 channel

Validation

• Change type: routing
• Focused tests and category gates from the golden path
• npm run lint
• Reconciled with the current active release base; focused checks rerun afterward
• Production-code changes include a new or updated automated test in this PR — docs only, no source file

Tests Added Or Updated

• tests/unit/auto-combo-quality-memory-cold-docs.test.ts — reads the routing guide and asserts it names the in-memory tracker, the cold restart, and the neutral 0.5, plus matches the release gate pattern.

Coverage Notes

N/A — docs only, no source file

Reviewer Notes

• Behavior: the 3 added lines sit after the factor table rather than inside it, since an insert inside the table breaks the table layout; the added lines name the quality tracker explicitly.