DEADBYTE MCP V0.4.7 RUNTIME WORKER MANIFEST ATTESTATION

Accepted parent: V0.4.6 target evidence proves three operations through two fixed package-local worker binaries over both direct and MCP contained execution paths.

V0.4.7 adds a build-generated bin/WORKER-REGISTRY.txt manifest that binds:
- schema/version/policy
- operation -> worker_id mapping
- worker_id -> executable basename mapping
- launcher SHA-256
- transform worker SHA-256
- reverse worker SHA-256

The Node control plane verifies the entire manifest and all binaries before spawn.
The native launcher independently parses the manifest, hashes launcher/workers using BCrypt SHA-256, and verifies the selected profile copy before CreateProcessW.
The signed execution receipt binds worker_manifest_sha256 and worker_source_sha256.
The independent verifier re-opens the manifest and current runtime binaries and verifies those bindings before semantic verification succeeds.

No arbitrary executable path, argv, shell, command_run, user environment, or host workspace mount is exposed.
