Select the pure generic caller entry for C commands #108
No reviewers
Labels
No labels
alpha-1
bug
ci
docs
duplicate
enhancement
help wanted
invalid
performance
phase-6
question
refactor
security
wontfix
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
erix/lib-cstd!108
Loading…
Reference in a new issue
No description provided.
Delete branch "perf/generic-caller-native-owner"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary and rationale
Select the complete command-owner source family whose explicitly caller-clocked public entry uses the shared pure executor directly. The producer and both workflows select the same Integration source and complete ten-body declaration.
The public generic entry now works inside the actual closed private cohort without requesting a Cargo-policy import. Its original clocks, process cleanup and refusal of a manufactured forest certificate remain explicit.
Tracking and scope
Companion to the generic caller entry.
Builds on the reader Scope companion and follows the root owner composition. Related: native owner compatibility.
Architecture, authority and failure behavior
There is one actual selected native class and registry family. Ordinary source-backed commands retain their defining Source/Stage facade. Original clock starts, cancellation, receipts, masks, OFD witnesses and physical retirement remain mandatory. This generic entry supplies no source or caller-channel forest authority.
Validation evidence
The selected owner controls and source-backed memory object/archive are qualified. Earlier reader/pure-owner artifact evidence remains separate; guest execution and self-hosting are not established here.
WIP: Select the pure generic caller entry for C commandsto Select the pure generic caller entry for C commandsThe matching private cohort now supports the public generic caller-clocked entry without Cargo imports. Its original native cleanup contract and the actual source-backed memory object/archive production are qualified; the selected Source/Stage facade is unchanged.
The memory job identified
runtime/posix-io/coreas the extra source entry. The intentional SIGILL child now disables its own core dumps, using the change from #102. The parent still checks for SIGILL and verifies that no core was dumped; source-closure checks remain strict.Updated the workspace controls to load all ten declared process-owner modules from the selected source instead of a synthetic partial cohort. Cache refusal now checks the defining command_native_runner source and the original module namespace. The hash-before-execution, ambient-module restoration and initializer/slot nonmutation checks remain intact. Published in
248f60df.Prepared the merge history at e90c0113 to remove duplicate upstream patches and integrate the feature on its prepared prerequisite history. The feature tree is unchanged.
Published the repaired merge history at 6cdd34c8. It is prepared on #106’s published
edd755b3prerequisite and selects the repaired command owner from erix/integration#775. It preserves the upstream release staging and diagnostics. The original work branch and earlier prepared ref remain intact. This prepared history targetsfeature/native-c-pure-owner-cohort; the original PR currently targetsfeature/raw-live-scope-freshness, so the destination must be reconciled before merging. Fresh review applies to the new prepared commit.