@pmelab/gtd 22.0.0 → 23.1.0

package/.claude-plugin/plugin.json

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

@@ -34,8 +34,8 @@ none is optional. See
 [Setup](https://github.com/pmelab/gtd/blob/main/docs/setup.md) for the list, the
 install flags, and the never-install-the-plugin caveat. Skills are declared per
 scope, and restricted per turn where the driver can; each bundled scope has its
-own addressable `.gtdrc` `skills:` entry — see
-[Configuration](https://github.com/pmelab/gtd/blob/main/docs/configuration.md#the-skills-key)
+own addressable `config.skills` entry in `gtd.config.ts` — see
+[Configuration](https://github.com/pmelab/gtd/blob/main/docs/configuration.md#skills)
 to repoint one to a set your own harness has instead.
 
 Each scope also declares which files its agent turns may read and write;
@@ -45,8 +45,10 @@ enforces it at the OS level. See
 [Configuration](https://github.com/pmelab/gtd/blob/main/docs/configuration.md#file-access).
 
 > **`fastTestCommand` is required, with no fallback to `testCommand`.** Set it
-> (everything but e2e) under `env:` in `.gtdrc` or as `GTD_FASTTESTCOMMAND`; gtd
-> stops at the start gate, writing `.gtd/SETUP.md`, until it is.
+> (everything but e2e) as a workflow option in `gtd.config.ts`
+> (`feature({ fastTestCommand: "npm run test:fast" })`) or as
+> `GTD_FASTTESTCOMMAND`; gtd stops at the start gate, writing `.gtd/SETUP.md`,
+> until it is.
 
 > **A repository's `gtd.config.ts` is code, and gtd runs it.** A custom workflow
 > is a TypeScript module, and every gtd command that looks at workflow state —
@@ -58,9 +60,11 @@ enforces it at the OS level. See
 
 Run `gtd install` at your repository's root. It writes a `gtd.config.ts` that
 runs gtd's shipped workflows — commit it; gtd refuses to run without one — and
-prints a briefing. Pipe that briefing into your coding agent and answer its
-questions. It should build you a script that will autonomously run the process
-for you. Ask your agent if you have any questions.
+prints a briefing. The repository need not be a JavaScript project: gtd resolves
+the config's `@pmelab/gtd/*` imports itself, so a Python, Rust or notes
+repository needs no `package.json` and no install. Pipe that briefing into your
+coding agent and answer its questions. It should build you a script that will
+autonomously run the process for you. Ask your agent if you have any questions.
 
 ## Why
 
@@ -96,7 +100,8 @@ that.
 The fastest way to understand it is to drive a few beats by hand. Any git
 repository with at least one commit will do once `gtd install` has written its
 `gtd.config.ts` and you have committed it — the first two beats need nothing
-else. Later beats run your test command, set under `env:` in `.gtdrc`.
+else. Later beats run your test command, set as the `testCommand` workflow
+option in `gtd.config.ts`.
 
 ### Beat 1 — `gtd next` says whose turn it is
 
@@ -415,11 +420,10 @@ noted in steps 3 and 4 below.
    With no `--provider`, `gtd judge run` picks jev when `TYPESAFE_API_KEY` is
    set and non-empty and no `--model` is given, else llm — never falling back
    across them; the `GTD_JUDGE_PROVIDER` / `GTD_JUDGE_MODEL` environment
-   variables, a user-level `~/.config/gtd/judge.json` `{ provider, model }`, and
-   a `.gtdrc` `judge:` key choose the judge without editing the driver (flags
-   win over all three, in that order); `--model` with `--provider fixed`/`jev`
-   is refused. jev and llm exit 1 with nothing on stdout when they cannot answer
-   every question):
+   variables and a user-level `~/.config/gtd/judge.json` `{ provider, model }`
+   choose the judge without editing the driver (flags win over both, in that
+   order); `--model` with `--provider fixed`/`jev` is refused. jev and llm exit
+   1 with nothing on stdout when they cannot answer every question):
    - Every red round after the first: was the failure identical, new, or
      progress?
    - After you review: is each of your notes an edit, a question, a nit or
@@ -521,6 +525,14 @@ 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,
 naming which side to upgrade, on a flows protocol mismatch.
 
+Everything else a repository configures — steering-file modes, `gtd ui`
+settings, per-scope skills and file access — goes in the same file's `config`
+export, built with `defineConfig` from `@pmelab/gtd/flows`, which rejects an
+unknown key. `gtd.config.ts` is the only repository config: gtd 23 removed the
+`.gtdrc` files, and a leftover one — in the repository, above it, or in your
+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).
+
 ## License
 
 MIT

package/claude/hooks/persona.ts

@@ -4,7 +4,7 @@ const NEUTRAL = "You are a coding agent working on the task you are given."
 
 // `general-purpose` cannot carry a restriction, so every prompt turn gets a
 // registered persona. The name hashes everything the spec depends on: a
-// `.gtdrc` change or gtd upgrade mid-session must register a fresh one.
+// `gtd.config.ts` change or gtd upgrade mid-session must register a fresh one.
 export async function personaSpec(t: Pick<Turn, "scope" | "system" | "skills">) {
   const key = JSON.stringify([t.scope, t.system ?? "", t.skills])
   const digest = new Uint8Array(