# Independent transfer integration audit — 2026-09-11

Codex-ytr83r /root/integration_audit. Starting checkout: `ff615d0`, clean. Scope is read-only source/history review plus this report; root owns Git mutations, production edits, Cargo and native input. Read local AGENTS.md, issue #1 through #146, the empty open-PR inventory, and Wiki Authoring20260911 / BehaviorAuthoring20260911. Ownership recorded in issue #1 comment #148.

## Published transfer inventory

| Snapshot | Transport branch and file | Required object | Decoded bytes / SHA256 |
| --- | --- | --- | --- |
| `3978bbe23c3d50563ad87fea5552de3d52f39d6b` | `codex/integration-transfer-20260910`, `harness/transfers/integration-3978bbe.bundle.b64` | `1797516f460ce27f7bc92e50ea2478ec51dd49b9` | 191436 / `15221FBAF45E226BAD4FDEDF241137AE2CCD36D246737F6B8D69818AB8F3629F` |
| `c6d296a7e22c8f126834a1e217b88551634dd5cf` | `codex/behavior-transfer-20260910`, `harness/transfers/behavior-c6d296a.bundle.b64` | `1797516f460ce27f7bc92e50ea2478ec51dd49b9` | 334830 / `526A80E2D32ED0E57A7B2372B5F02D4652E8751DFEBA81953C4F045225D6AACB` |
| `4bb4aaf3dc47b9738625b4d3f23ef8c74f286395` | `codex/integration-transfer-20260911`, `harness/transfers/creation-4bb4aaf.bundle.b64` | `3978bbe23c3d50563ad87fea5552de3d52f39d6b` | 105022 / `0DEFAE91A56430076C432758F923BC0675911DA9FA7588C9961FF15F47EAEBF6` |

These values are publisher/readback evidence from issue comments #97, #128, #136 and the Wiki; root performs independent local decoding/object verification. Transport branches contain delivery files and must not be merged as source histories.

The behavior snapshot already integrates equivalents of prior palette, behavior, packaging and scenario-workspace source. Issue #107 explicitly maps packaging `b98f135` to `6d2b961` and workspace `3978bbe` to `865cd55`; its Sensor correction was separately reproduced. Creation depends on original `3978bbe` for object transport, but its one coherent final creation commit can be applied over the behavior source after resolving actual divergent hunks. Importing a prerequisite bundle does not mean applying its changes twice.

## Preservation requirements

- Keep the starting user goal at `ff615d0` intact while separately retaining any newer explicit textual-notation additions from transferred history for root reconciliation. Neither host's release ledger may silently narrow the user goal.
- Preserve both hosts' dated ledger archives and attributed evidence. Current ledgers need a local-host synthesis; replacing them wholesale would present another host's executable/native results as local acceptance.
- Combine all `.gitattributes` rules protecting exact source fixtures, notices and evidence. Published packaging checks rely on all 25 notice byte hashes; newline normalization can invalidate otherwise unchanged evidence.
- Retain equivalent Sensor key `(document, scenario)` and both hosts' useful mounted regression coverage. A same-owner UUID after document replacement must still trigger viewport measurement.
- Creation must preserve exact prepared-command correlation before execution, success-only selection, explicit guards against applying another raw editor, root-owned SA checkpoint restoration and ordinary modal-priority Escape.
- Preserve B1 ordered-path projection and atomic conversion, B2 clicked root/operand slot capture, B3 exact initiating-use return/presentation restoration, and unpublished B4 ownership boundaries.

## Snapshot omissions and already-addressed defects

Reported source fixes already delivered in the transfer lineage include palette compile/inline-name rejection repairs, continuous editable ordered process paths, clicked non-message scenario insertion, caller-return/presentation restoration, same-size owner/document Sensor invalidation, local named Process/Scenario/State-machine creation, and strict packaging notice retention. These should be integrated and verified, not reimplemented independently.

`4bb4aaf` contains the **original v1 creation oracle**. Issue #132 later falsifies its disk-equals-reachable assumption: safe Save preserves known detached source files after Undo. The corrected v2 checker uses an explicit pre-Undo origin and accepts only its exact retained files; source SHA256 `51AB2FFA1826DD949B79F3A9690042A2F9E38DAF9ED91517CADE3861482117BA`. That correction and later native 13-command/recovery 19-check reports were still uncommitted in comments #132/#140/#142. Do not run or cite the transferred v1 as valid Undo acceptance.

Further work described after the published snapshots remains external/unpublished: source7 constructor-default documentation and its 54 accepted/12 refusal probes; staged prerequisite creation and semantic empty-state actions; source-only CLI; production contextual reference chooser; refined analysis-baseline and library compatibility contracts. Readback of a Wiki summary does not place these implementations or exact evidence files in this checkout.

B4 lifecycle projection is still an isolated test-only experiment in the behavior snapshot. Its integration must resolve visible lifetime extents versus insertion bounds, branch-local activation clipping at Delete, full lane geometry for incomplete lifelines, and self-message endpoint alignment (issue #114). Existing pure projection tests do not establish native lifecycle rendering.

Published desktop results are host/revision scoped: behavior `80cf197` 642/642 and creation candidate 653/653, followed by affected history63, strict Clippy and matching GUI. They do not certify the combined local source. Current Linux runtime, matching optimized packages and full cross-disciplinary release acceptance remain open.

## Local source audit status

Root imported the three exact objects under `codex/import-integration-3978bbe`, `codex/import-creation-4bb4aaf`, and `codex/import-behavior-c6d296a`, independently verifying bytes and bundle prerequisites. The creation hash in one earlier handoff/Wiki omitted an `F`; the correct verified value above contains `C9961FF15`.

Read-only Git inspection confirms the coherent source order: merge/import the full `c6d296a` source history onto `ff615d0` while reconciling PROJECT_GOAL, then cherry-pick **only `4bb4aaf`**. Do not replay original `3978bbe` or `d114a27` over their already integrated equivalents. Behavior ancestry after the original authoring line is `aed40d7 → eb5161b → 4ecad78 → 8547b85 → aa40345 → 632c8fe → ef1a447 → 65a1fef → 6d2b961 → 865cd55 → 80cf197 → c6d296a`. Original creation ancestry after its prior integration is `3978bbe → d114a27 → 4bb4aaf`.

Compared with `3978bbe`, behavior's production deltas are limited to the keyed Sensor, revised behavior/history guide, and semantic-schema generator's descriptor-use docstring. Additional Rust is the cfg(test) lifecycle module/declaration and Sensor regression. There are no incoming core changes from `ff615d0` to behavior `c6d296a`. Creation's source delta adds the planned creation/App/recovery/guide wiring and equivalent history-fields lint cleanup; source-semantic overlap is narrow.

The equivalent `d114a27` Sensor regression is richer than `80cf197`: it compares measured actual scroll geometry and asserts accepted Arc/no Undo changes across owner and document navigation. Root may preserve that richer test independently; the production Sensor differs only by a comment. Creation's guide hunk changes the first scenario instruction, adjacent to behavior's later clicked-tool instructions, so preserve both New creation and clicked root/operand/Back instructions plus advanced stored-history guidance.

Behavior's tree lacks five useful older other-host reports present at `3978bbe`: `release-behavior-gap-audit-20260910.md`, `release-integrated-gates-20260910.md`, `release-otherhost-checkpoint-20260910.md`, `release-readiness-audit-20260910.md`, and `release-wsl-readiness-20260910.md`. Creation modifies the integrated-gates report; root should preserve that incoming content and retain the other four if building a complete evidence union. Their historical findings retain original revision scope.

Git diff independently confirms transferred goal adds a four-bullet Textual notation requirement section (visual clutter, cognitive load, human/AI editability, complete text-only small/large models), beyond formatting changes. Root confirms the latest user's supplied goal includes that section, so final reconciliation must retain it.

Root merged behavior at `c81e285`; creation cherry-pick had no production conflicts. Root expanded this worker's ownership to the seven conflicted documentation/attribute files, current ledger synthesis, exact archives and missing other-host reports. These edits are complete without staging or other Git mutation by this worker.

Current `PLAN.md`, `STATE.md` and `TASK_LEDGER.md` describe Codex-ytr83r's unbuilt/unaccepted combined source, the full user goal, attributed prior-host results, external active owners and concrete next gates. Thirteen exact source blobs preserve the three ledgers from ff/c6/4bb plus both original palette/workspace reports under `history/2026-09-11-ytr83r-integration/`; original older archives remain. Four missing3978 reports are restored. Current palette/workspace/integrated-gates retain4bb content with an explicit earlier-host attribution note. `.gitattributes` unions both hosts' rules and protects the new archive.

Read-only final source comparison finds no lost semantics: against4bb, differences are the intended c6 test-only lifecycle declaration/module, equivalent Sensor/test variant, improved clicked-tool/operand/caller-return and stored-history guide instructions, and semantic-schema descriptor docstring. Againstc6, modified source is confined to planned creation/App/checkpoint/history-lint/guide paths. All creation implementation and App tests remain exactly4bb; the existing c6 Sensor owner/document regression remains. Auto-merged guide correctly retains both New scenario creation and the newer clicked-authoring instructions.

No build, test or native acceptance is claimed by this report. Root owns staging, commit and fresh combined-source verification.