Pin the legend component's icon and text

[!NOTE] Held in the #18985 reserve: not open for claiming yet. Curated issues are released in batches as review capacity frees up. Please pick an issue labelled good first issue instead. This one is also being moved to the component tier first: it tests something a human looks at, and #18985's tier rule sends those to a real browser.

Welcome 👋

Every form fieldset in Neo has a <legend> at its top: Neo.component.Legend, an optional check icon followed by a title. Three reactive configs (iconCls, useIcon, text) each change one part of its virtual DOM. It is the smallest complete example of a Neo component reacting to its configs, and it has no test.

This is a good first issue for Hacktoberfest 2026. It needs Node.js and a clone of this repository: no Docker, no AI setup.

[!IMPORTANT] Reserved for first-time Neo.mjs contributors. The maintainer team will not claim, edit, or implement this issue through 2026-10-31. Comment here to claim it, and ask anything on this issue.

Set up once: follow Set up the engine from a clone, including npm run bundle-browser-deps: without it the unit suite selects zero tests.

Where things live

• Source: src/component/Legend.mjs. vdom.cn[0] holds the icon markup and vdom.cn[1] the text. It is used by src/form/Fieldset.mjs.
• New test file: test/playwright/unit/component/Legend.spec.mjs
• Pattern to copy: test/playwright/unit/component/Progress.spec.mjs (creating a component with Neo.create() in a unit test)

What to cover

Done when

• test/playwright/unit/component/Legend.spec.mjs exists, following the pattern file's setup.
• One test(...) per table row.
• Test-only: if the component disagrees with a row, say so on this issue before changing src/.
• npm run test-unit -- test/playwright/unit/component/Legend.spec.mjs passes.
• npm run test-unit passes.

Out of scope

Fieldset itself, and styling.

While you wait for review

You just pinned one small piece of a multi-threaded application engine: in Neo.mjs your app's code runs inside a web worker, and the main thread only paints. Two things worth ten minutes:

• See the part nobody expects. Run npm run build-themes -- -n -e dev -t all and npm run server-start, open apps/workstation/, and drag a tab out of the browser window. It becomes its own OS window, still running, with the same component instances and the same worker. Benefits: Introduction explains why that is possible.
• Your coding agent can go much further here. The skills this repository's AI maintainers work with are published on npm as neo-agent-skills, and they need no Knowledge Base and no Memory Core. With Claude or GPT beside you, the help wanted issues are within reach after this one.