feat(platform-core): Capability Registry runtime wiring (W3)#74
Merged
Conversation
…ers→adapter→registry
Daha once foundation olarak hazirlanan Capability Provider Adapter + runtime provider'lari
ILK kez gercek capabilityRegistry singleton'ina SALT-OKUNUR AYNA modunda baglar. SystemBoot
Wave 2'de additive kayit (_reg, LIFO shutdown; savunmaci try/catch fail-soft).
Zincir: createRuntimeCapabilityProviders({env:{navigator,deviceTier}}) → createCapability
ProviderAdapter({registry,providers}) → capabilityRegistry.
EN KUCUK GUVENLI KAPSAM: yalniz yan-etkisiz browser-API + deviceTier kanidi baglanir
(device.gps/microphone/bluetooth/wifi/cellular, navigation.gps). Probe-tabanli provider'lar
(secureStorage/AI BYOK/modul readiness/offline map-routing) BILINCLI baglanmaz → ilgili
capability'ler Registry'de unknown kalir (zero-trust, durust bosluk; gercek probe'lar ayri PR).
Kurallar korundu: HAL/store/registry sahibi degismez · adapter yalniz kopru · Event Bus/Deep
Scan/Platform Kernel/tuketici migrasyonu YOK · UI/native/SQL/OBD/CAN dokunulmaz · yeni timer/
polling yok · import yan etkisiz · tek-instance guard · fail-soft · zero-leak · dedup (adapter
_last imza) · O(1). capabilityRegistry PAYLASILAN singleton → cleanup dispose ETMEZ.
Test: 32 yeni test (yasam dongusu/dedup/duplicate/fail-soft/bounded status/kapsam-siniri/
SystemBoot sira kilidi). Tam suite 3603 yesil (202 dosya), tsc temiz, lint 0 error, build OK.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0141GKY1eQru4Ap1PWN4VVst
…fied, cihaz bekliyor providers→adapter→registry ayna modu host-dogrulandi (32 test, suite 3603, tsc/lint/build temiz). Cihazda started/providerCount/resolvedCount + regresyon yoklugu dogrulanmali. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0141GKY1eQru4Ap1PWN4VVst
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Amaç (Roadmap FAZ 2 · W3)
Daha önce foundation olarak hazırlanan Capability Provider Adapter + runtime provider'ları
İLK kez gerçek
capabilityRegistrysingleton'ına — SALT-OKUNUR AYNA MODUNDA — bağlar.Yeni özellik/mimari değişikliği değil; yalnız mevcut foundation'ı güvenli aktive etmek.
Bağımlılık: ✅ W2 Vehicle HAL Wiring.
Salt-okunur analiz bulgusu (varsayım yok)
grep "apability" SystemBoot.ts→ BOŞ: Registry boot'a hiç bağlı değildi (W2'nin aksine).Foundation mevcut:
capabilityRegistry(PR #48),capabilityProviderAdapter(PR #52),runtimeCapabilityProviders. Eksik olan yalnız runtime wiring.Hedef veri akışı
En küçük güvenli kapsam (bilinçli)
Yalnız yan-etkisiz, salt-okunur browser-API +
deviceTierkanıtı bağlanır:device.gps/microphone/bluetooth/wifi/cellular,navigation.gps. Probe-tabanlı provider'lar(secureStorage / AI BYOK config / modül runtime readiness / offline map-routing) bilinçli
bağlanmadı → ilgili capability'ler Registry'de
unknownkalır (zero-trust, dürüst boşluk).Bu, yeni yan etki / yeni modül import'u / native çağrı eklemeden en küçük gerçek-kanıt akışını
sağlar; gerçek probe'lar sonraki PR'da eklenir (foundation'ın tasarımı da bu — probe DI).
Kural uyumu
HAL/store/registry sahibi değişmez · adapter yalnız köprü · Event Bus / Capability tüketici
migrasyonu / Deep Scan / Platform Kernel YOK · UI/native/SQL/OBD/CAN dokunulmaz · yeni timer/
polling yok · import yan etkisiz (
start...()çağrılana dek inert) · tek-instance guard ·fail-soft (dışarı exception kaçmaz) · zero-leak (cleanup adapter dispose) · dedup (
_lastimza) ·O(1).
capabilityRegistryPAYLAŞILAN singleton → cleanup dispose ETMEZ.Değişen dosyalar
platform/system/platformCoreCapabilityWiring.tsplatform/system/SystemBoot.ts_regkaydı (savunmacı try/catch)__tests__/platformCoreCapabilityWiring.test.tsdocs/DEVICE_VALIDATION_LEDGER.mdDoğrulama
kapsam-sınırı kaynak-kilidi / SystemBoot sıra kilidi)
tsc -btemiz · lint 0 error ·npm run buildOK🤖 Generated with Claude Code