Integrate callable-native dtype defaults into main after stacked PR2 - #3
Merged
Merged
Conversation
…0929 Declare native output defaults through existing typed dtype policy (#213)
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
1 participant
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.
Integrates the tested PR2 native callable dtype default into main. PR2 was stacked on the retained-history PR1 branch; merging it updated that former base branch, not main. The merged branch821696e7 includes current main409b1e0 and is tree-identical to the parent-tested d6d92a7 PR2 checkpoint. Actual code delta against main is only decorators.py and four focused callable dtype tests. Existing typed DtypeConversionConfig and reflected parameter owners are extended, not a BaSiC-specific registry/wrapper. Four real dtype cases passed in the paired15-test OpenHCS/BaSiCPy CPU source run; original packaged architecture ratchet38metrics, no positive deltas. No install/download or installed-entrypoint readiness claim. Parent owns this coherent integration; no optional hosted-CI wait. Source and receipts are documented in OpenHCS PR217 docs/validation/basicpy_parent_numeric_20260930 and its persistent issue-batch ledger. Closes the main-routing gap from PR2; OpenHCS installed/MCP acceptance remains separate.