[Clear1nsight]

Change and mathematical scope

Adds concrete source for a candidate entry that stops before inner birth while the actual parent qualifies its protected process chain, retires a property-query subtree, verifies immutable intent/release records and releases once through a held pidfd. The patch connects the entry, relay, lexical parent qualifier, common runner, bootstrap, loader, controller and terminal reader. It preserves a genuine optimized STOP rather than rewriting it as positive PASS.

This is a source archive of an implementation candidate and bounded lifecycle fixtures. The complete authenticated source/role assembly is not installed or accepted. No mathematical bound, scientific execution, complete native/resource admission, performance gain or original-activity completion is claimed. The primary baseline, full comparison campaign, retention and successful CLOSE integration remain outside the implemented scope. See README and open questions.

Task and overlap

Original investigation: #6321. Base: 7c49fe32c55de02c2c873655c804b16e4c3fef0a. Retains the source/ownership/relay contracts of #6830 at 39fcd67c991bd72918080b1d2c02feb3d679206d, common-runner ancestry exposed by #6837 at 92bd2213be787cc4451a3b61b00793dad26bebdd, inherited-limit repair #6847 at efb116491184bd16c5d1ada60d71efdefee61691, and existing complete-outcome CLOSE implementation from #6762 at 3bcf99910a95248452e955d382c59bd23792a39b. Those components are not requalified by this archive.

The added value is actual post-launch qualification/release wiring and a runnable waiting-runner/query-cleanup discriminator, beyond the recovered partial classes. Scope is refined to this concrete source boundary; the complete original caller objective remains open. A bounded all-author/all-state PR-body search for ProtectedRoot found no additional indexed counterpart at round opening; this is not global novelty.

Validation

Five distinct fixture behaviors passed across the declared source snapshots: query-subtree retirement leaves the real protected runner/time/entry intact; intent readback failure does not release; release-seal readback failure does not release; nested timer pop retains the original absolute guard; work expiry leaves only the original retirement interval and forbids new work. After concurrent-RSS reporting changed, the affected positive fixture passed again. Successful unchanged negative/timer controls were not repeated.

A completed bounded Pro review found a timer-unwind first-error defect in the initial commit. Both query and root paths now capture the original error before fallible timer pop. A new deterministic regression executes the actual production unwind nodes for both callers with inert clock/signal ports; both retain and raise the identical original error, then retain the deadline secondary. The correction was locally assessed and tested; complete successor source acceptance is not claimed. See the review disposition.

The fixtures use actual owned processes, pidfds and stop/continue signals, but explicitly inert Context/association/schema/funding ports and a fixture-owned copy of /usr/bin/false. No actual property observer, compiler, native-view entry or scientific driver executes. They do not qualify the authenticated production caller. Exact snapshot hashes and all earlier failed/successful stderr are retained. Fixture preparation failures and production-source failures remain visible.

Execution used Python 3.12 -S -s -P -B, clean fixed-seed environment, AS 256 MiB, soft file limit 2 MiB/hard 512 MiB, core 0, umask 077 and bounded timeout/kill tail. Suggested reproduction and mode reconstruction are in README. Complete resource fit is unproved. Physical costs outside recorded guard accounting remain OPEN_NOT_ZERO.

All 25 committed file bodies and Git blob identities were read back exactly. The manifest and eleven Python source syntax trees were checked without project imports. This is an inert source archive; no research replay hook is added to execute unqualified images. Hosted planning checks are separate from scientific replay.

Credit

Prepared for Clear1nsight with substantial OpenAI Codex and ChatGPT Pro assistance. Adapts Pro's recovered partial ProtectedRoot/DeadlineOwner/common-runner proposal; the waiting entry and connected callers required further implementation. Existing contributor attribution and Apache-2.0 notices are preserved; see NOTICE. AI review is not independent human or proof-kernel acceptance.

Open next questions

Independently review the exact connected source, assemble the immutable real role/stage/loader/controller tuple, and then exercise genuine parent qualification under complete source, ownership, native/resource and funding admission. Preserve the original baseline, comparison order, equality oracles, costs and final retention/CLOSE conditions. Do not infer a full caller, runtime admission or speedup from the fixtures or this PR.

The final head is 47cf8c9af49d22686264db2762700215032eda90 (two preserved commits). Source work closed at the fixed deadline; publication does not resume native/scientific work or add a budget.

[Clear1nsight]

Verified delivery at head 47cf8c9af49d22686264db2762700215032eda90: this PR is open and Ready for review, with maintainer modification disabled, two commits and 25 files. All published file bodies/blob identities and archive hashes were checked.

Hosted attempt 1: plan passed, including onboarding helper tests and changed-package selection; replay was skipped. This supplies archival planning evidence, not scientific replay or complete native qualification.

Canonical original-thread handoff and research-hub pointer are published. The source candidate, bounded Pro defect/correction and remaining source assembly, qualification, funding and comparison/retention/CLOSE requirements are documented above and in the archive. Source work remains frozen; no new execution or budget follows.