@ccdd/core 6.1.0 → 6.2.1

package/README.md

@@ -40,10 +40,11 @@ These relationships define required input, verification and default dependency-G
 Use Node.js 22 LTS, version 22.19.0 or later.
 
 ```sh
-npm install --ignore-scripts @ccdd/core@6.1.0 @ccdd/project@6.1.0
+npm install --ignore-scripts @ccdd/ccdd
+# or: pnpm add --ignore-scripts @ccdd/ccdd
 ```
 
-This single command installs the definitions and Project runtime, including their dependencies. Common view tools are optional and installed separately; see [installation choices](docs/getting-started.md#installation-choices).
+The single public package installs exact matching core, Project and default-tools modules as normal dependencies. Its `ccdd`, `ccdd-project` and `ccdd-view` commands delegate to those modules. Use `@ccdd/ccdd/core`, `/project` and `/tools` imports; see [installation choices](docs/getting-started.md#installation-choices).
 
 Inside an Artifact folder, create `ccdd.json`:
 
@@ -92,6 +93,7 @@ The optional local monitor shows folders, relationships, cycles, review progress
 
 | Package | Responsibility |
 | --- | --- |
+| `@ccdd/ccdd` | Single-install entrypoint, public module subpaths and CLI delegates. |
 | `@ccdd/core` | Public definitions and logical path resolution. |
 | `@ccdd/project` | Validation, CLI, Broker, Executors and monitor. |
 | `@ccdd/default-tools` | Optional common view scripts; no automatic registration. |
@@ -102,7 +104,22 @@ See [Contributing](CONTRIBUTING.md), [the context map](CONTEXT-MAP.md), [detaile
 
 [MIT](LICENSE).
 
-**CCDD 6.1.0:** adds shared machine resource admission, durable execution budgets, pinned runtime provenance and guarded load checks, with native Pi model catalogs. See the [release notes](docs/releases/v6.1.0.md) and [upgrade steps](docs/releases.md#upgrading-to-61). Stop old workers before upgrading; completed format-6 evidence remains reusable.
+**CCDD 6.2.1:** existing timeout declarations accept 20 minutes without arbitrary policy ceilings. Values remain bounded by Node timer representability; see the [release notes](docs/releases/v6.2.1.md).
+
+
+### Existing Pi AI API
+
+`@ccdd/ccdd/pi` re-exports Pi AI unchanged; `@ccdd/ccdd/pi/providers/all`
+re-exports its public `builtinModels` and `builtinProviders` catalog API. These
+are ESM and type forwards, not a new authentication manager or coding agent.
+The umbrella declares Pi AI directly, so both paths work under strict pnpm.
+
+The existing official CLI remains `npx @earendil-works/pi-ai@0.87.1 list` and
+`npx @earendil-works/pi-ai@0.87.1 login [provider]`. Its current CLI lists/logs
+in OAuth providers and saves `auth.json` in the current directory; use it only
+from an appropriate private directory outside reviewed input. API-key login
+is available through Pi's library API, not that OAuth-only CLI. These exports
+do not create new CCDD login commands, persistence or credential precedence.
 
 ## Review resources and budgets
 

package/examples/computed-views/README.md

@@ -9,4 +9,4 @@ ccdd-project verify checkout --human-inbox
 ccdd-project monitor
 ```
 
-Run these commands from this directory after installing `@ccdd/core` and `@ccdd/project`. Submit the Human verdict explicitly through the monitor. Scenario files, the manifest and the shared script determine input identity. Output belongs in `context.outputDir`, outside the supplied workspace. Parameter combinations that generate Artifact declarations are not supported in version 4.
+Run these commands from this directory after installing `@ccdd/ccdd`. Submit the Human verdict explicitly through the monitor. Scenario files, the manifest and the shared script determine input identity. Output belongs in `context.outputDir`, outside the supplied workspace. Parameter combinations that generate Artifact declarations are not supported in version 4.

package/examples/custom-text-reader/README.md

@@ -2,7 +2,7 @@
 
 `why/ccdd.json` declares an explicit basis. `spec/ccdd.json` owns its alignment Critic and reader. The instruction `{why}` derives the dependency; no `target`, `deps`, type registry or config factory is needed.
 
-Install `@ccdd/core` and `@ccdd/project` in this example directory. The custom `view.mjs` requires only Node; default tools are optional.
+Install `@ccdd/ccdd` in this example directory. The custom `view.mjs` requires only Node; default tools are optional.
 
 ```sh
 ccdd-project config check

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ccdd/core",
-  "version": "6.1.0",
+  "version": "6.2.1",
   "license": "MIT",
   "publishConfig": {
     "access": "public",
@@ -21,13 +21,14 @@
   },
   "workspaces": [
     "packages/default-tools",
-    "packages/project"
+    "packages/project",
+    "packages/ccdd"
   ],
   "engines": {
     "node": "^22.19.0"
   },
   "scripts": {
-    "build": "node scripts/clean-build.mjs && npm run build:core && npm run build:tools && node node_modules/typescript/bin/tsc -p tsconfig.json && npm run build:ui && npm run build:project",
+    "build": "node scripts/clean-build.mjs && npm run build:core && npm run build:tools && node node_modules/typescript/bin/tsc -p tsconfig.json && npm run build:ui && npm run build:project && npm run build:umbrella",
     "build:core": "node node_modules/typescript/bin/tsc -p tsconfig.runtime.json",
     "build:tools": "npm run build --workspace @ccdd/default-tools",
     "build:project": "node scripts/build-project.mjs",
@@ -41,7 +42,8 @@
     "release": "node scripts/local-release.mjs",
     "release:npm": "node scripts/local-release.mjs --npm",
     "release:npm:check": "node scripts/check-npm.mjs",
-    "demo:prepare": "npm run build && node dist/src/cli.js prepare-demo"
+    "demo:prepare": "npm run build && node dist/src/cli.js prepare-demo",
+    "build:umbrella": "npm run build --workspace @ccdd/ccdd"
   },
   "files": [
     "dist/src/sdk.*",
@@ -66,6 +68,7 @@
     "typescript": "7.0.2",
     "typescript-ui": "npm:typescript@6.0.3",
     "vite": "8.2.2",
-    "vue-tsc": "3.3.11"
+    "vue-tsc": "3.3.11",
+    "pnpm": "10.30.2"
   }
 }