TON Bug Triage

Use this skill when the job is to prove something on a local tontester network, not just to launch validators.

Typical triggers:

• deploy a contract and trigger a bug with an internal message
• compare baseline and probing validator builds
• verify a crash, liveness failure, malformed-packet path, or compatibility claim
• collect maintainer-ready evidence for a local TON repro

The standard is: choose the smallest topology that answers the question, define the success condition before running, and collect enough evidence that the result is interpretable.

Working Model

Keep these paths distinct: