@pmelab/gtd 23.2.0 → 24.1.0

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "gtd",
-  "version": "23.2.0",
+  "version": "24.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

@@ -501,25 +501,33 @@ the agent may overturn the answer. See
 [Configuration](https://github.com/pmelab/gtd/blob/main/docs/configuration.md)
 for its `ui:` settings.
 
-The bundled workflows are named `feature` (the ordinary start above), `fix` and
-`review`. Two doors start the other two and skip step 1. `gtd door fix` repairs
-a red baseline as its own reviewed commit instead of starting a process. And
+The bundled workflows are named `feature` (the ordinary start above), `review`
+and `fix`. They are independent: `review` and `fix` never plan, and they meet
+only in `.gtd/REVIEW.md`. Each brings its own door. This command:
 
 ```bash
 gtd door review <commitish>
 ```
 
-starts a pure review of everything from `<commitish>` to HEAD — straight to step
-4, no planning and no building. `gtd doors` lists every door; a `gtd.config.ts`
-can add its own. `gtd --workflow <name>` starts any workflow by name.
+starts a pure review of everything from `<commitish>` to HEAD. It goes straight
+to step 4, with no planning and no building. Sign off and it closes. Leave notes
+and the process ends with `.gtd/REVIEW.md` (and the reviewer's original,
+`.gtd/REVIEW.orig.md`) left for `gtd door fix`. Until `fix` consumes them,
+starting `feature` or `review` is refused; remove both files to abandon the
+hand-off. `gtd door fix` fixes those notes and every `Risk:` in one turn, then
+asks for your review of the fix. With no review waiting, it repairs a red
+baseline as its own reviewed commit instead. `gtd doors` lists the doors of the
+workflows your `gtd.config.ts` exports, plus any it adds.
+`gtd --workflow <name>` starts any workflow by name.
 
 The workflow itself is a plain async TypeScript function, and the
 `gtd.config.ts` at the repository root names it: the one `gtd install` writes
-re-exports the shipped workflows from `@pmelab/gtd/workflows`, and the pieces
-they are built from are exported for yours to reuse. Each shipped workflow is a
-factory — `feature({ testCommand: "npm run ci" })` — whose options gtd validates
-when it loads the config: a misspelled or mistyped one fails every command,
-naming the workflow, the key and what was expected. See
+re-exports each shipped workflow from its own subpath
+(`@pmelab/gtd/workflows/feature`, `…/review`, `…/fix`), and the pieces they are
+built from are exported for yours to reuse. Each shipped workflow is a factory —
+`feature({ testCommand: "npm run ci" })` — whose options gtd validates when it
+loads the config: a misspelled or mistyped one fails every command, naming the
+workflow, the key and what was expected. See
 [Configuration](https://github.com/pmelab/gtd/blob/main/docs/configuration.md) —
 and remember gtd evaluates that file on every command. A shared workflow package
 bundling its own `@pmelab/gtd` is checked against the running gtd and refused,
@@ -533,6 +541,31 @@ unknown key. `gtd.config.ts` is the only repository config: gtd 23 removed the
 home directory — fails every command until you delete it. See
 [Migrating from `.gtdrc`](https://github.com/pmelab/gtd/blob/main/docs/configuration.md#migrating-from-gtdrc).
 
+## Entrypoints
+
+gtd is one package, `@pmelab/gtd`, and every entrypoint shares its version and
+[SemVer promise](https://github.com/pmelab/gtd/blob/main/COMPATIBILITY.md).
+
+| Import                                                                                       | What it is                                                                                                                                                                                             |
+| -------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `@pmelab/gtd/flows`                                                                          | The flow API a workflow is written in: the steps (`agent`, `human`, `run`, …), workflow factories, `defineConfig` and `FLOWS_PROTOCOL`.                                                                |
+| `@pmelab/gtd/wire`                                                                           | The driver protocol: `WIRE_SCHEMA`, the exit codes and the types of every `--json` document.                                                                                                           |
+| `@pmelab/gtd/steering`                                                                       | The steering-file formats (`qa`, `review`) and the review-note readers.                                                                                                                                |
+| `@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` | 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.                                                         |
+
+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
+`@pmelab/gtd/*` imports to its own copy.
+
+The `gtd` bin's commands — `next`, `land`, `abandon`, `restore`, `validate`,
+`check`, `uncheck`, `install`, `summary`, `base`, `door`, `doors`, `version`,
+`help`, and the tools `ui`, `lsp`, `loop` and `judge` (`judge answer`,
+`judge run`) — are listed in the
+[CLI reference](https://github.com/pmelab/gtd/blob/main/docs/cli.md).
+
 ## License
 
 MIT

package/claude/hooks/access.ts

@@ -1,4 +1,4 @@
-import { globMatches } from "../../src/replay/Glob.js"
+import { globMatches } from "../../src/wire/Glob.js"
 
 export type AccessDef = { read: string[] | null; write: string[] | null }