rapidkit 0.29.1 → 0.30.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -131,6 +131,7 @@ npx rapidkit create # Prompts: workspace | project
131
131
  npx rapidkit create workspace <name> [--profile <profile>] [--author <name>] [--yes]
132
132
  npx rapidkit bootstrap [--profile <profile>] [--json]
133
133
  npx rapidkit setup <python|node|go|java> [--warm-deps]
134
+ npx rapidkit analyze [--workspace <path>] [--json] [--strict] [--output <file>]
134
135
  npx rapidkit readiness [--json] [--strict]
135
136
  npx rapidkit autopilot release [--mode <audit|safe-fix|enforce>] [--json] [--output <file>] [--since <ref>] [--parallel] [--max-workers <n>]
136
137
  ```
@@ -267,6 +268,7 @@ RapidKit keeps the wrapper boundary explicit so users know which layer owns each
267
268
  | `workspace run` | Workspace orchestrator | Stage execution across discovered projects with optional affected-only, blast-radius expansion, and policy-gated pre-checks |
268
269
 
269
270
  Use `npx rapidkit doctor` for a quick host pre-flight, `npx rapidkit doctor project` for a service-level check, and `npx rapidkit doctor workspace` for the full workspace picture.
271
+ Use `npx rapidkit analyze --json` to generate CI-friendly workspace health evidence and save it under `.rapidkit/reports/`.
270
272
  Use `npx rapidkit doctor workspace --plan` or `npx rapidkit doctor project --plan` to preview remediation safely.
271
273
  Use `npx rapidkit doctor workspace --apply` or `npx rapidkit doctor project --apply` for non-interactive remediation runs.
272
274
  Use `npx rapidkit readiness` when you need machine-readable release evidence or strict CI gating.
@@ -580,6 +582,14 @@ npm run install:local
580
582
  npx rapidkit --version
581
583
  ```
582
584
 
585
+ > Packaging note: `npm run prepack` will regenerate `data/modules-embeddings.json` from the mock embeddings script before `npm pack` / `npm publish`.
586
+ >
587
+ > If you need to refresh the local test embeddings manually, run:
588
+ >
589
+ > ```bash
590
+ > npm run test:prepare-embeddings
591
+ > ```
592
+
583
593
  ## Troubleshooting
584
594
 
585
595
  ### Quick fixes matrix