What is the Neural Link?

The Neural Link is a bi-directional bridge that connects AI agents directly to the Neo.mjs runtime. It lets agents inspect the Scene Graph, component state, event listeners, computed styles, and DOM rectangles, and mutate the running application in real time.

Why is Neo.mjs called an Application Engine instead of a framework?

Neo.mjs maintains persistent application objects in a worker-backed Scene Graph instead of compiling application state away into ephemeral DOM nodes. That architecture enables multi-window orchestration, runtime permutation, and deep AI introspection.

What is Context Engineering?

Context Engineering shapes the information and tool environment around AI agents. Neo.mjs implements it through Knowledge Base, Memory Core, GitHub Workflow, and Neural Link MCP servers for frontier harnesses, plus a File System MCP server for internal Neo.ai.Agent local loops.

What is the Neo.mjs Agent OS?

The Neo.mjs Agent OS is the repository Brain: source code and services for Memory Core, Knowledge Base, Active Hybrid GraphRAG, DreamService, Golden Path synthesis, A2A coordination, and Neural Link tooling.

Frontmatter

id	7289
title	Convert state/ProviderNestedDataConfigs.mjs Test from Siesta to Playwright
state	Closed
labels	enhancementhelp wantedgood first issuehacktoberfest
assignees	kart-u
createdAt	Sep 27, 2025, 4:02 PM
updatedAt	Oct 4, 2025, 5:23 PM
githubUrl	https://github.com/neomjs/neo/issues/7289
author	tobiu
commentsCount	5
parentIssue	7262
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Oct 4, 2025, 5:10 PM

Convert state/ProviderNestedDataConfigs.mjs Test from Siesta to Playwright

Closed v11.0.0/archive-v11-0-0-chunk-1 enhancementhelp wantedgood first issuehacktoberfest

tobiu commented on Sep 27, 2025, 4:02 PM

This task is to migrate the unit test for state/ProviderNestedDataConfigs.mjs from the Siesta test harness to the Playwright test runner.

Acceptance Criteria

Create a new test file at test/playwright/unit/state/ProviderNestedDataConfigs.spec.mjs.
Translate all assertions from the original file (test/siesta/tests/state/ProviderNestedDataConfigs.mjs) to the Playwright/Jest expect syntax.
Ensure the new test runs successfully via npm test.
The new test must cover all the functionality of the original Siesta test.

tobiu added parent issue #7262 on Sep 27, 2025, 4:02 PM

tobiu added the enhancement label on Sep 27, 2025, 4:02 PM

tobiu Oct 3, 2025, 6:13 PM

Hi and thanks for your interest. For the testing tickets, I strongly recommend trying out the "ai native" workflow.

I would read the hacktoberfest intro first: https://github.com/neomjs/neo/issues/7296

Then the following 2 guides: https://github.com/neomjs/neo/blob/dev/.github/WORKING_WITH_AGENTS.md https://github.com/neomjs/neo/blob/dev/.github/AI_QUICK_START.md

e.g. gemini cli should be capable to complete it on its own.

2025-10-04T09:45:35Z @kart-u cross-referenced by PR #7347
2025-10-04T09:58:12Z @kart-u cross-referenced by PR #7350
2025-10-04T10:31:18Z @kart-u cross-referenced by PR #7351
2025-10-04T12:23:03Z @kart-u cross-referenced by #7286

tobiu Oct 4, 2025, 4:49 PM

reopening to fix the class definition to prevent breaking tests.

tobiu Oct 4, 2025, 5:10 PM

i added a comment to the PR. i merged it anyways => i am not that strict to first-time contributors :)

there was a hint about this in the epic. this is why i pointed out to tell gemini to read it first, smoothening your workflow.

@kart-u - 2025-10-04T15:23:05Z

thank you for your understanding :)

2026-09-05T13:24:51Z @neo-fable cross-referenced by #18361