@boopkit/cli 0.1.14 → 0.1.16

package/dist/capability-versions.json

@@ -1,9 +1,9 @@
 {
   "@boopkit/cap-api": "0.1.0",
-  "@boopkit/cap-background-jobs": "0.2.0",
+  "@boopkit/cap-background-jobs": "0.2.6",
   "@boopkit/cap-cloud-storage": "0.1.0",
   "@boopkit/cap-coding": "0.1.0",
-  "@boopkit/cap-database": "0.1.3",
+  "@boopkit/cap-database": "0.1.4",
   "@boopkit/cap-email": "0.1.0",
   "@boopkit/cap-hello": "0.1.0",
   "@boopkit/cap-noticeboard": "0.1.1",

package/dist/cli.js

@@ -89,6 +89,7 @@ program
     .option('--restore', 'Restore locally deleted scaffold files')
     .option('--prune', 'Remove deprecated scaffold files from disk (creates .bak backup)')
     .option('--skip-npm', 'Skip npm update (only re-scaffold from installed versions)')
+    .option('--tag <tag>', 'Use a specific npm dist-tag instead of major-version pinning (e.g. beta)')
     .option('--json', 'Output structured JSON')
     .action(update_1.runUpdate);
 program

package/dist/commands/list.js

@@ -61,7 +61,7 @@ function listProfilesCommand() {
  * Reused by both `boop list capabilities` and `boop add` (no arg).
  */
 function printGroupedCapabilities() {
-    const capabilities = (0, capability_1.listCapabilities)().filter(c => !c.name.startsWith('_'));
+    const capabilities = (0, capability_1.listCapabilities)();
     if (capabilities.length === 0) {
         console.log('No capabilities found.');
         return;

package/dist/commands/status.js

@@ -117,11 +117,10 @@ function getStatusData(manifest, dir) {
             }
         }
         if (allRequiredSet) {
-            // Env vars are set — check if capability has setup checks or postInstall steps
+            // Env vars are set — check if capability has setup checks that enrichWithSetupChecks can resolve
             const capDef = (0, capability_1.getCapability)(capName, [dir]);
             const hasSetupChecks = capDef?.postInstall?.setupChecks?.length;
-            const hasPostInstall = capDef?.postInstall && (capDef.postInstall.steps?.length || capDef.postInstall.verify);
-            if (hasSetupChecks || hasPostInstall) {
+            if (hasSetupChecks) {
                 // Mark as 'setup' — dynamic checks will populate steps during enrichment
                 capabilities[capName] = { status: 'setup', type: capType, env: envStatus, optionalSteps: optionalSteps.length > 0 ? optionalSteps : undefined };
             }

package/dist/commands/update.d.ts

@@ -5,5 +5,6 @@ export interface UpdateOptions {
     prune?: boolean;
     json?: boolean;
     skipNpm?: boolean;
+    tag?: string;
 }
 export declare function runUpdate(capabilityName: string | undefined, options: UpdateOptions): void;

package/dist/commands/update.js

@@ -61,7 +61,7 @@ function runUpdate(capabilityName, options) {
     }
     // Step 1: npm install capability packages at latest within current major (unless --skip-npm or --dry-run)
     if (!options.skipNpm && !options.dryRun) {
-        const packageSpecs = resolveNpmPackageSpecs(capsToUpdate, targetDir);
+        const packageSpecs = resolveNpmPackageSpecs(capsToUpdate, targetDir, options.tag);
         if (packageSpecs.length > 0) {
             if (!options.json) {
                 console.log(`Updating npm packages: ${packageSpecs.join(', ')}`);
@@ -224,7 +224,7 @@ function diagnoseMissingPlans(capsToUpdate, requestedCap, targetDir) {
  * This allows minor+patch updates within the same major (including 0.x → 0.y)
  * without crossing a major version boundary.
  */
-function resolveNpmPackageSpecs(capabilities, targetDir) {
+function resolveNpmPackageSpecs(capabilities, targetDir, tag) {
     const specs = [];
     for (const cap of capabilities) {
         const pkgDir = (0, capability_1.getPackageDir)(cap, [targetDir]);
@@ -235,8 +235,13 @@ function resolveNpmPackageSpecs(capabilities, targetDir) {
             continue;
         const pkgJson = JSON.parse(fs.readFileSync(pkgJsonPath, 'utf-8'));
         if (pkgJson.name && pkgJson.boopkit?.capability && pkgJson.version) {
-            const major = pkgJson.version.split('.')[0];
-            specs.push(`${pkgJson.name}@${major}`);
+            if (tag) {
+                specs.push(`${pkgJson.name}@${tag}`);
+            }
+            else {
+                const major = pkgJson.version.split('.')[0];
+                specs.push(`${pkgJson.name}@${major}`);
+            }
         }
     }
     return specs;

package/dist/lib/capability.d.ts

@@ -16,7 +16,9 @@ export declare function getCatalogEntry(name: string): (CapabilityMetadata & {
  * List all capabilities by scanning package directory and capabilities/ source tree (test fixtures only).
  * Package resolution takes priority. Returns metadata for each valid capability.
  */
-export declare function listCapabilities(): CapabilityMetadata[];
+export declare function listCapabilities(opts?: {
+    includeTest?: boolean;
+}): CapabilityMetadata[];
 /**
  * Get a single capability's metadata by name.
  * Tries package resolution first, falls back to source tree.

package/dist/lib/capability.js

@@ -140,13 +140,14 @@ function getCatalogEntry(name) {
  * List all capabilities by scanning package directory and capabilities/ source tree (test fixtures only).
  * Package resolution takes priority. Returns metadata for each valid capability.
  */
-function listCapabilities() {
+function listCapabilities(opts) {
+    const includeTest = opts?.includeTest ?? false;
     const seen = new Set();
     const capabilities = [];
     // Primary source: baked-in catalog (always available in published CLI)
     const catalog = loadCatalog();
     for (const cap of catalog) {
-        if (cap.name.startsWith('_'))
+        if (!includeTest && cap.name.startsWith('_'))
             continue;
         seen.add(cap.name);
         // Also track the package short name (e.g. "users" from "@boopkit/cap-users")
@@ -174,6 +175,8 @@ function listCapabilities() {
             if ((!entry.isDirectory() && !entry.isSymbolicLink()) || !entry.name.startsWith('cap-'))
                 continue;
             const capName = entry.name.replace(/^cap-/, '');
+            if (!includeTest && capName.startsWith('_'))
+                continue;
             if (seen.has(capName))
                 continue;
             const cap = getCapabilityFromPackage(capName, [process.cwd()]);
@@ -190,6 +193,8 @@ function listCapabilities() {
         for (const entry of entries) {
             if (!entry.isDirectory())
                 continue;
+            if (!includeTest && entry.name.startsWith('_'))
+                continue;
             if (seen.has(entry.name))
                 continue;
             const cap = getCapabilityFromSourceTree(entry.name);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@boopkit/cli",
-  "version": "0.1.14",
+  "version": "0.1.16",
   "description": "CLI tool to scaffold new projects from boop profiles and capabilities",
   "main": "dist/cli.js",
   "workspaces": [
@@ -19,6 +19,8 @@
   },
   "scripts": {
     "build": "tsc && node tools/generate-version-manifest.js",
+    "build:caps": "./tools/build-caps.sh",
+    "publish" : "./tools/publish-caps.sh",
     "dev": "tsx src/cli.ts",
     "start": "node dist/cli.js",
     "test": "jest"

package/src/templates/kernel/AGENTS.md.hbs

@@ -2,17 +2,17 @@
 
 This is a **boop**-managed project. Use boop commands — don't reinvent what boop already provides.
 
-## Getting Started
+## Conversational style
+When the user asks a question, it is for informational purpose and not a veiled request for action. Unless the user says a colloquially phrased command like "can you write a test for X" or "can you add a database", you should not take any action.  If the user wants you to do something, they will ask you to do it directly.
 
-1. Run `boop status` to see what needs configuration
-2. Follow the setup hints to configure your environment
-3. Run `npm run dev` to start the development server
+Don't confirm a hypothesis (or take action) without observation - logs, tests, and other data are your friends. If you don't have the information you need to answer a question, find it (eg. run db queries, look at logs, add more logging, etc.) or ask for it instead of guessing.
 
 ## How to work in this project
 
-1. **Check skills first.** Before coding, reviewing, testing, or designing, check [skills/index.md](skills/index.md) for a matching skill and follow its process. Do not rely on general knowledge when a project skill exists.
-2. **Use boop for capabilities.** To add features like database, auth, or other infrastructure, run `boop add <capability>` — don't install or wire things manually. Run `boop caps` to see what's available.
-3. **Check project status.** Run `boop status` to see what's configured and what needs attention.
+0. **Read the skills index now.** Open [skills/index.md](skills/index.md) before doing anything else in this session. You need to know what skills exist before you can apply rule 1.
+1. **Check skills first.** Before coding, reviewing, testing, designing, debugging, filing issues, or proposing any non-trivial change, check [skills/index.md](skills/index.md) for a matching skill and follow its process. Do not rely on general knowledge when a project skill exists.
+2. **Use boop for capabilities.** Run `boop caps` to see what's available. To add features like database, auth, or other services and infrastructure, run `boop add <capability>` — don't install or wire things manually.
+3. **Check project status.** If the system isn't working or new capabilities need to be added run `boop status` to see what's configured and what needs attention.
 4. **Run `boop --help`** for the full command list.
 
 ## Boop extension model