nulnul harness 1.7.0

nulnul harness 1.7.0

This release candidate adds opt-in Personal Evolution without adding raw project memory. A project-verified mechanism can become a personal adaptation only after a frozen source identity, representative transfer checks, an incompatible-shape skip, and an independent Personal Gate. A new project must still pass a compatibility and completion check before reuse.

The first candidate reuses the already accepted checkpoint-freshness mechanism. Fresh Node and Make shapes passed, a one-shot shape skipped, and a fresh data-CLI project discovered and verified the adaptation from an isolated user-selected temporary home. The no-registry baseline also completed its task but did not discover an approved adaptation; no token, runtime, or universal task-quality win is claimed.

The registry is a user-selected existing local directory and stores only generalized bounded evidence, activation conditions, contraindications, provenance, permissions, and revocation state. Missing home, private data, self-approval, hidden failed transfer, false activation, duplicate identity, conflict, permission expansion, and stale or revoked adaptations fail closed. Publication is not complete until exact-version public 1.7.0 adoption evidence passes the final Release Gate.