pty-supervisor readiness marker

Trap: reading four expected marker lines and then using read to reject a fifth looks like exact-schema validation, but POSIX read returns failure for trailing bytes without a newline, so malformed extra data is accepted. Fix: explicitly prove EOF after the fourth newline, require fixed paths/order and unique records, and bind the root-owned marker to the complete reviewed source manifest plus every installed runtime artifact.