Skip to content

Preserve scientific field sequences through review and release - #46

Closed
MrScripty wants to merge 1 commit into
feature/generic-project-opening-20261013from
feature/scientific-field-sequences-20261013
Closed

MrScripty wants to merge 1 commit into
feature/generic-project-opening-20261013from
feature/scientific-field-sequences-20261013

Conversation

@MrScripty

@MrScripty MrScripty commented Oct 13, 2026 •

Copy link
Copy Markdown
Owner

Integration disposition — 2026-10-14

Current reconciliation (2026-10-14): qualified generic content from this original stack is superseded and integrated in merged PR56 on main, without unqualified PR43 ancestry. This original draft/branch remains retained as source/evidence and for any producer-v2-specific dependent guards. It is no longer a pending generic-feature merge. Do not merge the deferred legacy stack wholesale; its original actual-data acceptance remains open.

Original source and qualification record follows:

Scientific repositories can now import lossless field sequences into Data, inspect staggered fields in physical coordinates, review whole trajectories and freeze a recoverable canonical release. Import binds the displayed source hash; original ZIP/NPY bytes, time labels and producer stages are preserved. The generic core contains no producer-specific parsing.

Schema6 explicitly upgrades the Workbench kind constraint while retaining earlier schema identities. Shared local-file publication preserves rollback and uncertain-commit custody. The cold reader checks original arrays, duplicated provenance and family protections. Existing catalog workflows remain available.

Validation: actual native and rotated noncubic browser workflows pass offline, including stale imports, exact independent NumPy slices, review/freeze/download/restart and delayed-import selection protection. Storage/migration67, project17, scientific parser/service7, cold reader6 and independent spatial reader20 tests pass. Existing workspace browser18 passes. Independent review found no remaining source blocker. Final full suite:696 tests passed (three optional-reader skips covered by separate passing qualified-reader runs). Hosted CI passed at exact head 2476a7daa339597557d29eb6e691327895d8c48c: UI14/14 steps and lifecycle125/125 steps.

Stacked on PR45. Evidence and screenshots: docs/plans/generic-scientific-projects/reports/p2-verification.md. This is custody and inspection qualification; it does not claim scientific/model accuracy, training, actor authorization or native execution through Runs. No merge/deployment.

@coderabbitai

coderabbitai Bot commented Oct 13, 2026

Copy link
Copy Markdown

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

  • Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

Copy link
Copy Markdown
Owner Author

Closing this original stacked proposal as selectively incorporated or superseded by merged #56 (generic scientific core) and #57 (generic scoped MCP).

Scientific field/immutable asset/release/schema6 owners and P2 evidence incorporated through qualified final P5c source/PR56; later finite model evidence extends those owners.

Independent cleanup review checked this exact head 2476a7daa339597557d29eb6e691327895d8c48c against main ab2ca5ba225ae6f8fa91ce7dd743ba1e48ea72a0 and the admitted selective-integration lineage. Deferred controls-v2 and complete original P6/G7 scope remain preserved in open #43 and #53; this closure does not claim those gates passed.

The original branch is retained. Its head is not ancestral to main, so this cleanup neither deletes its history nor merges its excluded ancestry.

@MrScripty MrScripty closed this Oct 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant