# Published multiselect contribution: integration-owner audit

This is an **offline evidence and source review**, not combined-build or native acceptance.
Delivery is `7e348d967d1787c052a145b7448636613a6a7054`; final product source is
`f6a6010baed9e6164a1fcc7ecd58256a562827d7`, following `12a7352ddef5f69a144ead8219a50916233d63a9`
above State/attachment base `b8685416f56e53e30bd11ecf93a54cea10ac8458`.
The reviewed integration target is `f82e29d6b8ed2b5fd23ac806675d3eafe851d104`.

The parent fetched the named delivery, read all three supplied verifiers, exported the
exact committed package bytes, and ran those verifiers with Python 3 on Windows.
All three exited zero. [Raw result and exported-file pins](parent-result.json) and
the three `parent-verifier-*.log` files retain the actual outputs. Paths in that
result are historical machine-local labels, not handoff dependencies.

- Checks package: 19 closed historical runs, 134 logical files, 114 stored members,
  and nine source-capsule pairs. Five historical nonzero runs remain failures.
- Native package: two historical closed runs, 393 members, 27 and 24 captures,
  nine positive saved-state checks per run, and exact three-group source history.
- Source identity: every captured input and the complete filtered inventory match
  the named Git trees for desktop-4 (`12a7352`, 729 inputs) and desktop-5
  (`f6a6010`, 729 inputs).

These checks establish package consistency and committed-source identity. They do
not rerun a compiler, archived helper, application evaluator, or GUI; they do not
independently authenticate historical gestures. The parent also read the delivery's
verification report. Its final desktop result is reported as 1,257 passed / zero
failed / six ignored, distinct from the earlier layout-defective build. Native
movement uses an inferred bounded common delta, and contextual Add is not native
Shift-click evidence. Those limitations remain applicable.

The [independent source/composition review](../../reviews/multiselect-composition-20260923.md)
finds no established production blocker in the scoped contribution. Integration
must add `layout: None` to the new example's Diagram literal, retain the final fixed
selection strip and the target's Scenario admission, Text writer, Properties actions,
and saved-Scenario exclusions, then verify the combined behavior. The preview-cache
ordering observation is a targeted regression requirement, not a demonstrated
native bug. Full issue 29 remains open for other diagram families and aggregate
model deletion; this audit does not change ownership or acceptance.

Reproduce the upstream audits from a checkout of the delivery containing its ancestor
commits (the scripts themselves are versioned at that exact delivery):

```text
python -B harness/experiments/multiselect-20260923/checks/verify.py
python -B harness/experiments/multiselect-20260923/native/verify.py
python -B harness/experiments/multiselect-20260923/source/verify.py --repo . --checks harness/experiments/multiselect-20260923/checks
```

Upstream [verification report](http://217.177.34.108:3000/sorokin.oleg.edu/ARCADIA-Studio/src/commit/7e348d967d1787c052a145b7448636613a6a7054/harness/multiselect-saved-view-20260923.md)
contains the original commands, scope, historical failures, native observations,
and linked packages. The parent performed this audit without changing the active
combined or private-analysis source under test. Linux remains user-deferred.