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.

Neo.mjs - Self-Evolving Software Organism

ad1tyayadav commented on Oct 27, 2025, 2:47 PM

Closes #7476

What kind of change does this PR introduce? (check at least one)

Bugfix
Feature
Code style update
Refactor
Build-related changes
Other, please describe: Test Plan Documentation

Does this PR introduce a breaking change? (check one)

Yes
No

If yes, please describe the impact and migration path for existing applications:

The PR fulfills these requirements:

It's submitted to the dev branch, not the main branch
I have read the Contributing Guidelines

If adding a new feature, the PR's description includes:

A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

Other information:

This PR adds a comprehensive test plan for the Neo.form.field.Password component as part of the Hacktoberfest Cookbook initiative. The test plan was generated following the AI-Native workflow outlined in epic #7475 and covers:

Inherited behavior from Text field
Password-specific functionality (input masking, security)
Accessibility requirements
Validation and interaction tests

The test plan serves as the foundation for future implementation of Playwright component tests and follows the project's established format for test planning.

tobiu commented on Oct 27, 2025, 2:56 PM

thx. i will convert it into a new ticket (our internal file naming for local tickets changed, now that the 2-way sync is in place).

tobiu commented on Oct 27, 2025, 3:01 PM

here: https://github.com/neomjs/neo/issues/7677 => in case you want to pick it up, please add a comment on the issue.

title	Create test plan for form.field.Password component
author	ad1tyayadav
state	Merged
createdAt	Oct 27, 2025, 2:47 PM
updatedAt	Oct 27, 2025, 3:01 PM
closedAt	Oct 27, 2025, 2:56 PM
mergedAt	Oct 27, 2025, 2:56 PM
branches	`dev` ← `test-plan-password-field`
url	https://github.com/neomjs/neo/pull/7676