@pmelab/gtd 57.0.0 → 58.1.0

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "gtd",
-  "version": "57.0.0",
+  "version": "58.1.0",
   "description": "Drive the gtd loop inside Claude Code: agent turns run as subagents, gtd decides every beat",
   "author": {
     "name": "Philipp Melab"

package/README.md

@@ -692,14 +692,15 @@ build, one quality lap, one review — however many criteria it has. Sizing the
 work is yours: split a change too big for one process into several before the
 sketch.
 
-**Flag mode (`flagMode`, on by default).** On, the naive pass's judge runs as
-above and a rebuilt implementation is asked for a new release flag (none at a
-`low` risk tier); a pass the judge lets land is not asked for one. A project
-that is not publicly released turns it off explicitly —
-`feature({ flagMode: false })` in `gtd.config.ts`, it is never detected: then no
-flag is asked for, no seam judge or refactor runs, and the naive pass lands as
-the implementation, straight through the health loop and the quality lap. See
-[`flagMode`](docs/configuration.md#the-bundled-workflows-settings).
+**Release flags (only when asked for).** A change ships unflagged unless its
+requirements ask for a flag: a `## Release Flag` section in
+`.gtd/REQUIREMENTS.md` reading `new` (a new release flag) or `existing: <NAME>`
+(behind a flag that already exists). Triage writes it only when the sketch asks
+for a flag; you can add, change or delete it at the design gate. With it, the
+naive pass's judge runs as above and the build adds the new flag, or uses the
+named one; without it, no seam judge or refactor runs and the naive pass lands
+as the implementation, straight through the health loop and the quality lap. See
+[Release flags](docs/configuration.md#release-flags).
 
 **Risk tier (flag `GTD_FLAG_RISK_TIER=1`, off by default).** Triage proposes a
 risk tier, `low` or `high`, and the production signals to watch after merge.
@@ -880,10 +881,11 @@ gtd is one package, `@pmelab/gtd`, and every entrypoint shares its version and
 | `@pmelab/gtd/workflow-kit`                                                                                                                                     | Policy-free building blocks to compose a workflow from: health checks, quality laps, scenario freezing, review tails.                                                                                  |
 | `@pmelab/gtd/workflows`                                                                                                                                        | Every shipped workflow and all its parts in one module; also resolvable as `@pmelab/gtd/workflow`.                                                                                                     |
 | `@pmelab/gtd/workflows/feature`, `@pmelab/gtd/workflows/review`, `@pmelab/gtd/workflows/fix`, `@pmelab/gtd/workflows/rollout`, `@pmelab/gtd/workflows/cleanup` | One shipped workflow each: its factory as the default export, its parts, and the reserved exports (`defaults`, `envDefaults`, `summary`, `steering`, `skills`, `access`). `gtd install` imports these. |
-| `@pmelab/gtd/testkit`                                                                                                                                          | Runs any workflow against the real engine, in an in-memory or a real repository. Needs `vitest` and `quickpickle`, optional peer dependencies.                                                         |
+| `@pmelab/gtd/testkit`                                                                                                                                          | Runs any workflow against the real engine in an in-memory repository, under any test runner. See [Testing a workflow](https://github.com/pmelab/gtd/blob/main/docs/testing.md).                        |
+| `@pmelab/gtd/testkit/gherkin`                                                                                                                                  | The testkit as quickpickle steps for vitest. Needs `vitest` and `quickpickle`, optional peer dependencies.                                                                                             |
 
 Types come from the TypeScript sources the package ships. Configs never need an
-install for any of these but `./testkit`: gtd resolves a `gtd.config.ts`'s
+install for any of these but the testkit's: gtd resolves a `gtd.config.ts`'s
 `@pmelab/gtd/*` imports to its own copy.
 
 The `gtd` bin's commands — `next`, `land`, `abandon`, `restore`, `validate`,