LazyBrain 2.1.0: Codex Desktop capability router

[papperrollinggery]

Outcome

Repositions LazyBrain around Codex Desktop: index local Skills, Plugins, MCP servers, agents, and commands; turn vague tasks into explainable recommendations and safe workflows; provide a versioned @visualize decision-explorer payload with an accessible fallback.

Key changes

• Codex Desktop plugin, bundled Skill, read-only MCP recommendation surface
• Plugin and MCP discovery in the local capability index
• Interactive desktop visualization contract with explicit composer activation
• Untrusted metadata bounding and Markdown/prompt-injection defenses
• Product/SEO README, Chinese README, use cases, privacy, install and desktop docs
• Node 18/20/22 CI and release matrix, packed-install smoke, plugin/Skill validation
• 2.1.0 version alignment and dependency audit hardening

Verification

• lint/build PASS
• 157 tests PASS on current Node and Node 18
• npm audit: 0 vulnerabilities
• public package audit and packed install smoke PASS
• Codex Plugin and Skill validators PASS
• installed LazyBrain Codex Desktop plugin/MCP readback PASS
• independent cold review PASS

Desktop boundary

@visualize is an OpenAI preview. It must be selected by the user in the Codex Desktop composer for the current task. LazyBrain falls back to an accessible Markdown table and exact reusable prompt when the host does not expose it; selection never executes a capability.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: a408336cd2

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Do not mark marketplace-only plugins installed

When scanning a Codex marketplace file, this converts every catalog entry into a normal plugin capability; rawToCapability then defaults every non-disabled raw capability to status: 'installed'. In the common state after adding a marketplace but before actually installing a plugin, those entries are only available, so lb compile/recommendations can suggest a plugin the user cannot use yet. The parser should either preserve an available status from marketplace entries or skip entries that are not installed.

Useful? React with 👍 / 👎.