CFEngine Build modules, and blocks for their promise types

[aleksandrychev]

Adds modules from the CFEngine Build index (build.cfengine.com) to the builder, and blocks for the promise types they provide.

Modules

• A VS Code-style activity bar switches the side bar between Blocks and files and a new Modules view: search (every word, old names too), tag chips, Supported only, "In this project" and "All modules".
• A module's page opens over the canvas, like on build.cfengine.com: README, links, maintainer, downloads, versions, tags. The details come from build.cfengine.com's own js/modules.json (what Mission Portal uses). The README becomes plain data rendered as React elements, never as HTML. Only GitHub images load (CSP img-src).
• Adding and removing modules, and answering their input (the Input tab, in Mission Portal's layout), are undoable project edits. Saving runs cfbs add / cfbs remove before writing anything else, and writes <module>/input.json. Modules run before the project's own policy. Policy sets only.
• Test runs build the project with its modules and their input.

Promise-type blocks

• Git Checkout, Systemd Unit, HTTP Request and Run Ansible Playbook, plus Custom Promise for any module's promise type (name = value attribute rows).
• Adding one adds its module. The module can't be removed while a block uses it.
• Notes on these become # Note: lines: promise modules refuse comment.
• The blocks advise installing python3, with buttons to add an Install python3 block before them or to ignore the advice for the project.
• The demo downloads the CFEngine logo with an HTTP Request and shows it on its landing page.

AI agents (MCP)

• New tools: search_modules, get_module, add_module, set_module_input, remove_module.
• The guide covers modules and these blocks.
• Two field tests with an agent without repository access built a project with modules and promise-type blocks; the second passed on a Debian 12 test host.

Tests

• Unit, component and main-process tests.
• An offline integration test: real sidecar and cfbs, with a local git module listed by a custom index.
• An offline e2e journey on fixture data (CFPB_MODULE_DATA, development builds only).
• Opt-in network and Docker journeys. The Docker one checks the demo's logo is served.

🤖 Generated with Claude Code