S367 · SOURCE-BOUND GATE EVIDENCE
S367 · Linked reply-endpoint wake production writer guard integration
tam production Rust öğesi + exact acquire→release odağı → S247 guard modülü → Operations-bound focused test Bu sayfa yalnız S367 kapısına aittir; komşu kapıların kaynakları bu kabulün içine katılmaz.
S367Production writer guardOperations id exactsource SHA exacttest target exact
operation: g8l-s367-linked-reply-endpoint-wake-writer-guard-integration-partial
production · S247 guard · focused test · Operations · 4 exact excerpt
sequence-bound=true · implementation-bound=true
01 · Test edilen uygulama/model kodu
Kapının yürüttüğü gerçek kaynak
tam Rust öğesiL3153–L3266kapı odağı L3231–L3244
kernel/src/ui/capability.rs::teardown_endpoint_object_under_ipc_transaction
Tam kapsayıcı Rust öğesi gösterilir; vurgulu blok yalnız S367 exact production writer üyeliği sınırıdır. Komşu kod, guard kapsamı iddiası değildir.
/// Commit one already-preflighted normal endpoint removal. This function has
/// no fallible allocation; invariant failures are fail-stop because returning
/// after the registry linearization point would expose a partial teardown.
fn teardown_endpoint_object_under_ipc_transaction(
id: CapId,
expected_owner: u64,
revoker: Option<u64>,
) -> Option<EndpointTeardown> {
let holder_preflight = {
#[cfg(feature = "board-rpi5")]
let _s251_scheduler_read_access = crate::g8l_target_dispatch_scheduler_owner_scheduler_mutation_production_migration_lifecycle_s250_endpoint_commit_read_access_guard_expansion::acquire_s251_production_scheduler_read_access()
.unwrap_or_else(|error| panic!("S251 endpoint-commit holder-preflight scheduler read guard failed closed: {:?}", error));
unsafe { (&*core::ptr::addr_of!(crate::task::scheduler::SCHEDULER)) }
.preflight_endpoint_holder_purge(id, expected_owner)
.expect("endpoint holder graph was not preflighted before commit")
};
let mut removed = {
let mut registry = ENDPOINT_REGISTRY.lock();
let position = registry
.iter()
.position(|endpoint| endpoint.id == id && !endpoint.is_reply_cap)?;
registry.remove(position)
};
assert_eq!(
removed.owner, expected_owner,
"endpoint object owner changed after typed teardown preflight"
);
#[cfg(all(target_arch = "aarch64", target_os = "none", feature = "board-rpi5"))]
let s365_writer_access = crate::g8l_target_dispatch_scheduler_owner_scheduler_mutation_production_migration_lifecycle_s365_endpoint_holder_purge_writer_guard_integration::acquire_s365_production_scheduler_writer_access()
.unwrap_or_else(|error| {
panic!(
"S365 endpoint-holder purge scheduler writer guard failed closed: {:?}",
error
)
});
let purged_holders = unsafe {
(&mut *core::ptr::addr_of_mut!(crate::task::scheduler::SCHEDULER))
.purge_endpoint_holders_exact(id, expected_owner)
};
#[cfg(all(target_arch = "aarch64", target_os = "none", feature = "board-rpi5"))]
drop(s365_writer_access);
assert_eq!(
purged_holders, holder_preflight,
"endpoint holder purge did not match teardown preflight"
);
assert_eq!(
get_capability_store().revoke_endpoint_provenance(id, revoker),
1,
"normal endpoint object must have exactly one provenance record"
);
#[cfg(all(target_arch = "aarch64", target_os = "none", feature = "board-rpi5"))]
let s366_writer_access = crate::g8l_target_dispatch_scheduler_owner_scheduler_mutation_production_migration_lifecycle_s366_primary_endpoint_wake_writer_guard_integration::acquire_s366_production_scheduler_writer_access()
.unwrap_or_else(|error| {
panic!(
"S366 primary endpoint wake scheduler writer guard failed closed: {:?}",
error
)
});
unsafe {
let scheduler = &mut *core::ptr::addr_of_mut!(crate::task::scheduler::SCHEDULER);
scheduler.wake_tasks_on_revoked_endpoint(id);
}
#[cfg(all(target_arch = "aarch64", target_os = "none", feature = "board-rpi5"))]
drop(s366_writer_access);
let rendezvous_summary = removed.rendezvous.revoke();
let mut drained = rendezvous_summary.cancelled_calls;
while let Some((caller_task, reply_cap_id)) = removed.rendezvous.take_cancelled_wake() {
let retire_witness = removed
.rendezvous
.retire(caller_task, reply_cap_id)
.expect("revoked parked CALL must retire after cancellation notification");
assert!(
discard_retired_reply_endpoint_under_ipc_transaction(id, retire_witness, revoker,),
"revoked CALL lost its linked reply object"
);
#[cfg(all(target_arch = "aarch64", target_os = "none", feature = "board-rpi5"))]
let s367_writer_access = crate::g8l_target_dispatch_scheduler_owner_scheduler_mutation_production_migration_lifecycle_s367_linked_reply_endpoint_wake_writer_guard_integration::acquire_s367_production_scheduler_writer_access()
.unwrap_or_else(|error| {
panic!(
"S367 linked reply-endpoint wake scheduler writer guard failed closed: {:?}",
error
)
});
unsafe {
let scheduler = &mut *core::ptr::addr_of_mut!(crate::task::scheduler::SCHEDULER);
scheduler.wake_tasks_on_revoked_endpoint(reply_cap_id);
}
#[cfg(all(target_arch = "aarch64", target_os = "none", feature = "board-rpi5"))]
drop(s367_writer_access);
}
assert_eq!(
removed.rendezvous.reply_len(),
0,
"preflighted endpoint teardown left a reply record behind"
);
// Drain the pre-rendezvous kernel-demo queue as well. EL0 syscalls never
// publish into this legacy queue after K2 P0 integration.
while let Some(envelope) = removed.pending_messages.pop_front() {
drained += 1;
assert_eq!(
envelope.reply_cap_id, 0,
"legacy queue carried a reply authority without rendezvous state"
);
}
Some(EndpointTeardown {
owner: removed.owner,
drained,
})
}snippet sha256: 2b8e092409e5…file sha256: 304e1227daf9…focus sha256: f0a98e61c925…
02 · Ortak exclusion üyeliği
S247 production writer guard
tam Rust öğesiL184–L196
kernel/src/g8l_target_dispatch_scheduler_owner_scheduler_mutation_production_migration_lifecycle_s367_linked_reply_endpoint_wake_writer_guard_integration.rs::acquire_s367_production_scheduler_writer_access
#[cfg(all(target_arch = "aarch64", target_os = "none", feature = "board-rpi5"))]
pub fn acquire_s367_production_scheduler_writer_access(
) -> Result<G8lS367ProductionSchedulerWriterAccess, G8lS247WholeSchedulerAccessError> {
let caller_cpu =
crate::percpu::try_current_cpu_id().ok_or(G8lS247WholeSchedulerAccessError::InvalidCpu)?;
if caller_cpu != crate::g8l_runtime_contract::CPU0 {
return Err(G8lS247WholeSchedulerAccessError::InvalidCpu);
}
let access = crate::g8l_target_dispatch_scheduler_owner_scheduler_mutation_production_migration_lifecycle_s246_whole_scheduler_read_access_guard::S247_PRODUCTION_WHOLE_SCHEDULER_ACCESS_GATE
.try_acquire_exclusive_for_valid_cpu(caller_cpu)?;
Ok(G8lS367ProductionSchedulerWriterAccess { _access: access })
}snippet sha256: 806d5576c30b…file sha256: 9e155a08f7ef…
03 · Doğrulayan test kodu
Operations komutuna bağlı focused test
tam Rust öğesiL386–L397
simulation/tests/g8l_target_dispatch_scheduler_owner_scheduler_mutation_production_migration_lifecycle_s367_linked_reply_endpoint_wake_writer_guard_integration.rs::helper_has_exactly_one_s367_acquire_and_one_release
#[test]
fn helper_has_exactly_one_s367_acquire_and_one_release() {
let boundary = endpoint_teardown_commit_boundary();
assert_eq!(
boundary
.matches("acquire_s367_production_scheduler_writer_access")
.count(),
1
);
assert_eq!(boundary.matches("drop(s367_writer_access)").count(), 1);
}snippet sha256: cc321c57f091…file sha256: b92e6770f060…
04 · Kapı kimlik kaydı
Operations sıra, kimlik ve başlık bağı
tam Operations kaydıL10899–L11047
website/src/lib/operations.ts::g8l-s367-linked-reply-endpoint-wake-writer-guard-integration-partial
{
id: "g8l-s367-linked-reply-endpoint-wake-writer-guard-integration-partial",
date: "2026-08-28",
sequence: 367,
status: "passed",
umbrella_status: "partial",
title:
"S367 · Linked reply-endpoint wake production writer guard integration",
summary:
"S367, teardown_endpoint_object_under_ipc_transaction içindeki exact wake_tasks_on_revoked_endpoint(reply_cap_id) linked reply-endpoint scheduler mutation'ını S366 ve 44 production reader'ın kullandığı aynı statik S247 state word'e bağlar. S366 primary-wake release'i, rendezvous revoke, cancelled-wake extraction, exact reply retirement ve linked reply-object discard writer'dan önce kapanır. Gerçek per-CPU kimliğinden yalnız CPU0 için S367 exclusive writer alınır; exact tek mutable SCHEDULER aliası bütün linked-reply wake method çağrısını kapsar ve loop devam etmeden explicit bırakılır. Helper'ın S365/S366/S367 olmak üzere üç writer sınırı ayrı membership'lerle kapanmıştır; helper içinde başka scheduler writer kalmaz. Guarded writer 40/69, açık writer 29, provider authority 0 ve whole-scheduler exclusion false'dur. İki direct production caller path vardır; supported-profile runtime observation=0'dır. Kaynak sırasındaki sonraki ayrı kapı S368 task-lifecycle wake-capacity writer'ıdır.",
evidence: [
"Focused S367 kapısının production reply-wake membership'i bağlanmadan önceki TDD koşusu 39/51 PASS ve 12 RED verdi. RED yüzeyi exact acquire/release, retire-discard-before-writer sırası, guarded reply slice, üç ayrı helper membership'i ve final empty-rendezvous sınırında kaldı.",
"Exact S367 production acquire/drop bağlandıktan sonra aynı focused hedef 1 grup / 51 passed / 0 failed verdi; envanter veya downstream S368 assertion'ı gevşetilmedi.",
"Final envanter module constants, pending-request outcome ve production source assertions katmanlarında birlikte 44 guarded reader + 40/69 guarded writer + 29 open writer'dır.",
"Exact kaynak sırası S251 holder snapshot → registry linearization → S365 holder purge/drop → equality/provenance → S366 primary wake/drop → rendezvous revoke → cancelled wake take → exact reply retire → linked reply object discard → S367 writer → tek mutable SCHEDULER aliası → wake_tasks_on_revoked_endpoint(reply_cap_id) → writer drop → loop/empty assertion'dır.",
"S366 lease rendezvous revoke başlamadan önce explicit bırakılır. S367 lease ise reply retire ve linked object discard tamamlandıktan sonra alınır; S366→S367 nested exclusive membership oluşmaz.",
"discard_retired_reply_endpoint_under_ipc_transaction exact retire witness olmadan linked reply registry/CNode/provenance nesnesini kaldırmaz. Bu fail-stop boundary S367 scheduler mutation'ından önce kapanır.",
"Production wrapper exact target_arch=aarch64, target_os=none ve feature=board-rpi5 cfg kesişimindedir; try_current_cpu_id gerçek CPU kimliğini türetir ve yalnız CPU0 kabul edilir.",
"Wrapper exact S247_PRODUCTION_WHOLE_SCHEDULER_ACCESS_GATE üzerinde try_acquire_exclusive_for_valid_cpu kullanır. Caller-supplied CPU taklidi veya ayrı model state word production'a taşınmaz.",
"teardown_endpoint_object_under_ipc_transaction içinde exact bir acquire_s367 occurrence'ı, exact bir reply-wake mutable scheduler aliası ve exact bir drop(s367_writer_access) vardır.",
"S367 lease altında yalnız linked reply_cap_id için wake_tasks_on_revoked_endpoint çağrısı yürütülür. Prior holder/provenance/primary/rendezvous/retire/discard kodları guarded dilime katılmaz.",
"drop(s367_writer_access) loop'un devamından ve removed.rendezvous.reply_len()==0 final assertion'ından önce exact kaynak sırasındadır; lease bir iteration dışına taşınmaz.",
"Helper üç mutable scheduler aliasını korur: S365 holder purge, S366 primary wake ve S367 linked reply wake. Üçünün acquire-to-release aralıkları ayrı ve sıralıdır.",
"S367 release'inden sonra helper içinde başka addr_of_mut!(SCHEDULER) veya wake_tasks_on_revoked_endpoint occurrence'ı yoktur; helper writer inventory'si bu kapıda kapanır.",
"Kaynak sırasındaki sonraki writer teardown_task_ipc_lifecycle içindeki try_reserve_ipc_wake_capacity(wake_capacity) sınırıdır. acquire_s368 production sembolü S367 kapanışında yoktur.",
"Scheduler::wake_tasks_on_revoked_endpoint önce IPC deadline registry lock'unu, sonra ipc_blocked_tasks lock'unu alır; lock sırası focused kaynak assertion'ıyla korunur.",
"Wake method CALL ve RECEIVE kayıtlarında endpoint id, reply target, task/token/kind ve deadline identity bağlarını yeniden doğrular; yalnız exact revoked peer ile ilişkili kayıtlar seçilir.",
"Her deadline için complete_peer_closed_exact task state commit'inden önce yürür. Deadline tuple drift'i sessiz başarılı kabul edilmez.",
"Selected continuation exact InvalidCapability alır; message label, badge, data tail ve saved GPR dönüş yüzeyi sıfırlanır. Stale IPC payload kullanıcı continuation'ına taşınmaz.",
"Her seçili task Blocked IPC state'inden Ready durumuna taşınır ve ready_queue'ya exact bir kez yayınlanır. Nonzero ASID yalnız ilgili task için Ready publication'dan önce invalidate edilir.",
"ipc_blocked_tasks lock'u task commit sırasında bırakılır; owned task update ve queue publication sonrasında kalan kayıt taraması için yeniden alınır.",
"İki distinct direct caller path vardır: S364 admission üzerinden task-owned/kernel-shared endpoint destroy yolu ve teardown_task_ipc_lifecycle task-exit yolu. Bu static wiring runtime invocation sayısı değildir.",
"Task-lifecycle caller outer IrqGuard, IPC_TRANSACTION_LOCK ve checked wake capacity discipline'ini taşır. S367 helper yeni outer transaction edinmez.",
"Host-testable execute_s367_guarded_linked_reply_endpoint_wake_commit yalnız CPU0 callback'ini çalıştırır. Non-CPU0, active reader veya active writer callback başlamadan fail-closed olur.",
"Host callback success ve error yolları membership'i exact-once bırakır; success receipt nonzero token ve owned output taşır. S366→S367 token monotonluğu doğrulandı.",
"S367 preflight S366'nın 44 reader / 39 guarded writer / 30 open snapshot'ını exact doğrular; yalnız doğru zincir 40/69 guarded ve 29 open sonucu üretir. Drift ayrı fail-closed error'dır.",
"Pending S245 request yalnız non-consuming view ile incelenir. Request id korunur, take edilmez, S244 admission yayınlanmaz ve provider authority oluşturulmaz.",
"CPU1 coverage service S366 service'inden sonra ve tarihsel S242 consumer'dan önce bağlıdır. Service S247 writer edinmez ve S367 production wake runtime'ını çalıştırmaz.",
"Tarihsel S290 reply-endpoint wake audit'i model-level lease/order kanıtı olarak ayrı kalır. S367 gerçek board-rpi5 static wrapper ve exact production acquisition/drop sınırını ekler.",
"S367 wiring sonrası S366 focused testi iki obsolete global absence assertion'ında 49/51 RED oldu. Assertion'lar S366 guarded diliminin değişmediğini ve S367'nin ayrı downstream membership olduğunu birlikte kanıtlayacak biçimde daraltıldı; S366 51/51 PASS oldu.",
"S365 focused testi aynı nedenle 46/48 RED oldu; historical 38/69 snapshot korunup S366/S367 exact-one ayrı memberships sabitlenerek 48/48 PASS oldu.",
"S364 global downstream absence assertion'ları kendi admission slice'ında S365–S367 acquisition yokluğu ile ayrı teardown helper'daki exact-one memberships'i birlikte doğrulayacak biçimde güncellendi; final S364 41/41 PASS'tir.",
"Final seçili regresyon 9 grup / 256/256 PASS'tir: S367 51, S366 51, S365 48, S364 41, S289–S290 30, S250 11, IPC rendezvous 14 ve IPC CALL deadline runtime 10.",
"Seçili regresyon summary'si 1926 B / e783a0feb37ba384382ff6f5900d32a6e8f11e68e6a36ab57486865aa354902b olarak /tmp/aselsanos-s367-selected.wIbVAO altında ölçüldü.",
"Fresh izole AArch64 profilleri 4/4 exit 0 verdi. Build logları board-qemu 111554 B / b26d45a0a70842e99e96285465252b5ac0b592249684a84fd863ca1427da0a66 / 293 warning; board-rpi4 150399 B / b0fff58d62d3c79904c3f84d665c7491adf89b7c87e0ac76c44498d92073edb7 / 391; board-rpi5 597675 B / 2c6c4abb0114d4e6e7c9d261fd5650dc39a5a61152f6fd3ad2788bd5ee728ec9 / 1354 ve board-rpi5+smp 597669 B / 9db2d9e253f63f00b822505d1e8056d1be4d7ea8fd96707eb02db9866ee25b71 / 1354'tür. Zero-warning iddiası yoktur.",
"Fresh ELF'ler qemu 12622960 B / 0bcab18d7a84a21069354d5fe6cdef2f60ad1345ddca6937c53bfb1877977409; rpi4 7736832 B / 9b0dd541dd9fff004b1be4529100ff9efcbc7e4bfb1b1ba2c935092c0049ad42; rpi5 13979192 B / 3c5ac5a1f8f26389672dd12b67a4bd6b995448aa8782f9c46753c5d800f50a7c ve rpi5+smp 13957496 B / 65e54d3df4f1b8af79fb90d33e4dfb4d619632e554e4209218f0bf809ec37e6a olarak loglardan ayrı ölçüldü.",
"S238–S367 dependency matrisi 131 gruptur ve iki bağımsız seri koşunun her biri 2712/2712 PASS verdi. 12444 B raw özetler 8af4f5d7a31e00c0473cf133a727dfc8619917fc271c5bd1d49ea92c232407e0 / 437e137a99678cc9797cb9d973f25f8c9e8dea3e336b8d46010d3115ac0f2294; 22 timing-result farkı vardır. 12706 B normalize özetler 7d7263a3206d7f9ad2390e4755729d874814f67c34782eb8543c0ad748515525 ile byte-eşittir.",
"Exact yedi frozen G8h assertion dışındaki seri workspace 330 grup / 4570 PASS / 0 fail / 7 filtered verdi; 31232 B summary SHA-256 9c50a5b95c581659277ffac25ab79c432d3baa5d19207994bccecaa50d262227'dir.",
"Filtresiz workspace exit 101 ile yalnız frozen S96 wiring_does_not_mutate_timer_gic_boot_or_expand_runtime_scope source-identity reddinde durdu; 283 grup / 4315 PASS / 1 fail, 26813 B / be5628c72c99fe249c6574450ea8f2530158c34612a987fdbb275c73344a4be7. Global workspace GREEN iddia edilmez.",
"make verify-qemu 116354 B / 0bb2c4de60e19dabbb4a85546860ec1811dcbf623d0622d3248937e68957534e ile W^X 31/31, S130–S154+S271, RuntimePmm, EL0x4096, IPC 20/20, SEC5 ve kernel fault/panic marker 0 PASS verdi. Bu S367 RPi5 runtime invocation kanıtı değildir.",
"S367 modülü/testi ve güncellenen S366/S365/S364 tarihsel boundary testleri scoped rustfmt ile boş çıktılı PASS'tir; seçili git diff check de boş çıktı verdi. Global cargo fmt 117937 B / fb19ddd73dff6c95ae96ded6d6881d785735c16cae0b74c74483b2c86f67faf5 ile miras farklarda RED'dir.",
"Fresh build, dependency, workspace, QEMU ve format artifact dizinleri /tmp/aselsanos-s367-builds.0WIQpv, /tmp/aselsanos-s367-dependency.HX2DKA, /tmp/aselsanos-s367-workspace.Ee5HHr, /tmp/aselsanos-s367-qemu.jSCNgd ve /tmp/aselsanos-s367-format.6cNiZm'dir.",
"S1–S327 tarihsel Kod kataloğu 327/327 ayrı kimlik olarak korunur. Eksik sıra 0, duplicate 0'dır; S365/S366/S367 production panelleri ortak teardown helper'ını tam gösterir ve her kapının exact acquire-to-release üyeliğini ayrı focus ile ayırır. Odaklar birbirine karışmaz.",
"İlk website publication öncesi source-bound registry S1–S367 aralığında 367/367 kapı, 1031 exact excerpt, pre-S328 327/327, missing=none ve registry payload SHA-256 a3a4435fb4e60bdabf0531f115c54a44de28fab936f0fe6fa825b483e12cd313 verdi.",
"Production/main deployment f0327fcb-5127-4a2a-9f40-43bf104ff039 ile https://f0327fcb.aselsan-microkernel.pages.dev adresine 116 upload + 84 existing = 200 asset olarak tamamlandı. Yayın öncesi website 629/629, lint PASS, boş çıktılı TypeScript ve 24/24 static route build PASS verdi.",
"Cache-busted custom-domain /code/, /operations/, /timeline/ ve /yol-haritasi/ HTTP 200 ve deployment out'u ile raw byte-exact PASS verdi. İlk publication ölçüleri sırasıyla 20544721 B / 59ff3274e62f63013db495a5e1ebdec9402a0a444d13a036ff079f89541fc939, 12405643 B / 082faef24882adcba04d351e606cc1cce68b03e58abf5ecad9e3432a71e22022, 4455243 B / 0f4ce42b5cd5ac87b1a1cd6ab840d099a990ae347b8c804f312ffafeb15e0a2e ve 4454991 B / 6c4e594ecdac75dfe7d55512f20d1dc19f2f75ed082841d2a58a2ce20a3d6852'dir. /code no-transform header'ı vardır; literal gate labels 367/367, pre-S328 327/327, missing=0, duplicate=0 ve gerçek Cloudflare email rewrite=0'dır. Immutable f0327fcb hostname probe'u curl exit 28 / HTTP 000 verdi ve custom-domain PASS yerine geçirilmedi. Publication artifact dizini /tmp/aselsanos-s367-publication.s6LCBJ'dir.",
"S367 sırasında güç, SD kart, Mac kart erişimi, UART capture, raw validation, archive veya promotion yapılmadı: physical/device operations=0 ve RUNBOOK_EXECUTED_IN_S367=NO.",
"S367 bazlı bağlayıcı olmayan planlama görünümü R1 S367–S397, R2 S422–S472, R3 S551+, kaba S527–S577 ve risk paylı merkez yaklaşık S552'dir. Bu projeksiyon yeni sıra veya ürün taahhüdü değildir.",
],
commands: [
"cargo test -p aselsan_microkernel_simulation --test g8l_target_dispatch_scheduler_owner_scheduler_mutation_production_migration_lifecycle_s367_linked_reply_endpoint_wake_writer_guard_integration -- --test-threads=1",
"run S367, S366, S365, S364, S289, S290, S250, ipc_rendezvous and ipc_call_deadline_runtime serially",
"run four fresh AArch64 profile builds; run S238-S367 dependency list twice; run filtered and unfiltered serial workspace audits; make verify-qemu",
"npm test && npm run lint && npx tsc --noEmit && npm run build",
"npm run deploy",
"cache-busted curl + cmp for /code/, /operations/, /timeline/ and /yol-haritasi/",
],
terminalSessions: [
{
id: "g8l-s367-focused-source-contract",
title: "S367 focused linked reply-endpoint wake writer membership",
commandLines: [
"cargo test -p aselsan_microkernel_simulation --test g8l_target_dispatch_scheduler_owner_scheduler_mutation_production_migration_lifecycle_s367_linked_reply_endpoint_wake_writer_guard_integration -- --test-threads=1",
],
outputLines: [
"initial test result: RED; S367 focused 39 passed; 12 failed; exact production reply-wake membership not yet wired",
"final test result: ok; S367 focused 1 group / 51 passed; 0 failed",
"shared S247 gate: 44 guarded readers + 40/69 guarded writers; 29 writers open",
"rendezvous revoke/retire/discard < S367 writer < linked reply wake method < writer release < loop/empty assertion",
"helper scheduler writers after S367=0; direct caller paths=2; runtime observations=0; provider authority=0",
],
exitCode: 0,
outputMode: "complete",
},
{
id: "g8l-s367-selected-endpoint-regression",
title: "S367 selected linked-reply endpoint regression",
commandLines: [
"run S367, S366, S365, S364, S289, S290, S250, ipc_rendezvous and ipc_call_deadline_runtime serially",
],
outputLines: [
"historical S366 initially 49/51 RED on obsolete global S367 absence",
"historical S365 initially 46/48 RED on obsolete global S367 absence",
"preserved S364-S366 guarded slices and bound exact one separate downstream S367 membership",
"S368 task-lifecycle wake-capacity remains a separate open writer",
"final result: 9 groups / 256 passed / 0 failed",
],
exitCode: 0,
outputMode: "complete",
},
{
id: "g8l-s367-core-acceptance",
title: "S367 four-profile, dependency, workspace and QEMU acceptance",
commandLines: [
"run four fresh AArch64 profile builds",
"run S238-S367 dependency list twice and normalize timing fields",
"run filtered and unfiltered serial workspace audits",
"make verify-qemu",
],
outputLines: [
"four profiles 4/4 exit 0; log and ELF byte/hash measurements recorded separately; zero-warning not claimed",
"dependency 131 groups / 2712/2712 twice; normalized 12706-byte summaries are SHA-256 identical",
"filtered workspace 330 groups / 4570 PASS / 7 filtered; unfiltered frozen-S96 remains RED",
"QEMU W^X 31/31 + S130-S154 + S271 + RuntimePmm + EL0x4096 + IPC 20/20 + SEC5 PASS; not an S367 runtime observation",
],
exitCode: 0,
outputMode: "complete",
},
{
id: "g8l-s367-production-publication",
title: "S367 Operations/Timeline/Code production publication",
commandLines: [
"npm test && npm run lint && npx tsc --noEmit && npm run build",
"npm run deploy",
"cache-busted curl + cmp for /code/, /operations/, /timeline/ and /yol-haritasi/",
],
outputLines: [
"website tests 629/629 PASS; lint PASS; TypeScript exit 0 with empty output; static routes 24/24",
"registry S1-S367: 367/367 gates; 1031 exact excerpts; pre-S328 327/327; missing=0; duplicate=0",
"deployment f0327fcb-5127-4a2a-9f40-43bf104ff039; 116 upload + 84 existing = 200 assets",
"custom-domain code/operations/timeline/yol-haritasi HTTP 200 and byte-exact=true; email rewrite=0; no-transform",
"immutable hostname curl exit 28 / HTTP 000; custom-domain PASS not substituted",
],
exitCode: 0,
outputMode: "complete",
},
],
terminalSessionsNote:
"Terminal kartları focused kaynak kabulünü, seçili endpoint regresyonunu, dört-profil/dependency/workspace/QEMU kabulünü ve production publication'ı ayrı gösterir. S367 yalnız linked reply-endpoint wake writer'ıdır; prior retire/discard veya next S368 task-lifecycle writer kodunu kendi guard coverage'ına katmaz.",
limitations: [
"S367 kırkıncı production writer'ın dar kaynak entegrasyonudur; yalnız exact linked reply-endpoint wake mutation'ı guarded'dır.",
"S368 task-lifecycle wake-capacity reservation ayrı açık kapıdır; prior rendezvous/retire/discard S367 lease'i dışında kalır.",
"29 production writer shared S247 gate dışında kalır; provider authority ve whole-scheduler exclusion tamamlanmadı.",
"İki static caller path wiring envanteridir; S367-specific supported-profile invocation/observation kanıtı yoktur.",
"Global rustfmt ve frozen-S96 filtresiz workspace RED'dir; global repository GREEN iddia edilmez.",
"Default-parallel PTY determinism, transient-contention liveness/soak, Generic SMP ve fiziksel RPi kabulü açıktır.",
"physical/device operations=0 · RUNBOOK_EXECUTED_IN_S367=NO.",
],
},snippet sha256: f1f4dae26686…file sha256: 9726dbf00f84…
Focused test komutu
cargo test -p aselsan_microkernel_simulation --test g8l_target_dispatch_scheduler_owner_scheduler_mutation_production_migration_lifecycle_s367_linked_reply_endpoint_wake_writer_guard_integration -- --test-threads=1proof: docs/M8.1-RPi5-G8l-S367-Linked-Reply-Endpoint-Wake-Writer-Guard-Integration-Proof.md
Registry schema v5 · generator
website/scripts/generate-code-gates.mjs · Tam SHA-256: 91d38c7b6222f0b4c117be786454853543da55a160e543d9b951057cc20dcc06