[anilkreddy]

Cleanup cannot currently emit a valid notification because the existing contract has no cleanup event. Add ccv2.build-cleanup.completed, its data type, schema validation, public factory, and focused tests within the existing notification-contract package. Existing event semantics, package structure, OAuth, and transport remain unchanged.

This is an unpublished compatibility candidate for the CCv2 Build Cleanup action. No package version or registry lockfile was changed. Publication, version selection, and consumer pin updates require separate authorization; keep dependent action changes in draft until a supported package is available.

Validation against source base 9aeded72cf1faaf4441a24ff8c9510daab06e2ca:

• Prettier and ESLint passed for changed package files; full TypeScript checking passed.
• All 277 action-kit tests passed, including existing event fixtures and cleanup validation cases.
• The exact-source packed contract passed cleanup adapter and existing notify-provider integration tests.
• Candidate tarball integrity: sha512-T+wt6X75QSHDpxHJDxqH797K1jO+YFKAbMLymqJ1rs78R0mWR8RT1bn53mwXviqAu7eO51YWMxm6CH6eW8iPtw==.

Commit: 05eb3240a036dd4afaf191921aa7bbb2ba4bf168. No publication, release, tag, merge, deployment, or real SAP deletion was performed.

Companion draft PRs

• Cleanup action
• Notify rendering
• Sandbox fixtures and races

These are coordinated draft changes. No merge, publication, tagging, deployment, production enablement, or real SAP deletion is authorized by this review. Keep the dependency-publication and SAP eligibility gates explicit.

Hosted validation snapshot — 2026-11-14

PASS: quality and all three platform jobs, analysis workflow, and CodeQL checks passed on the pushed head. This does not authorize publishing the candidate package. The cleanup companion's audit/CodeQL checks now pass after targeted fixes (validated run). SAP eligibility remains unverified, and Notify's registry-only build remains blocked until a separately authorized compatible publication/pin.