Context
Slice 2 of #9846 (split during the #13154 review, per @neo-gpt's close-target audit). Slice 1 — the create_component NL tool (schema-validated, write-locked, delegates to call_method as container.add(config)) — shipped in #13154 with unit coverage. This ticket carries the live-runtime + E2E verification of the shipped tool.
Release classification: boardless — Agent OS / Neural Link enhancement, not a v13 release blocker.
The Problem
Slice 1's create_component resolves the target via sessionId (parity with every NL tool) and is unit-tested by mocking the transport. It does NOT yet: (a) verify the created component is queryable / visible afterward, or (b) prove the create end-to-end against a live App Worker.
The Fix
- get_component_tree visibility: confirm a component created via
create_component appears in get_component_tree / is queryable in the live app.
- E2E proof: an e2e that drives a live app, calls
create_component, and inspects the result (via the NeuralLink fixture + a real App Worker).
- (Multi-window targeting moved to #13185 — see re-scope below.)
Acceptance Criteria (re-scoped per @neo-gpt's #13183 review)
Out of Scope
- The tool itself, schema-validation, and the
write-locked tier (delivered in #13154).
- The direct multi-window e2e (AC1) — #13185.
Implementation note
The NL-service e2e/unit setup must set the neural-link config autoConnect=false before importing ConnectionService (else it spawns a real Bridge at import — see #13154's isolation fix).
Related
Related: #9846, #13154, #13106, #13183, #13185
Origin Session ID: 4cc428e3-cf36-4324-8646-1b96cb23fa4a
Context
Slice 2 of #9846 (split during the #13154 review, per @neo-gpt's close-target audit). Slice 1 — the
create_componentNL tool (schema-validated,write-locked, delegates tocall_methodascontainer.add(config)) — shipped in #13154 with unit coverage. This ticket carries the live-runtime + E2E verification of the shipped tool.Release classification: boardless — Agent OS / Neural Link enhancement, not a v13 release blocker.
The Problem
Slice 1's
create_componentresolves the target viasessionId(parity with every NL tool) and is unit-tested by mocking the transport. It does NOT yet: (a) verify the created component is queryable / visible afterward, or (b) prove the create end-to-end against a live App Worker.The Fix
create_componentappears inget_component_tree/ is queryable in the live app.create_component, and inspects the result (via the NeuralLink fixture + a real App Worker).Acceptance Criteria (re-scoped per @neo-gpt's #13183 review)
create_componentappears inget_component_treeresults — delivered in #13183.useSharedWorkers: true) — moved to #13185 (a direct shared-worker multi-window e2e). It is belt-and-suspenders: the mechanism is sound by composition (create_componentdelegates to the window-agnostic, id-basedcall_method; globally-unique ids reuse the App Worker's existing per-window routing). #13157 is now scoped to the delivered AC2 + AC3.Out of Scope
write-lockedtier (delivered in #13154).Implementation note
The NL-service e2e/unit setup must set the neural-link config
autoConnect=falsebefore importingConnectionService(else it spawns a real Bridge at import — see #13154's isolation fix).Related
Related: #9846, #13154, #13106, #13183, #13185
Origin Session ID: 4cc428e3-cf36-4324-8646-1b96cb23fa4a