# Nested lifecycle / typed activation source union

Source: `f6595ebf66e88ec42c37b5c1a3c014f5e52cb32d`.
Base: `d61f1f38779ab70a77efcde523ae31c432aefcfd`.

- [Source handoff](source-handoff.md)
- [Independent source review](independent-review.md)
- [Exact committed source snapshot](source/crates/oa-desktop/src/behavior.rs)
- [Full-index binary Git patch](patches/d61f1f3-to-f6595eb.patch)
- [Payload manifest](manifest.json)
- [Archive/verification helper](tools/archive-lifecycle-union-f6595eb.py)

The six source files are extracted from committed Git blobs; they are evidence,
not an additional production tree. Notes retain their original bytes, including
historical local paths and source-scoped statements. The manifest lists portable
archive-relative paths plus original source provenance. It does not claim tests,
native acceptance, import, or publication succeeded. Subsequent gates remain
separate source-identified records owned by the integration owner.

From repository root, run the helper with `verify` to compare payload bytes,
manifest metadata, source blobs and regenerated patch. After owner-controlled
staging, run `verify-index` to additionally compare every payload and manifest
with Git index blobs. Neither mode stages or rewrites files. If Git attributes
normalize archived bytes, index verification fails; the owner must resolve that
explicitly. No patch is applied by this helper.