feat: Identify closed runtime custody hold boundaries #101

Manually merged
Owner

Identify original runtime hold callsites and Cargo evidence observation/retirement stages using closed literal categories. Retain original owners, raw failures and independent cleanup errors without printing exception representations, paths, tokens or identifiers.

Diagnostics capture the actual failing boundary; they do not establish its cause or successful retirement. Original native holds, deadlines and acceptance requirements remain unchanged.

Identify original runtime hold callsites and Cargo evidence observation/retirement stages using closed literal categories. Retain original owners, raw failures and independent cleanup errors without printing exception representations, paths, tokens or identifiers. Diagnostics capture the actual failing boundary; they do not establish its cause or successful retirement. Original native holds, deadlines and acceptance requirements remain unchanged.
feat: Identify closed runtime custody hold boundaries
Some checks failed
CI / markdown (push) Successful in 28s
CI / thread (push) Successful in 1m48s
CI / memory (pull_request) Has been skipped
CI / thread (pull_request) Has been skipped
CI / markdown (pull_request) Has been skipped
CI / memory (push) Has been cancelled
49e2e19fc5
Emit only a defining callsite category after retaining the original owners and raw primary error. Keep the existing nonreturning hold, independent failures and original ends unchanged; diagnostic refusal cannot release custody. Cover every callsite, hostile representations and actual workspace evidence retirement without inferring native acceptance from model data.
erikinkinen added this to the Alpha 1 milestone 2026-11-10 02:23:23 +01:00
fix: Identify actual Cargo evidence failure stages
Some checks failed
CI / memory (pull_request) Has been skipped
CI / thread (pull_request) Has been skipped
CI / markdown (pull_request) Has been skipped
CI / markdown (push) Successful in 18s
CI / thread (push) Successful in 2m20s
CI / memory (push) Has been cancelled
4706019f3f
Record only closed literal observation and retirement boundaries while preserving original exceptions, independent cleanup errors and uncertain-owner holds. Enroll focused controls without changing native clocks or releasing evidence.
Keep intentional Linux SIGILL controls from publishing uncontrolled core output. Change only each declared crash child, assert its actual limit and dumpability policy, and preserve the parent signal and generated-source closure requirements.

(cherry picked from commit d46538f25f)
(cherry picked from commit 1ee3b7b1c7)
Keep the existing acquisition orderings and update closures while using the renamed standard-library API. Identifier allocation and join-state claims retain their original exhaustion and once-only behavior without deprecated method warnings.
fix: Update startup atomic claims to the current API
Some checks failed
CI / memory (pull_request) Has been skipped
CI / thread (pull_request) Has been skipped
CI / markdown (pull_request) Has been skipped
CI / thread (push) Successful in 1m8s
CI / markdown (push) Successful in 3s
CI / memory (push) Failing after 2m40s
d8680ec532
Use the same standard-library rename for startup binding counts and locale references. Preserve the existing orderings, overflow limits and refusal closures.
fix: Keep checked atomic admission compatible with stable Rust
Some checks failed
CI / memory (pull_request) Has been skipped
CI / thread (pull_request) Has been skipped
CI / markdown (pull_request) Has been skipped
CI / markdown (push) Successful in 4s
CI / thread (push) Successful in 1m16s
CI / memory (push) Failing after 8m34s
3edb0e534f
Use compare-exchange loops for generation, borrow, lease and locale reader admission. Preserve the original success and failure orderings, old-value result and overflow refusal without requiring the unstable atomic_try_update API.
Author
Owner

The wide-string core rejection now accepts both GNU and LLVM diagnostic spelling while requiring the exact nineteen missing aliases and rejecting warnings. This retains the actual failed-link and cleanup checks instead of treating any linker error as success. The startup source oracle also includes its existing inert-by-default thread dependency and explicit feature edges. Published in 4b062cd1.

The wide-string core rejection now accepts both GNU and LLVM diagnostic spelling while requiring the exact nineteen missing aliases and rejecting warnings. This retains the actual failed-link and cleanup checks instead of treating any linker error as success. The startup source oracle also includes its existing inert-by-default thread dependency and explicit feature edges. Published in `4b062cd1`.
Account for the existing inert thread-runtime dependency and locale/string feature edges in the startup source contract. Retain exact dependency and feature equality, optional POSIX admission and forbidden core export checks without changing production code.
Accept the GNU and LLVM undefined-reference spellings only after the original clean exit-one native receipt, then require exactly the nineteen conventional wide names and no warnings. Keep all public and hidden semantics, guard faults, source ownership and original deadlines unchanged.
fix: Compare complete undefined wide symbol tokens
Some checks failed
CI / memory (pull_request) Has been skipped
CI / thread (pull_request) Has been skipped
CI / markdown (pull_request) Has been skipped
CI / thread (push) Successful in 1m8s
CI / markdown (push) Successful in 3s
CI / memory (push) Failing after 8m39s
4b062cd118
Require horizontal separation and the full LLVM diagnostic token so a suffixed or newline-separated spelling cannot impersonate a conventional alias. Preserve exact symbol-set rejection, native receipt requirements and the unchanged companion instructions.
Author
Owner

The corrected wide-string rejection let CI reach the span probe, where rustc could not load the C runtime’s transitive thread ABI dependency. Routed all full-runtime Rust probes through the same retained dependency owner as their library in 7ec60da5. Withdrawal now refuses before compiler invocation, while the original extern metadata, dependency outputs and fresh-result checks remain owned throughout each call.

The corrected wide-string rejection let CI reach the span probe, where rustc could not load the C runtime’s transitive thread ABI dependency. Routed all full-runtime Rust probes through the same retained dependency owner as their library in `7ec60da5`. Withdrawal now refuses before compiler invocation, while the original extern metadata, dependency outputs and fresh-result checks remain owned throughout each call.
Route thematic full-crate callers through the same original dependency owner as their library. Keep the actual extern metadata, dependency directory and fresh output checks throughout each compiler call so transitive crate loading does not fall back to an unowned lookup.
test: Reject Rust probes after dependency withdrawal
Some checks failed
CI / memory (pull_request) Has been skipped
CI / thread (pull_request) Has been skipped
CI / markdown (pull_request) Has been skipped
CI / thread (push) Successful in 1m9s
CI / markdown (push) Successful in 3s
CI / memory (push) Failing after 10m0s
7ec60da544
Keep the saved compiler command subordinate to the original retained output lifetime. Document the shared dependency boundary and check that a withdrawn receiver refuses before source verification or native invocation.
Author
Owner

CI now reaches the freestanding error callback, where the debug build emits an out-of-line libcore slice-method call for is_empty. Selected the same intrinsic length match already used by #111 in dc866c7e. The known/unknown error cases and short-copy capacity assertions remain unchanged; this witness still links without a libcore implementation.

CI now reaches the freestanding error callback, where the debug build emits an out-of-line libcore slice-method call for is_empty. Selected the same intrinsic length match already used by #111 in `dc866c7e`. The known/unknown error cases and short-copy capacity assertions remain unchanged; this witness still links without a libcore implementation.
fix: Keep the freestanding error witness independent of libcore
All checks were successful
CI / memory (pull_request) Has been skipped
CI / thread (pull_request) Has been skipped
CI / markdown (pull_request) Has been skipped
CI / markdown (push) Successful in 3s
CI / thread (push) Successful in 1m12s
CI / memory (push) Successful in 11m11s
dc866c7e9b
Match the intrinsic expected length directly when selecting the short-copy capacity. The debug callback must preserve its unchanged known and unknown error assertions without acquiring an out-of-line core slice-method dependency.

(cherry picked from commit fc2f4828da)
erikinkinen manually merged commit 3b8ea7d481 into feature/offline-workspace-source-catalog 2026-11-21 07:24:06 +01:00
Sign in to join this conversation.
No description provided.