Testing BGS Modpack Batches (judgment skill)

Testing BGS Modpack Batches (judgment skill)

This skill answers one question: "It's installed -- how do I PROACTIVELY verify this batch before declaring the batch good?"

BB84's source material is thin here. That is part of the skill's operating doctrine: do not manufacture a giant universal QA checklist. Test the batch's intended in-game impact, preserve save hygiene, query KB for game-specific commands/routes, and mark [GAP — needs user input] when the substrate is silent.

The Iron Law

+------------------------------------------------------------------------------------------------+
| A batch is not accepted because the game reached the main menu. It is accepted only after the   |
| batch's intended in-game effect is observed in its target context, with no immediate local       |
| breakage, and without baking unverified state into the user's main save.                         |
+------------------------------------------------------------------------------------------------+

Route gate (one primary skill per intent)

Use this skill when the user has already installed a batch and wants a proactive post-install verification pass: what to inspect, what commands/routes to use, what counts as enough evidence to move to the next batch.

Do not use this skill as the primary skill for adjacent intents:

Terminal handoff: if proactive testing finds a failure signal, stop calling it "testing" and hand off to diagnosing-bgs-problems. A failed verification pass is not an invitation to improvise a fix inside this skill.

When to use / When NOT

Use when:

• A small batch was installed and the user asks "what should I test before moving on?"
• The user asks "is it stable?", "post-install check", "验证安装", or "测试整合包".
• You need to verify visible new content, expected local mechanics, or immediate CTD/performance risk in the batch's target context.
• You need a save-hygiene reminder before the user commits playthrough state.