# SCUM Durable Run Schema Probe Evidence — 2026-08-12

## Scope

- Evidence kind: product-path durable Run job result accepted by Platform.
- Target server: `枣庄服务器` via the active authenticated Run binding `server-run-server-scum-1785923898033`.
- Boundary: Platform/plugin/browser did not download or parse `SCUM.db`; the database probe was produced by Run as a typed, redacted `sqlite.schema-probe` envelope and then persisted by Platform.
- Redaction: this artifact intentionally omits host paths, database paths, credentials, sockets, raw SQL, raw rows, raw XML, raw player names, and network material.

## External Run Deployment Evidence

- Independent Run repository: `git@git.npc0.com:admin343/run.git`.
- Tested Run fix: commit `8fe6f9b` (`Fix SQLite probe data target mapping`).
- Run verification performed in the independent Run repository: focused data-target/runtime tests and `go test ./...` passed before deployment.
- Installed distribution on `枣庄服务器`: `run-dist-server-scum-1785923898033-windows-amd64-1-zao-zhuang-data-target-run-fix-2026081-6988495348508259730`.
- Distribution checksum: `sha256:a5ac9fe31ed0e0f595e70e3d3322f44aa81bd165183530e4be6939aff81c3016`.
- Runtime capability evidence: the active endpoint advertises `remote.run.db.sqlite.probe` and `remote.run.db.sqlite.query` after installation.

## Platform Acceptance Evidence

- Durable job: `job-remote-adapter-server-scum-1785923898033-7249327407638289501`.
- Platform terminal state: `succeeded` with progress `100` and message `SQLite schema probe completed`.
- Terminal time: `2026-08-12T12:29:24.857542Z`.
- Probe observed time: `2026-08-12T12:17:39.0088015Z`.
- Probe status: `succeeded`.
- Source fingerprint: `sha256:d8f3e2f5e9c8241f55b931008309a7ab5f241118a82cbd3620ddedf233e74c13`.
- Schema fingerprint: `sha256:ebd477d6c6ead9c34c41169af489236d762a76186d45dedd753d50f1b81e26f0`.
- Result digest: `sha256:ef13678df4add731c758bba157627dc8af80138a69476facd81bbe354c31d7f1`.
- Schema object count: `161`.
- Safe error: empty / not retryable.

## Platform Decode Fix

- Run emits `sourceFingerprint` in successful SQLite schema-probe results.
- Platform DTO/domain/validator handling now accepts and persists `sourceFingerprint` only when it is a safe digest/fingerprint.
- Validator coverage rejects raw path-shaped values such as a host database path and permits bounded generic Run `data_target_*` safe error codes without allowing path material.

## Server-Management SSH Verification

- The personal server-management MCP inventory found `枣庄服务器` with device id `FyBDIohqPhRx7Cia`.
- `test_connection` succeeded for `枣庄服务器`.
- `ssh_exec` was used for bounded, read-only PowerShell status checks only; no SCUM database query or file copy was performed.
- Remote process summary at `2026-08-12T14:13:56.4937358Z`: `SCUMServer.exe` process count `1`.
- Run journal summary: scanned `1` job journal, target job active count `0`, target pending result count `0`, total active count `0`, total pending count `1`.
- Interpretation: the durable schema-probe job is not stuck in the remote Run active queue or pending-results spool after Platform accepted the typed result. The remaining unrelated pending result, if any, is outside this evidence item.

## Resulting Gates

- This proves the product acceptance path for schema probing: Platform durable job → authenticated active Run binding → Run-side typed/redacted SQLite schema-probe envelope → Platform validation and persistence.
- This does not prove player/squad/vehicle/flag/position query adapter compatibility, rank meanings, currency semantics, map transform, gift aliases/transports, or `855` named-attribute mapping.
- Database-backed player/squad/map/gift/write capabilities remain disabled until the versioned adapters and query/mutation contracts in later task groups are implemented and matched against this evidence matrix.