@ccdd/core 5.1.2 → 6.0.0

package/README.md

@@ -72,7 +72,7 @@ The [getting-started guide](docs/getting-started.md) includes a complete runnabl
 
 Every actual review returns a verdict and any owner-defined fields required by its optional passSchema/failSchema. There is no built-in summary or evidence field. GREEN means its criteria were met; RED means they were not. Execution problems produce ERROR. Final validation needs matching PASS evidence for all required Critics and dependencies. A folder without Critics stays UNREVIEWED unless explicitly declared `basis: true`.
 
-An individual check runs its selected Critics immediately. If other required evidence is missing, their results are saved and the request is INCOMPLETE. Add `--recursive` to include those other evaluations. CCDD reuses both matching GREEN and RED results (RED remains unsatisfied), coalesces identical active requests across Runs, and computes freshness when queried; it does not store stale flags.
+By default, Critics wait for current GREEN evidence from dependency Critics outside their strongly connected component. RED dependencies block descendants; operational failures leave them waiting without a fabricated verdict. Use `--ignore-gates` only when intentionally reviewing despite dependency verdicts. If other required evidence is missing, their results are saved and the request is INCOMPLETE. Add `--recursive` to include those other evaluations. CCDD reuses both matching GREEN and RED results (RED remains unsatisfied), coalesces identical active requests across Runs, and computes freshness when queried; it does not store stale flags.
 
 Reviews run in the workspace you supply. Keep it unchanged until completion, including Human waiting. Records, caches and generated output live outside it. To keep editing elsewhere, create your own worktree and pass it with `--repo`.
 
@@ -100,4 +100,4 @@ See [Contributing](CONTRIBUTING.md), [the context map](CONTEXT-MAP.md), [detaile
 
 [MIT](LICENSE).
 
-**CCDD 5.1.2:** bounded Broker read caches reduce synchronous lifecycle JSON work that can delay tool responses on large Runs. See the [release notes, measurements and limitations](docs/releases/v5.1.2.md). Existing 5.0 and 5.1 state and reuse keys remain valid; upgrades from 4.x require the [5.0 migration guide](docs/migration-v5.md).
+**CCDD 6.0.0 is a breaking release:** use a fresh format-6 state directory, account for dependency-GREEN gates, and move live polling to `broker.changes`. Read the [6.0 migration guide](docs/migration-v6.md) and [release notes, measurements and limits](docs/releases/v6.0.0.md) before upgrading.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ccdd/core",
-  "version": "5.1.2",
+  "version": "6.0.0",
   "license": "MIT",
   "publishConfig": {
     "access": "public",