DevTool Import Evidence

Current Web/WebGL playable work may continue without developer-tool import evidence. Final S5 import certification and S8 Go/No-Go require both WeChat and Douyin generated projects to be imported by their developer tools before the project can claim mini-game import verification.

Required final import targets:

wechat_minigame
douyin_minigame

kuaishou_minigame remains static-gate plus risk-note unless exact official docs, source, or import evidence is available.

Passing evidence is written to docs/evidence/devtool-import/{target}-{gameVersionId}.json.

For simulation-fixture-v1, final certification requires both:

docs/evidence/devtool-import/wechat_minigame-simulation-fixture-v1.json
docs/evidence/devtool-import/douyin_minigame-simulation-fixture-v1.json

Passing evidence must include target, gameVersionId, referencePlatformReason, result="passed", toolName, toolVersion, importedProjectPath, projectChecksum, logPath, and createdAt. screenshotPath is optional, but if present it must point to an existing file.

importedProjectPath and logPath must exist when evidence is recorded. projectChecksum must match the stable hash of the imported project directory contents.

result="blocked" or result="failed" is not passing evidence. Use DevToolImportBlocker.result="blocked" when the tool is unavailable, and DevToolImportBlocker.result="failed" when import runs but rejects the project. A blocker explains S5 import-certification No-Go and keeps the retry path auditable, but it never satisfies DevToolImportEvidence.

ChannelReadinessNote is only for later channel preparation gaps. It cannot replace DevToolImportEvidence, DevToolImportBlocker, or channel review.