“In a pursue run, don't fight the guard.”

During an autonomous campaign, the blueprint guard blocked a Write to the protected blueprints directory — the campaign skill hadn't armed the lock through the expected channel. The blueprint itself was fully process-derived; only the path was contested.

The deviation went into the campaign artifact record, the lesson went into memory for all future runs, and the actual root cause — a session-ID asymmetry between the arming hook and the guard — was diagnosed and fixed in the plugin release shortly after.