Repository navigation
Fix paired-field Cells measurement identity (#314) - #317
Merged
Merged
Conversation
…red-field journey
trissim
marked this pull request as ready for review
October 1, 2026 00:41
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Closes #314 and #322. Parent owns integration. Normally merged current main8e478cb21; the existing source-image-set identity owner now distinguishes fixed paired-field coordinates from selected plane membership. Existing NamedSourceBinding.component_values remains assignment/selector authority. Consumers/exporters do not gain CSV joins, copied metadata, module switches or another registry.
The actual installed journey exposed #322: ConvertImageToObjects called image.copy on a metadata-bearing runtime carrier. Its existing NumPy conversion owner now supplies the owned numeric working copy through np.asarray(image).copy(); original main flow, label-builder source, pixels, provenance and declared spacing remain intact. No forwarding shim or guard weakening.
Current evidence
Preserved failures and limits
The first installed predecessor failed at image.copy and is retained. The repaired copy then exposed a parent-authored control mistake: KnownCells inherited previous DNA-only main flow instead of selecting original Actin main flow. Reflected schema and existing importer confirm the fix is the existing lazy input_source=PIPELINE_START declaration, not a production fallback. That failure and output remain; final run uses a separate output directory with unchanged algorithms/settings.
A receipt helper initially hit its PTY canonical input-size limit before dispatch. A fresh MCP client reconnects with corrected terminal capture to the same original native child; startup/execution are not replayed and10s observation deadlines are unchanged.
This generic source-binding control does not declare physical calibration; it proves field/row identity in pixels, not installed physical-unit, visual biological QA or a promoted recipe. H003e remains immutable REJECT with no scientific-data access, rerun, retune or held-out/reference answers opened. Full ZIP/R0/R1 completion remains outside this checkpoint.
Canonical receipt: docs/validation/paired_field_csv_314_20260930/installed-parent-checkpoint.rst.