Releases: chistiq/rapidkit-npm
Release list
v0.42.3
Release Notes
Latest Release: v0.42.3 (July 25, 2026)
Secure Compatibility and Workspai Migration
This patch keeps the legacy rapidkit npm compatibility package safe and makes
the migration path to Workspai shorter and clearer. Runtime command behavior is
unchanged.
Security:
- Updated
brace-expansionto5.0.8to resolve the current high-severity
unbounded-expansion denial-of-service advisory. - Updated
postcssto8.5.23to resolve the current high-severity previous
source-map path traversal advisory. - Updated the compatible transitive
nanoiddependency selected by PostCSS. npm audit --audit-level=highreports zero vulnerabilities.
Migration and documentation:
- Replaced the feature-heavy README with a concise compatibility and migration
entry point. - Added a source-preserving migration guide for existing projects, named
workspaces, CI, agent/IDE consumers, verification, and rollback. - Added migration notices to user-facing legacy documentation so direct links
do not look like new-project onboarding. - Strengthened the docs drift and npm publish contracts around the legacy
package boundary.
Breaking changes: None.
Verification:
npm audit --audit-level=highnpm run check:brandnpm run validate:docsnpm testnpm run build
Upgrade:
npm install -g rapidkit@0.42.3New projects should install and use workspai instead.
v0.42.2
Release Notes
Latest Release: v0.42.2 (July 22, 2026)
Dependency Security Maintenance
This patch keeps the legacy compatibility CLI behavior unchanged while
refreshing its dependency lockfile against current npm security advisories.
Fixed:
- High-severity
brace-expansiondenial-of-service advisory. - High-severity
fast-urihost-confusion advisories. - High-severity
js-yamlquadratic CPU-consumption advisory.
Breaking changes: None.
Verification:
npm audit --audit-level=highnpm run validatenpm run build
Upgrade:
npm install -g rapidkit@0.42.2v0.42.1
Release Notes
Latest Release: v0.42.1 (July 9, 2026)
Workspai Migration Notice
This patch release keeps the legacy rapidkit npm package available while
making the migration path to Workspai explicit for new users.
What's New:
-
README migration guidance
- New installs are directed to the
workspainpm package. - The new repository is linked at
rapidkitlabs/workspai. - The legacy
rapidkitpackage is documented as a compatibility package that
is planned for deprecation in a future release.
- New installs are directed to the
-
CLI help migration guidance
npx rapidkit --helpnow prints a migration notice before the legacy command
reference so users who do not read the README still see the new path.
-
Contract bridge alignment
- Extension compatibility metadata points to
workspai@0.43.1. - Runtime/create-planner wording uses Workspai for the npm CLI ownership
surface.
- Extension compatibility metadata points to
Breaking changes: None.
Verification:
npm run validate:contractsnpm run buildnpm run test -- src/__tests__/index.test.tsnode dist/index.js --help
Upgrade:
npm install -g rapidkit@0.42.1v0.42.0
Release Notes
Latest Release: v0.42.0 (July 6, 2026)
Optional Python Engine and Profile Compatibility
This minor release separates Workspace Intelligence from the workspace-local
Python engine. Teams can now create governed workspaces first, model/adopt/import
projects, and install the local Python engine only when a RapidKit
module-enabled kit actually needs it.
What's New:
-
Optional Python engine for Python-aware profiles
create workspace --skip-python-enginekeepspython-only,polyglot, and
enterpriseworkspaces available for Workspace Intelligence without
installingrapidkit-coreimmediately.- Skipped workspaces record explicit
python_core.status = skippedmetadata
in workspace manifests, markers, and toolchain evidence. - Local launchers now explain the skip state and point users to npm-owned
workspace commands until the Python engine is intentionally installed.
-
Python-free workspace integrity
minimal,java-only,node-only,go-only, anddotnet-onlyworkspaces
no longer create root-levelpyproject.toml,poetry.toml,
.python-version, or.venvartifacts.- Empty skipped workspaces and arbitrary adopted/imported Python projects keep
the Python engine skipped unless a RapidKit module-enabled kit is present.
-
Module-enabled kit gate
- RapidKit module commands are guaranteed only for RapidKit-owned
module-enabled kits:fastapi.standard,fastapi.ddd, and
nestjs.standard. - Adopted/imported projects can still be modeled, governed, verified, and
surfaced in Workspace Intelligence even when module mutation is disabled.
- RapidKit module commands are guaranteed only for RapidKit-owned
-
Profile/runtime compatibility
create project,import,adopt, andbootstrapcompliance now share a
consistent profile compatibility policy.- Default mode warns and recommends profile realignment; strict mode blocks
mismatched runtime additions before registration. - Broader language/runtime signals such as Rust, C, and C++ are counted in the
workspace runtime mix even when RapidKit does not own a native scaffold.
Breaking changes: None.
Verification:
npm exec -- vitest run src/__tests__/e2e.test.ts src/__tests__/create-internal.test.ts src/__tests__/workspace-python-engine-install-gate.test.tsnpm run typecheck -- --pretty falsenpm run lintnpm run buildnpm exec -- vitest run
Upgrade:
npm install -g rapidkit@0.42.0v0.41.5
Release Notes
Latest Release: v0.41.5 (July 4, 2026)
Workspace Creation Location and Governance Gate Fixes
This patch release tightens workspace creation, Doctor workspace discovery, and
Workspace Verify exit-code behavior for Workspai, CI, and CLI users.
What's New:
-
Workspace creation location integrity
create workspacenow respects an explicitly selected target parent
(Current directory,--here, or--output <parent-dir>) when checking
duplicate workspace names.- A workspace with the same name in the managed home no longer blocks creating
another workspace in a different explicit parent directory. - Creating into an already-existing target path is still blocked.
-
Doctor empty workspace handling
doctor workspaceno longer treats an empty workspace shell as a project
just because the workspace root contains toolchain files such as
pyproject.tomlorpoetry.toml.- Empty workspace shells now report zero discovered projects and a workspace
discovery warning instead of misleading project health.
-
Workspace Verify exit codes
- Default-mode
needs-attentionverification now reports a passing gate with
exit code0. - Strict mode still fails non-ready verification as expected.
- Default-mode
Breaking changes: None.
Verification:
npm exec -- vitest run src/__tests__/workspace-create-location.test.tsnpm run typecheck -- --pretty falsenpm run build
Upgrade:
npm install -g rapidkit@0.41.5v0.41.4
Release Notes
Latest Release: v0.41.4 (July 2, 2026)
Cross-Artifact Studio Remediation Plan
This patch release adds a workspace-level repair contract for Workspai Studio and
agent consumers. Instead of scraping individual governance cards, npm can now emit
one ordered remediation plan across Bootstrap, Doctor, Analyze, Readiness, Pipeline,
Workspace Run, and Workspace Verify evidence.
What's New:
-
workspace remediation-plan- New command:
rapidkit workspace remediation-plan [--json] [--write] [--ci] [--include-paths] - Scans
.rapidkit/reports/and builds a Studio-ready action list with risk,
approval state, verify commands, and deterministic file operations where safe. --ciproduces stricter verify-oriented command plans where supported.
- New command:
-
artifact-remediation-plan.v1- New schema at
contracts/artifact-remediation-plan.v1.json - Persists to
.rapidkit/reports/artifact-remediation-plan-last-run.json - Bridges Doctor-specific plans with cross-card governance repair for dashboard
and Studio handoff consumers.
- New schema at
-
Published contract surface
- Added to
runtime-command-surface.v1,extension-cli-compatibility.v1,
agent-customization-pack.v1, workspace model evidence refs, and agent-sync
catalog entries. - Operational skills now direct agents to read the artifact remediation plan
before per-card improvisation.
- Added to
Breaking changes: None.
Verification:
npm run typechecknpm run validate:contractsnpm testnpm run smoke:enterprise-packagenpm run prepack
Upgrade:
npm install -g rapidkit@0.41.4v0.41.3
Release Notes
Latest Release: v0.41.3 (July 2, 2026)
Enterprise Doctor Evidence and Studio Remediation Contracts
This patch release hardens RapidKit's npm source-of-truth layer for Workspai
Studio, enterprise workspace governance, and agent-facing evidence. Doctor now
emits deeper multi-language, multi-framework project signals; repair planning is
structured as an ordered remediation contract; and Workspace Intelligence
artifacts carry fact-level freshness metadata so humans and agents know which
facts are durable, derived, evidence-backed, live, or verification-gated.
What's New:
-
Enterprise Doctor evidence
doctor workspace,doctor workspace --fix,doctor project, and
doctor project --fixnow inspect broader project surfaces: dependency
contracts, env/config baselines, tests, quality tooling, security tooling,
container/deployment files, migrations, health probes, and runtime
entrypoints.- Doctor output is more reliable across frontend, backend, and polyglot
workspaces, with canary coverage for multi-stack scenarios.
-
Studio-ready remediation
- New
doctor-remediation-plan.v1contract describes ordered safe and guarded
repair steps, file hints, verification commands, rollback metadata, and
repair capability state. - Doctor repair capabilities now favor the smallest safe edit first while
keeping higher-risk steps review-gated for Workspai Studio.
- New
-
Fact freshness
- New
fact-freshness.v1contract extends freshness from artifact-level
metadata down to the facts that agents actually reason over. - Workspace context, model, history, verify, and agent-sync outputs now expose
the newer freshness and remediation evidence in structured form.
- New
-
Enterprise CLI gates
- CLI routing and release gates are hardened around npm-vs-Python RapidKit
command ownership, package smoke, manual release workflows, and Studio-safe
repair command execution.
- CLI routing and release gates are hardened around npm-vs-Python RapidKit
Breaking changes: None.
Verification:
npm run typechecknpm run validate:contractsnpm testnpm run smoke:enterprise-packagenpm run prepack
Upgrade:
npm install -g rapidkit@0.41.3v0.41.2
Release Notes
Latest Release: v0.41.2 (June 28, 2026)
Workspace Intelligence Contract and Publish Smoke Hardening
This patch release tightens the npm source-of-truth layer for Workspai,
enterprise CI, and agent-facing workspace operations. It expands the published
Workspace Intelligence command surface, adds structured incident handoff
metadata for Studio consumers, hardens package smoke against noisy npm output
and read-only npm caches, and clarifies RapidKit's category positioning in the
README.
What's New:
-
Workspace Intelligence command surface
runtime-command-surface.v1now advertisesworkspace whyand
workspace traceas Workspace Intelligence subcommands alongside
workspace explain.- Contract tests now assert
explain,why, andtracestay published for
IDE/CI capability detection.
-
Studio incident handoff
studio-blocker-handoff.v1now includes an additiveincidentSummary
object for phase, primary action, verification requirement, and audit state.
-
Enterprise package smoke
enterprise-package-smokenow uses an isolated writable npm cache instead
of inheriting a possibly read-only parentnpm_config_cache.- The smoke parser now tolerates npm lifecycle noise before
npm pack --json
output.
-
Workspace Intelligence docs and positioning
- README positioning now leads with Open-Source Workspace Intelligence for
Software Systems and clarifies that RapidKit is not another AI coding
assistant, agent framework, or context engine. - The mental model now makes Workspace Intelligence framework-agnostic:
RapidKit can govern created, imported, and adopted projects across frontend,
backend, and polyglot stacks. - Contract docs now list the newer Workspace Intelligence schemas and fix the
.rapidkit/AGENT-GROUNDING.mdartifact path.
- README positioning now leads with Open-Source Workspace Intelligence for
-
Graph impact quality
- Workspace impact centrality handling no longer relies on non-null
assertions when building transitive impact and hotspot summaries.
- Workspace impact centrality handling no longer relies on non-null
Breaking changes: None.
Verification:
npm run lintnpm run typechecknpm run format:checknpm run validate:docsnpm run check:generated-contractsnpm run check:shared-contractsnpm test(1573 passed, 8 skipped)npm run smoke:enterprise-packagenpm run prepack
Upgrade:
npm install -g rapidkit@0.41.2v0.41.1
Release Notes
Latest Release: v0.41.1 (June 28, 2026)
Enterprise Package Smoke and Runner Hardening
This patch release hardens the npm CLI for enterprise extension hosts, CI, and
publish gates: package runners no longer depend on a perfect PATH, piped CLI
output is safe before process exit, workspace-root init uses the same npm-aware
preflight as project lifecycle commands, and npm package smoke now blocks
publishing on broken artifacts.
What's New:
-
Publish gates
prepacknow builds dist, prepares packaged embeddings, verifies CLI command
ownership, and runs enterprise package smoke beforenpm pack/ publish.- CI and manual release workflows run
smoke:enterprise-package.
-
Package runner hardening
- npm/npx/pnpm/yarn subprocesses resolve through a command-safe invocation
contract (npm_execpath, well-known npm CLI paths, orcorepack npm). - Nested
npx --packageenvironment pins are stripped before child package
runners execute. COREPACK_HOMEis made writable for package-runner subprocesses.
- npm/npx/pnpm/yarn subprocesses resolve through a command-safe invocation
-
Pipe-safe CLI output
- Piped stdout/stderr is written synchronously for CLI entrypoint execution so
--version --json, workspace policy, cache, and lifecycle command output are
not lost on fast exits.
- Piped stdout/stderr is written synchronously for CLI entrypoint execution so
-
Workspace Intelligence graph
workspace-dependency-graph.v1now carries richer operational profile,
coverage, topology, and diagnostics data for Workspai enterprise graph
surfaces.
-
Scaffold/runtime stability
- Frontend create commands and Node runtime package-manager detection use the
same package-runner contract. - Workspace fleet init preflight accepts npm runners resolved outside PATH,
matching project-level lifecycle execution.
- Frontend create commands and Node runtime package-manager detection use the
Breaking changes: None.
Verification:
./node_modules/.bin/tsc --noEmit./node_modules/.bin/vitest run(1573 passed, 8 skipped)node scripts/enterprise-package-smoke.mjsnode scripts/prepack-enterprise.mjs
Upgrade:
npm install -g rapidkit@0.41.1v0.41.0
Release Notes
Latest Release: v0.41.0 (June 23, 2026)
Phase 4 Workspace Intelligence Closure
This minor release completes the operational intelligence loop: human-readable
blocker narratives, agent feedback, MCP read bridge, operational skills, structured
doctor-fix evidence, and extended verify + fleet-run gates — all versioned for
Workspai, CI, and AI agents.
What's New:
-
Explain / Why / Trace
workspace explain,workspace why, andworkspace trace --from <diff>with
workspace-explain.v1artifact.
-
MCP serve
- Read-mostly stdio JSON-RPC:
workspace mcp serve.
- Read-mostly stdio JSON-RPC:
-
Agent feedback & skills
workspace feedback record→ history ring buffer.- Operational skills via
workspace agent-sync --write(no separate generator).
-
Doctor fix result
- Structured
fixResultondoctor workspace --fix --json
(rapidkit-doctor-fix-result-v1).
- Structured
-
Verify & fleet extensions
- Verify init/start fleet evidence + optional doctor-fix step.
- Resolution hints on blocking steps.
workspace runcustom stages,--reuse-passed, stage dependencies.
-
Contracts
- Nine new/updated Phase 4 schemas; extension CLI compatibility matrix expanded.
Breaking changes: None.
Upgrade:
npm install -g rapidkit@0.41.0