[BUG] Launch admission typing and original fixtures retain superseded geometry #19
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/launchd#19
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
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
Launch admission typing and original fixtures retain superseded geometry. Maintained validation cannot reach its intended successful boundary.
A newer independent factory-transfer control also mistakes the post-retirement READ/MINT mask for the initial READ/WRITE/MINT receipt.
Reproduction
At Launchd
7e861a0bd9002476e75fd3db2127fc54d411726c, runcargo test --all-targets --offline --lockedwith the original declared Git dependencies prepared.genuine_factories_move_after_receivers_without_a_single_factory_ceilingfails atsrc/runtime/realm_mediator_factory_tests.rs:87: actual 2051 (0x803), expected 2049 (0x801). The bin suite finishes 211 passed and one failed.Expected and actual behavior
The maintained source should compile, discover its original controls and complete the specified checks without warnings. Two scoped owner constructors pass a u32 generation to the full-width u64 binding. Original fixtures additionally omit required manifest/display storage, use old call envelopes or relocation opcodes, retain the old client stride/two-column layout and miss an inherited stream descriptor. Empty local stream regions are also rejected despite explicit disabled policy.
The initial independent expectation must be READ/WRITE/MINT (
0x803). READ/MINT (0x801) belongs only to the proven later initial-result retirement phase. Keep the exact original factory identity, source mask, caller correlation, single native completion, unique movement and independent absence assertions. The runtime already delivers the canonical0x803receipt; this failure is in the maintained control.Environment and identity
Component repository/revision and Integration source graph: original launchd source, original Integration graph.
Image profile, digest and build/runtime configuration: maintained host validation and selected component workflow; no guest image is claimed by this report.
Hardware or VM, architecture, firmware and toolchain versions: x86_64 host with the workflow-selected toolchain; no hardware or firmware-specific cause is inferred.
Input/session route and granted authority relevant to reproduction: explicit source graph and local validation inputs; no additional runtime authority is introduced.
Last known working revision, if known: not established.
Additional reproduced source: Launchd
7e861a0bd9002476e75fd3db2127fc54d411726c, original Cargo selectors, Rust 1.93.0 on x86_64 Linux. An exact signed private checkout reproduces the unchanged control with only the reviewed documentation overlay; no image or extra native authority is involved.Evidence and prior checks
The initial factory control expects READ/MINT despite the canonical phases. Existing recipient-role controls independently reject the premature
0x801mask. The original 211/1 failure is retained separately from corrected-source results.Tracking
Phase completion tracks the remaining guest and self-hosting work.
The related factory documentation mismatch is separate from this wrong control expectation. Neither correction changes production rights or grants broader guest acceptance.
The correction uses independent
0xc03source and0x803initial-recipient expectations. The identity, caller correlation, unique movement and source-absence checks remain intact. The original 211-pass/one-failure result is retained; the corrected control passes. Production rights and layouts are unchanged. The manual and related documentation are being aligned with the same transition.