Keep the answer connected to the source.

Transfer the source map, held cases and removal procedure—not just access to the dashboard.

Assign an owner and a verification step to every important source update; automatic refresh is not proof that an answer changed.

Match refresh capability and review effort to actual source changes; do not buy a faster schedule without a reason.

Launch only the tested scope, with a source owner, a working non-chat route and a practical removal path.

Keep the article, navigation and keyboard path usable whether the chat interface is open or closed.

Test the open conversation, keyboard and source links—not just whether the launcher fits in a corner.

Record what changed, why it changed and which evidence was rechecked; do not overwrite the previous accepted state.

Retain source references, expected answer points and configuration notes outside the vendor before you need to move.

Continue only when the bounded reader job works and the review burden is sustainable; no-data and failure are different outcomes.