From 2cd5f7577f1f6775451168ea62b89e615271fce1 Mon Sep 17 00:00:00 2001 From: Gustavo Madeira Santana Date: Sun, 15 Mar 2026 16:41:36 +0000 Subject: [PATCH] Docs: refresh extension host migration status --- .../openclaw-capability-catalog-and-arbitration-spec.md | 2 ++ .../openclaw-extension-contribution-schema-spec.md | 2 ++ .../openclaw-extension-host-implementation-guide.md | 2 ++ .../openclaw-extension-host-lifecycle-and-security-spec.md | 2 ++ .../openclaw-kernel-event-pipeline-spec.md | 1 + .../openclaw-kernel-extension-host-transition-plan.md | 3 +++ 6 files changed, 12 insertions(+) diff --git a/docs/.internal/extension-host-migration/openclaw-capability-catalog-and-arbitration-spec.md b/docs/.internal/extension-host-migration/openclaw-capability-catalog-and-arbitration-spec.md index 4881e229a81..7f70942b6c3 100644 --- a/docs/.internal/extension-host-migration/openclaw-capability-catalog-and-arbitration-spec.md +++ b/docs/.internal/extension-host-migration/openclaw-capability-catalog-and-arbitration-spec.md @@ -48,6 +48,7 @@ What has been implemented: - loader post-import planning and `register(...)` execution now route through `src/extension-host/loader-register.ts` - loader per-candidate orchestration now routes through `src/extension-host/loader-flow.ts` - loader top-level load orchestration now routes through `src/extension-host/loader-orchestrator.ts` +- loader execution setup composition now routes through `src/extension-host/loader-execution.ts` - loader discovery and manifest bootstrap now routes through `src/extension-host/loader-bootstrap.ts` - loader mutable activation state now routes through `src/extension-host/loader-session.ts` - loader session run and finalization composition now routes through `src/extension-host/loader-run.ts` @@ -69,6 +70,7 @@ How it has been implemented: - by extracting discovery, manifest loading, manifest diagnostics, discovery-policy logging, provenance building, and candidate ordering into a host-owned loader-bootstrap helper before catalog publication work - by extracting candidate iteration, manifest lookup, per-candidate session processing, and finalization handoff into a host-owned loader-run helper before catalog publication work - by converting the compatibility record-state layer into an enforced loader lifecycle state machine before catalog publication work +- by extracting runtime creation, registry creation, bootstrap setup, module-loader creation, and session creation into a host-owned loader-execution helper before catalog publication work - by moving mutable activation state into a host-owned loader session before catalog publication work - by extracting shared provenance path matching and install-rule evaluation into `src/extension-host/loader-provenance.ts` so activation and finalization policy seams reuse one host-owned implementation - by turning open-allowlist discovery warnings into explicit host-owned discovery-policy results before catalog publication work diff --git a/docs/.internal/extension-host-migration/openclaw-extension-contribution-schema-spec.md b/docs/.internal/extension-host-migration/openclaw-extension-contribution-schema-spec.md index 3e555e11467..ec1b3cdf426 100644 --- a/docs/.internal/extension-host-migration/openclaw-extension-contribution-schema-spec.md +++ b/docs/.internal/extension-host-migration/openclaw-extension-contribution-schema-spec.md @@ -52,6 +52,7 @@ What has been implemented: - loader post-import planning and `register(...)` execution now route through `src/extension-host/loader-register.ts` - loader per-candidate orchestration now routes through `src/extension-host/loader-flow.ts` - loader top-level load orchestration now routes through `src/extension-host/loader-orchestrator.ts` +- loader execution setup composition now routes through `src/extension-host/loader-execution.ts` - loader discovery and manifest bootstrap now routes through `src/extension-host/loader-bootstrap.ts` - loader mutable activation state now routes through `src/extension-host/loader-session.ts` - loader session run and finalization composition now routes through `src/extension-host/loader-run.ts` @@ -73,6 +74,7 @@ How it has been implemented: - by extracting discovery, manifest loading, manifest diagnostics, discovery-policy logging, provenance building, and candidate ordering into a host-owned loader-bootstrap helper before broader schema-driven lifecycle ownership changes - by extracting candidate iteration, manifest lookup, per-candidate session processing, and finalization handoff into a host-owned loader-run helper before broader schema-driven lifecycle ownership changes - by turning the compatibility record-state layer into an enforced loader lifecycle state machine before broadening the schema-driven host lifecycle model +- by extracting runtime creation, registry creation, bootstrap setup, module-loader creation, and session creation into a host-owned loader-execution helper before broadening the schema-driven host lifecycle model - by moving mutable activation state into a host-owned loader session before broadening the schema-driven host lifecycle model - by extracting shared provenance path matching and install-rule evaluation into `src/extension-host/loader-provenance.ts` so activation and finalization policy seams reuse one host-owned implementation - by turning open-allowlist discovery warnings into explicit host-owned discovery-policy results before broadening the schema-driven host lifecycle model diff --git a/docs/.internal/extension-host-migration/openclaw-extension-host-implementation-guide.md b/docs/.internal/extension-host-migration/openclaw-extension-host-implementation-guide.md index ed779637e3b..5b51507e535 100644 --- a/docs/.internal/extension-host-migration/openclaw-extension-host-implementation-guide.md +++ b/docs/.internal/extension-host-migration/openclaw-extension-host-implementation-guide.md @@ -73,6 +73,7 @@ What has been implemented so far: - loader post-import planning and `register(...)` execution now route through `src/extension-host/loader-register.ts` - loader per-candidate orchestration now routes through `src/extension-host/loader-flow.ts` - loader top-level load orchestration now routes through `src/extension-host/loader-orchestrator.ts` +- loader execution setup composition now routes through `src/extension-host/loader-execution.ts` - loader discovery and manifest bootstrap now routes through `src/extension-host/loader-bootstrap.ts` - loader mutable activation state now routes through `src/extension-host/loader-session.ts` - loader session run and finalization composition now routes through `src/extension-host/loader-run.ts` @@ -116,6 +117,7 @@ How it has been done: - by adding explicit compatibility `lifecycleState` mapping on loader-owned plugin records before enforcing the loader lifecycle state machine - by turning that compatibility `lifecycleState` field into an enforced loader lifecycle state machine with readiness promotion during finalization - by moving the remaining top-level loader orchestration into a host-owned module so `src/plugins/loader.ts` becomes a compatibility facade instead of the real owner +- by extracting runtime creation, registry creation, bootstrap setup, module-loader creation, and session creation into a host-owned loader-execution helper before shrinking the remaining orchestrator surface - by moving mutable activation state such as seen-id tracking, memory-slot selection, and finalization inputs into a host-owned loader session instead of leaving them in top-level loader variables - by extracting shared provenance path matching and install-rule evaluation into `src/extension-host/loader-provenance.ts` so activation and finalization policy seams reuse one host-owned implementation - by turning open-allowlist discovery warnings into explicit host-owned discovery-policy results before the orchestrator logs them diff --git a/docs/.internal/extension-host-migration/openclaw-extension-host-lifecycle-and-security-spec.md b/docs/.internal/extension-host-migration/openclaw-extension-host-lifecycle-and-security-spec.md index 1ea4e32595e..0503da1f7f0 100644 --- a/docs/.internal/extension-host-migration/openclaw-extension-host-lifecycle-and-security-spec.md +++ b/docs/.internal/extension-host-migration/openclaw-extension-host-lifecycle-and-security-spec.md @@ -50,6 +50,7 @@ What has been implemented: - loader post-import planning and `register(...)` execution now route through `src/extension-host/loader-register.ts` - loader per-candidate orchestration now routes through `src/extension-host/loader-flow.ts` - loader top-level load orchestration now routes through `src/extension-host/loader-orchestrator.ts` +- loader execution setup composition now routes through `src/extension-host/loader-execution.ts` - loader discovery and manifest bootstrap now routes through `src/extension-host/loader-bootstrap.ts` - loader mutable activation state now routes through `src/extension-host/loader-session.ts` - loader session run and finalization composition now routes through `src/extension-host/loader-run.ts` @@ -79,6 +80,7 @@ How it has been implemented: - by moving post-import planning and `register(...)` execution next while leaving entry-path and import flow unchanged - by composing those seams into one host-owned per-candidate loader orchestrator before moving final lifecycle-state behavior - by moving the remaining top-level loader orchestration into a host-owned module before enforcing the loader lifecycle state machine +- by extracting runtime creation, registry creation, bootstrap setup, module-loader creation, and session creation into a host-owned loader-execution helper before shrinking the remaining orchestrator surface - by moving record-state transitions first into a compatibility layer and then into an enforced loader lifecycle state machine - by moving cache writes, provenance warnings, final memory-slot warnings, and activation into a host-owned loader finalizer before introducing an explicit lifecycle state machine - by adding explicit compatibility `lifecycleState` mapping on loader-owned plugin records before enforcing the loader lifecycle state machine diff --git a/docs/.internal/extension-host-migration/openclaw-kernel-event-pipeline-spec.md b/docs/.internal/extension-host-migration/openclaw-kernel-event-pipeline-spec.md index c2c9aef9122..4fe13cba1f4 100644 --- a/docs/.internal/extension-host-migration/openclaw-kernel-event-pipeline-spec.md +++ b/docs/.internal/extension-host-migration/openclaw-kernel-event-pipeline-spec.md @@ -47,6 +47,7 @@ Relevant prerequisite work that has landed: - loader post-import planning and `register(...)` execution now have a host-owned helper boundary - loader per-candidate orchestration now has a host-owned helper boundary - loader top-level load orchestration now has a host-owned helper boundary +- loader execution setup composition now has a host-owned helper boundary - loader discovery and manifest bootstrap now has a host-owned helper boundary - loader discovery policy outcomes now have a host-owned helper boundary - loader mutable activation state now has a host-owned helper boundary diff --git a/docs/.internal/extension-host-migration/openclaw-kernel-extension-host-transition-plan.md b/docs/.internal/extension-host-migration/openclaw-kernel-extension-host-transition-plan.md index 139dfa01ccf..bd4e39b62c4 100644 --- a/docs/.internal/extension-host-migration/openclaw-kernel-extension-host-transition-plan.md +++ b/docs/.internal/extension-host-migration/openclaw-kernel-extension-host-transition-plan.md @@ -58,6 +58,7 @@ What has landed: - loader post-import planning and `register(...)` execution now route through `src/extension-host/loader-register.ts` - loader per-candidate orchestration now routes through `src/extension-host/loader-flow.ts` - loader top-level load orchestration now routes through `src/extension-host/loader-orchestrator.ts` +- loader execution setup composition now routes through `src/extension-host/loader-execution.ts` - loader discovery and manifest bootstrap now routes through `src/extension-host/loader-bootstrap.ts` - loader mutable activation state now routes through `src/extension-host/loader-session.ts` - loader session run and finalization composition now routes through `src/extension-host/loader-run.ts` @@ -102,6 +103,7 @@ How it was done: - by adding explicit compatibility `lifecycleState` mapping on loader-owned plugin records before enforcing the loader lifecycle state machine - by turning that compatibility `lifecycleState` field into an enforced loader lifecycle state machine with readiness promotion during finalization - by moving the remaining top-level loader orchestration into a host-owned module so `src/plugins/loader.ts` becomes a compatibility facade instead of the real owner +- by extracting runtime creation, registry creation, bootstrap setup, module-loader creation, and session creation into a host-owned loader-execution helper before shrinking the remaining orchestrator surface - by moving mutable activation state such as seen-id tracking, memory-slot selection, and finalization inputs into a host-owned loader session instead of leaving them in top-level loader variables - by extracting shared provenance path matching and install-rule evaluation into `src/extension-host/loader-provenance.ts` so activation and finalization policy seams reuse one host-owned implementation - by turning open-allowlist discovery warnings into explicit host-owned discovery-policy results before the orchestrator logs them @@ -130,6 +132,7 @@ Committed implementation slices so far: - `52495d23d5` `Plugins: extract loader runtime factories` - `6e187ffb62` `Plugins: extract loader bootstrap` - `234a540720` `Plugins: extract loader session runner` +- `a98443c39d` `Plugins: extract loader execution setup` - `89414ed857` `Docs: track extension host migration internally` - `d8af1eceaf` `Docs: refresh extension host migration status`