Adopt Wellmanifest validation and ticket lifecycle for WUP #10

WUP currently adopts only the Wellmanifest local-CI publication policy in AGENTS.md. That partial adoption did not create a full protected test profile, an evidence attestation, or a lifecycle contract for Planfile tickets.

Acceptance criteria:

1. Adopt the applicable Wellmanifest/new-project governance and validation-attestation guidance at an immutable revision, with a repository-local record of scope and exclusions.
2. Bind each protected local-CI receipt to the exact PR head, base and computed merge result; distinguish declared, configured, deployed, verified and published evidence.
3. Define a Planfile ticket lifecycle that records provenance, deduplicates incidents, archives resolved noise and synchronizes the intended GitHub issue state.
4. Keep Wellmanifest tooling out of WUP runtime and test dependencies; standards are process configuration and validation, not production imports.
5. Demonstrate the process with a canary WUP change and document maintenance ownership.

WUP currently adopts only the Wellmanifest local-CI publication policy in AGENTS.md. That partial adoption did not create a full protected test profile, an evidence attestation, or a lifecycle contract for Planfile tickets.

Acceptance criteria:

1. Adopt the applicable Wellmanifest/new-project governance and validation-attestation guidance at an immutable revision, with a repository-local record of scope and exclusions.
2. Bind each protected local-CI receipt to the exact PR head, base and computed merge result; distinguish declared, configured, deployed, verified and published evidence.
3. Define a Planfile ticket lifecycle that records provenance, deduplicates incidents, archives resolved noise and synchronizes the intended GitHub issue state.
4. Keep Wellmanifest tooling out of WUP runtime and test dependencies; standards are process configuration and validation, not production imports.
5. Demonstrate the process with a canary WUP change and document maintenance ownership.