@aifabrix/builder 2.43.0 → 2.44.0

package/.cursor/rules/anchor-docs.mdc

@@ -0,0 +1,15 @@
+---
+description: Mandatory structure for Builder CLI anchor-docs.
+globs: anchor-docs/**/*.md
+alwaysApply: false
+---
+
+# anchor-docs (Builder)
+
+When editing `anchor-docs/**/*.md` (only `README.md` is exempt). Copy `anchor-docs/_TEMPLATE` to create a new anchor (no `.md` extension — not validated):
+
+- Include YAML frontmatter: `title`, `navigation_id`, `owner`, `last_verified_commit`.
+- `navigation_id` must match **aifabrix-docs** `docs/builder/navigation.yaml` entries (`builder/<url>`).
+- Sections required: `## Summary`, `## Details`, `## Examples`, `## Paths`.
+- Reference repo files with **`[path:aifabrix-builder/...]`**; avoid backtick-only paths for the same references.
+- Align with CLI user-doc rules: keep HTTP/API endpoint names out of `docs/commands/` user text; technical anchors may cite code paths.

package/README.md

@@ -48,7 +48,7 @@ Get the platform running locally so you can try it.
    aifabrix up-infra
    ```
 
-   First-time run creates required infra secrets automatically. Use `aifabrix up-infra --adminPwd <password>` to set a custom admin password for Postgres, pgAdmin, and Redis Commander.
+   First-time run creates required infra secrets automatically. Use `aifabrix up-infra --adminPassword <password>` to set a custom admin password for Postgres, pgAdmin, and Redis Commander.
 
 2. **Start the platform** (Keycloak, Miso Controller, Dataplane) from community images:
 

package/anchor-docs/README.md

@@ -0,0 +1,10 @@
+# anchor-docs (Builder CLI)
+
+Canonical technical notes for the AI Fabrix Builder. Command references, JSON schemas, and generator entrypoints live here; **aifabrix-docs** `docs/builder/` should only summarize and link.
+
+## Conventions
+
+* Copy `anchor-docs/_TEMPLATE` to a new `*.md` file and fill in placeholders (the template is not `.md`, so it is not validated as an anchor).
+* `navigation_id` must match **aifabrix-docs** `docs/builder/navigation.yaml` (`builder/<url>`).
+* Use **`[path:aifabrix-builder/...]`** markers only.
+* PRs touching anchors should request review from the `owner` team.

package/anchor-docs/_TEMPLATE

@@ -0,0 +1,24 @@
+# Copy this file to `your-topic.md` and replace placeholders. This is not `*.md` so it is not validated as an anchor-doc.
+
+---
+title: <Title>
+navigation_id: builder/<slug-from-navigation.yaml>
+owner: <team>
+last_verified_commit: <sha-or-TBD>
+---
+
+## Summary
+
+<What this anchor covers for Builder CLI or schemas.>
+
+## Details
+
+<Implementation notes; keep persona docs in aifabrix-docs thin.>
+
+## Examples
+
+<aifabrix wizard|validate|deploy ...>
+
+## Paths
+
+[path:aifabrix-builder/README.md]

package/bin/aifabrix.js

@@ -28,14 +28,23 @@ function initializeCLI() {
 
   program.name('aifabrix')
     .version(packageJson.version)
-    .description('AI Fabrix Builder – Help and documentation');
+    .description(
+      'Local Docker infra, app scaffolding, validation, and deploy to Azure (or local) via Miso Controller'
+    );
 
   // Delegate command setup to lib/cli.js (order matches help categories for consistency)
   cli.setupCommands(program);
 
-  // Use categorized help for a more user-friendly command list
+  // Custom help replaces Commander default; append footer here (program.addHelpText is not applied)
+  const ROOT_HELP_FOOTER = `
+
+More:
+  aifabrix <command> --help    Options and examples for one command
+  docs/commands/README.md     Command reference in the repo
+`;
+
   program.helpInformation = function() {
-    return buildCategorizedHelp(program);
+    return buildCategorizedHelp(program) + ROOT_HELP_FOOTER;
   };
 
   // Parse command line arguments
@@ -51,7 +60,7 @@ if (require.main === module) {
   try {
     initializeCLI();
   } catch (error) {
-    logger.error('❌ Failed to initialize CLI:', error.message);
+    logger.error('✖ Failed to initialize CLI:', error.message);
     process.exit(1);
   }
 }

package/integration/hubspot-test/README.md

@@ -8,6 +8,37 @@ HubSpot CRM integration with OpenAPI support for companies, contacts, and deals
 - **System Type**: `openapi`
 - **Datasources**: 4
 
+## Regenerating files with the CLI (recommended)
+
+Datasource and system JSON under this folder are **normally produced by the Builder**, not edited by hand for structural/schema changes. Use one of these flows (from the **repository root**):
+
+1. **Interactive wizard** (writes to `integration/hubspot-test/` when the app key is `hubspot-test`):
+
+   ```bash
+   aifabrix wizard hubspot-test
+   ```
+
+2. **Headless wizard – known platform HubSpot** (same folder; needs dataplane + auth):
+
+   ```bash
+   node bin/aifabrix.js wizard \
+     --config integration/hubspot-test/wizard-hubspot-test-headless.yaml \
+     --controller <YOUR_CONTROLLER_URL> \
+     --environment <YOUR_ENV>
+   ```
+
+   Edit `deployment.controller` / `deployment.environment` in that YAML if you prefer not to pass flags.
+
+3. **Helper script** (generates a temporary wizard config and runs the CLI; defaults OpenAPI to `companies.json` in this directory):
+
+   ```bash
+   node integration/hubspot-test/create-hubspot.js --name hubspot-test --keep-wizard-files
+   ```
+
+After regeneration, run `aifabrix validate hubspot-test --type external` and the HubSpot integration tests as needed.
+
+Committed copies may still be **trimmed or adjusted** for repo tests (e.g. deterministic fields); prefer changing **generators/templates** in `lib/` and `templates/` when defaults should change for everyone.
+
 ## Files
 
 - `application.yaml` – Application configuration with `app` and `externalIntegration` blocks

package/integration/hubspot-test/create-hubspot.js

@@ -404,7 +404,7 @@ async function executeWizard(args) {
     args.controller,
     args.environment
   );
-  logSuccess(`✓ Created config: ${configPath}`);
+  logSuccess(`✔ Created config: ${configPath}`);
 
   logInfo('\n2. Running wizard...');
   const wizardResult = await runWizard(configPath, args.controller, args.environment);
@@ -420,7 +420,7 @@ async function executeWizard(args) {
     throw new Error('Wizard execution failed');
   }
 
-  logSuccess('✓ Wizard completed successfully');
+  logSuccess('✔ Wizard completed successfully');
   return configPath;
 }
 
@@ -444,7 +444,7 @@ async function processGeneratedFiles(args) {
   if (outputDir !== wizardOutputDir) {
     logInfo(`\n4. Copying files to: ${outputDir}`);
     const copiedFiles = await copyDirectoryContents(wizardOutputDir, outputDir);
-    logSuccess(`✓ Copied ${copiedFiles.length} files`);
+    logSuccess(`✔ Copied ${copiedFiles.length} files`);
   } else {
     logInfo(`\n4. Files are in: ${outputDir}`);
   }
@@ -462,7 +462,7 @@ async function processGeneratedFiles(args) {
  * @returns {Promise<void>} Resolves when summary is printed
  */
 async function printSummary(outputDir, appName, environment) {
-  logSuccess('\n✓ HubSpot integration created successfully!');
+  logSuccess('\n✔ HubSpot integration created successfully!');
   logger.log('\nGenerated files:');
   const files = await listFiles(outputDir);
   for (const file of files) {
@@ -490,7 +490,7 @@ async function cleanupFiles(configPath, wizardOutputDir, outputDir, keepWizardFi
   if (!keepWizardFiles && outputDir !== wizardOutputDir) {
     logInfo('\n5. Cleaning up wizard files...');
     await fs.rm(wizardOutputDir, { recursive: true, force: true });
-    logSuccess('✓ Cleaned up wizard files');
+    logSuccess('✔ Cleaned up wizard files');
   }
 
   await fs.unlink(configPath).catch(() => {