@pmelab/gtd 39.0.0 → 40.0.0

package/src/workflows/feature/quality-unresolved.feature

@@ -1,9 +1,9 @@
 @inmem
-Feature: quality findings left unresolved hold a feature process short of idle
+Feature: quality findings left unresolved hold a feature process short of its review
 
-  The quality lap is the last look `feature` takes. When the fix cap leaves
-  `.gtd/QUALITY.md` behind, the process rests for a person instead of ending
-  with findings nobody acted on.
+  When the quality lap's fix cap leaves `.gtd/QUALITY.md` behind, the process
+  rests for a person instead of handing findings nobody acted on to the
+  human review.
 
   Background:
     Given the shipped workflows, as gtd install scaffolds them
@@ -97,10 +97,10 @@ Feature: quality findings left unresolved hold a feature process short of idle
     And step "build.health.check" changes nothing
     When gtd lands
     And the process is driven
-    Then the process rests at "idle"
+    Then the process rests at "build.review.reviewing"
     And the commit subjects end with:
       """
       gtd(check): build.health.check → build.quality-unresolved
       gtd(human): build.quality-unresolved → build.health.check
-      gtd(check): build.health.check → idle
+      gtd(check): build.health.check → build.review.reviewing
       """

package/src/workflows/feature/refactor-absorbs.feature

@@ -42,7 +42,7 @@ Feature: a refactor that carried the whole feature still gets a quality lap over
       """
     And step "design.gate.answer" changes nothing
 
-  Scenario: a tests-only implement turn after a refactor that did it all reaches the quality lap and idle
+  Scenario: a tests-only implement turn after a refactor that did it all reaches the quality lap and the review
     Given step "seam.check" changes nothing
     And step "seam.naive" writes "src/acceptance.test.ts" with:
       """
@@ -113,7 +113,7 @@ Feature: a refactor that carried the whole feature still gets a quality lap over
 
     Given step "build.quality.correctness.reviewing" changes nothing
     When the process is driven
-    Then the process rests at "idle"
+    Then the process rests at "build.review.reviewing"
     And "src/calc.ts" contains "subtract"
     And the commit subjects end with:
       """
@@ -123,7 +123,7 @@ Feature: a refactor that carried the whole feature still gets a quality lap over
       gtd(check): implement.health.check → implement.coverage
       gtd(judge): implement.coverage → implement.closing
       gtd(check): implement.closing → build.quality.correctness.reviewing
-      gtd(agent): build.quality.correctness.reviewing → idle
+      gtd(agent): build.quality.correctness.reviewing → build.review.reviewing
       """
     And the output lines of gtd "slices" start with:
       """

package/src/workflows/feature/refactor-first.feature

@@ -1,10 +1,10 @@
 # One SDLC path per file, so a changed path reds exactly one fixture — do not merge.
 @inmem
-Feature: a refactor-first judgment walks one fixed path to idle
+Feature: a refactor-first judgment walks one fixed path to the review gate
 
   With GTD_FLAG_RISK_TIER off, a naive pass touching
   an existing non-allowlisted file is ruled refactor-first, is refactored and
-  that refactor reviewed, and only then implemented, with no feature review. The flags are
+  that refactor reviewed, and only then implemented and brought to the feature review. The flags are
   pinned so the per-flag test runs never move it off its path.
 
   Background:
@@ -41,7 +41,7 @@ Feature: a refactor-first judgment walks one fixed path to idle
       """
     And step "design.gate.answer" changes nothing
 
-  Scenario: a refactor-first judgment runs refactor, its review, implement and review to idle
+  Scenario: a refactor-first judgment runs refactor, its review, implement and the quality lap to the feature review
     Given step "seam.check" changes nothing
     And step "seam.naive" writes "src/acceptance.test.ts" with:
       """
@@ -121,7 +121,7 @@ Feature: a refactor-first judgment walks one fixed path to idle
       [{"id":"AC-1","answer":"yes","p":0.9}]
       """
     When the process is driven
-    Then the process rests at "idle"
+    Then the process rests at "build.review.reviewing"
     And "src/calc.ts" contains "op(a, b, 1)"
     And "src/calc.ts" contains "subtract"
     And the commit subjects end with:
@@ -145,7 +145,7 @@ Feature: a refactor-first judgment walks one fixed path to idle
       gtd(agent): implement.building → implement.health.check
       gtd(check): implement.health.check → implement.coverage
       gtd(judge): implement.coverage → implement.closing
-      gtd(check): implement.closing → idle
+      gtd(check): implement.closing → build.review.reviewing
       """
     And the commit "gtd(human): idle → unwind" has a body containing "Gtd-Var: flag_risk_tier=0"
     And the commit "gtd(agent): seam.naive → seam.check" has a body containing "Gtd-Kept:"

package/src/workflows/feature/refactor-rebuild.feature

@@ -242,7 +242,7 @@ Feature: refactor-first writes a refactor note, refactors on its own, then rebui
       [{"id":"AC-1","answer":"yes","p":0.9}]
       """
     When the process is driven
-    Then the process rests at "idle"
+    Then the process rests at "build.review.reviewing"
     And "src/calc.ts" contains "op(a, b, -1)"
     And "src/acceptance.test.ts" contains "[AC-1]"
     And ".gtd/REFACTOR-NOTE.md" does not exist
@@ -260,7 +260,7 @@ Feature: refactor-first writes a refactor note, refactors on its own, then rebui
       gtd(agent): implement.building → implement.health.check
       gtd(check): implement.health.check → implement.coverage
       gtd(judge): implement.coverage → implement.closing
-      gtd(check): implement.closing → idle
+      gtd(check): implement.closing → build.review.reviewing
       """
     And the output lines of gtd "slices" start with:
       """

package/src/workflows/feature/refactor-review.feature

@@ -4,7 +4,7 @@ Feature: the refactor slice is reviewed on its own before the feature is impleme
   After a refactor-first judgment the refactor is built, quality-lapped and
   reviewed in its own slice. Review edits re-run the refactor, never the design;
   the feature slice that follows is quality-lapped from the refactor's
-  sign-off, with no feature review. The flags are pinned so the per-flag test runs never move it off
+  sign-off, then reviewed. The flags are pinned so the per-flag test runs never move it off
   its path.
 
   Background:
@@ -428,7 +428,7 @@ Feature: the refactor slice is reviewed on its own before the feature is impleme
       Then the process rests at "refactor.build.review.await-review"
       When gtd lands
       And the process is driven
-      Then the process rests at "idle"
+      Then the process rests at "build.review.reviewing"
 
     Scenario: a question answered at the refactor review reaches the re-derived package as ### Answered Questions
       When the process is driven
@@ -727,7 +727,7 @@ Feature: the refactor slice is reviewed on its own before the feature is impleme
         """
       When gtd lands
       And the process is driven
-      Then the process rests at "idle"
+      Then the process rests at "build.review.reviewing"
       And "src/calc.ts" contains "subtract"
 
     Scenario: a praise-only one-shot footnote signs off and the feature slice follows
@@ -769,7 +769,7 @@ Feature: the refactor slice is reviewed on its own before the feature is impleme
         """
       When gtd lands
       And the process is driven
-      Then the process rests at "idle"
+      Then the process rests at "build.review.reviewing"
       And "src/calc.ts" contains "subtract"
 
     Scenario: a one-shot footnote judged edit that collecting leaves out refuses naming its anchor
@@ -1084,7 +1084,7 @@ Feature: the refactor slice is reviewed on its own before the feature is impleme
         """
       When gtd lands
       And the process is driven
-      Then the process rests at "idle"
+      Then the process rests at "build.review.reviewing"
       And "src/calc.ts" contains "subtract"
 
     Scenario: a praise-only refactor review still signs off and the feature slice follows
@@ -1119,7 +1119,7 @@ Feature: the refactor slice is reviewed on its own before the feature is impleme
         """
       When gtd lands
       And the process is driven
-      Then the process rests at "idle"
+      Then the process rests at "build.review.reviewing"
       And "src/calc.ts" contains "subtract"
 
     Scenario: a nit fix in the refactor slice that changes a non-stray is refused, though a glob stray widens the write access
@@ -1309,11 +1309,11 @@ Feature: the refactor slice is reviewed on its own before the feature is impleme
       And the resting step's content contains the hash of the commit "gtd(check): refactor.build.review.closing → implement.building"
       Given step "build.quality.correctness.reviewing" changes nothing
       When the process is driven
-      Then the process rests at "idle"
+      Then the process rests at "build.review.reviewing"
       And the commit subjects end with:
         """
         gtd(check): implement.closing → build.quality.correctness.reviewing
-        gtd(agent): build.quality.correctness.reviewing → idle
+        gtd(agent): build.quality.correctness.reviewing → build.review.reviewing
         """
 
   Rule: a refactor package never carries a test file, and demoted headings stop at ######

package/src/workflows/feature/review-gate.feature

@@ -0,0 +1,271 @@
+@inmem
+Feature: a feature process ends at the human review
+
+  After the last slice's quality lap the process rests at the review gate,
+  `.gtd/REVIEW.md`. A sign-off ends the process. A note asking for a change in
+  behaviour starts a feedback lap — design, then implement with no new naive
+  pass or seam judge, the coverage judge over every criterion, the quality lap
+  — and the review again. Its design keeps a built criterion's ID and numbers
+  new behaviour above every ID handed out.
+
+  Background:
+    Given the shipped workflows, as gtd install scaffolds them
+    And an environment variable "GTD_QUALITYREVIEWS" set to ""
+    And an environment variable "GTD_FLAGMODE" set to "false"
+    And a file "src/calc.ts" with:
+      """
+      export const add = (a: number, b: number) => a + b
+      """
+    And the working tree is committed as "feat: add calculator"
+    And a file "TODO.md" with:
+      """
+      # Add subtract
+
+      subtract(a, b) returns the difference.
+      """
+    And step "unwind" changes nothing
+    And step "start-gate.check" changes nothing
+    And step "design.triage" writes ".gtd/REQUIREMENTS.md" with:
+      """
+      # Requirements
+
+      ## Concerns
+
+      ### Subtract
+
+      - `subtract(a, b)` returns `a - b`.
+
+      ## Acceptance Criteria
+
+      - AC-1: subtract(a, b) returns a - b.
+      """
+    And step "design.gate.answer" changes nothing
+    And step "seam.naive" writes "src/calc.test.ts" with:
+      """
+      it("[AC-1] subtracts", () => {})
+      """
+    And step "seam.naive" writes "src/calc.ts" with:
+      """
+      export const add = (a: number, b: number) => a + b
+      export const subtract = (a: number, b: number) => a - b
+      """
+    And step "seam.check" changes nothing
+    And step "implement.applying" runs its script
+    And step "implement.health.check" changes nothing
+    And step "implement.closing" runs its script
+    And judge step "implement.coverage" answers:
+      """
+      [{"id":"AC-1","answer":"yes","p":0.9}]
+      """
+    And step "build.review.reviewing" writes ".gtd/REVIEW.md" with:
+      """
+      # Review: abc1234
+
+      <!-- base: 0000000 -->
+
+      ## calc
+
+      - [ ] ./src/calc.ts#2-2
+        new subtract function
+      """
+    And step "build.review.closing" runs its script
+
+  Scenario: a feature process ends at the review gate
+    When the process is driven
+    Then the process rests at "build.review.await-review"
+    And ".gtd/REQUIREMENTS.md" does not exist
+    And the resting step's content contains the hash of the commit "feat: add calculator"
+    And the commit subjects end with:
+      """
+      gtd(judge): implement.coverage → implement.closing
+      gtd(check): implement.closing → build.review.reviewing
+      gtd(agent): build.review.reviewing → build.review.await-review
+      """
+
+  Scenario: a sign-off ends the process at idle
+    When the process is driven
+    Then the process rests at "build.review.await-review"
+    Given a file ".gtd/REVIEW.md" with:
+      """
+      # Review: abc1234
+
+      <!-- base: 0000000 -->
+
+      ## calc
+
+      - [x] ./src/calc.ts#2-2
+        new subtract function
+      """
+    When gtd lands
+    And the process is driven
+    Then the process rests at "idle"
+    And ".gtd/REVIEW.md" does not exist
+    And the commit subjects end with:
+      """
+      gtd(agent): build.review.reviewing → build.review.await-review
+      gtd(human): build.review.await-review → build.review.closing
+      gtd(check): build.review.closing → idle
+      """
+
+  Rule: a note asking for new behaviour runs the feedback lap
+
+    Background:
+      Given step "build.review.collecting" writes ".gtd/REQUIREMENTS.md" with:
+        """
+        # Requirements
+
+        ## Concerns
+
+        ### Multiply
+
+        - Export `multiply()`.
+        """
+      And step "build.review.collecting" writes ".gtd/REVIEW.md" with:
+        """
+        # Review: abc1234
+
+        <!-- base: 0000000 -->
+
+        ## calc
+
+        - [ ] ./src/calc.ts#2-2
+          new subtract function[^why]
+
+        [^why]:
+            - H: also export multiply
+            - A: noted in the requirements.
+        """
+      And step "re-unwind" runs its script
+      When the process is driven
+      Then the process rests at "build.review.await-review"
+      Given a file ".gtd/REVIEW.md" with:
+        """
+        # Review: abc1234
+
+        <!-- base: 0000000 -->
+
+        ## calc
+
+        - [ ] ./src/calc.ts#2-2
+          new subtract function[^why]
+
+        [^why]:
+            - H: also export multiply
+        """
+      When gtd lands
+      And the process is driven
+      Then the process rests at "build.review.await-review"
+      And ".gtd/REQUIREMENTS.md" contains "multiply"
+      Given a file ".gtd/REVIEW.md" with:
+        """
+        # Review: abc1234
+
+        <!-- base: 0000000 -->
+
+        ## calc
+
+        - [ ] ./src/calc.ts#2-2
+          new subtract function
+        """
+
+    Scenario: the lap keeps AC-1, adds AC-2, and covers both before the next review
+      Given step "design.triage" from now on changes nothing
+      And step "design.triage" writes ".gtd/REQUIREMENTS.md" with:
+        """
+        # Requirements
+
+        ## Concerns
+
+        ### Multiply
+
+        - `multiply(a, b)` returns `a * b`.
+
+        ## Acceptance Criteria
+
+        - AC-1: subtract(a, b) returns a - b.
+        - AC-2: multiply(a, b) returns a * b.
+        """
+      And step "implement.building" writes "src/calc.ts" with:
+        """
+        export const add = (a: number, b: number) => a + b
+        export const subtract = (a: number, b: number) => a - b
+        export const multiply = (a: number, b: number) => a * b
+        """
+      And step "implement.building" writes "src/multiply.test.ts" with:
+        """
+        it("[AC-2] multiplies", () => {})
+        """
+      And judge step "implement.coverage" answers:
+        """
+        [{"id":"AC-1","answer":"yes","p":0.9},{"id":"AC-2","answer":"yes","p":0.9}]
+        """
+      When gtd lands
+      And the process is driven
+      Then the process rests at "build.review.await-review"
+      And ".gtd/REQUIREMENTS.md" does not exist
+      And the commit "gtd(judge): implement.coverage → implement.closing" has a body containing "Gtd-Mark: covers=AC-1"
+      And the commit subjects end with:
+        """
+        gtd(human): build.review.await-review → build.review.closing
+        gtd(check): build.review.closing → re-unwind
+        gtd(check): re-unwind → design.triage
+        gtd(agent): design.triage → design.gate.answer
+        gtd(human): design.gate.answer → implement.building
+        gtd(agent): implement.building → implement.health.check
+        gtd(check): implement.health.check → implement.coverage
+        gtd(judge): implement.coverage → implement.closing
+        gtd(check): implement.closing → build.review.reviewing
+        gtd(agent): build.review.reviewing → build.review.await-review
+        """
+
+    Scenario: a design numbering new behaviour at or below an earlier ID is refused
+      Given step "design.triage" from now on changes nothing
+      And step "design.triage" writes ".gtd/REQUIREMENTS.md" with:
+        """
+        # Requirements
+
+        ## Concerns
+
+        ### Multiply
+
+        - `multiply(a, b)` returns `a * b`.
+
+        ## Acceptance Criteria
+
+        - AC-0: multiply(a, b) returns a * b.
+        - AC-1: subtract(a, b) returns a - b.
+        """
+      When gtd lands
+      Then driving the process is refused with "criteria-ids"
+
+    Scenario: the lap holds a new criterion to coverage
+      Given step "design.triage" from now on changes nothing
+      And step "design.triage" writes ".gtd/REQUIREMENTS.md" with:
+        """
+        # Requirements
+
+        ## Concerns
+
+        ### Multiply
+
+        - `multiply(a, b)` returns `a * b`.
+
+        ## Acceptance Criteria
+
+        - AC-1: subtract(a, b) returns a - b.
+        - AC-2: multiply(a, b) returns a * b.
+        """
+      And step "implement.building" writes "src/calc.ts" with:
+        """
+        export const add = (a: number, b: number) => a + b
+        export const subtract = (a: number, b: number) => a - b
+        export const multiply = (a: number, b: number) => a * b
+        """
+      And judge step "implement.coverage" answers:
+        """
+        [{"id":"AC-1","answer":"yes","p":0.9},{"id":"AC-2","answer":"no","p":0.9}]
+        """
+      When gtd lands
+      And the process is driven
+      Then the process rests at "implement.covering"
+      And the resting step's content contains "AC-2"

package/src/workflows/feature/seam-rejection.feature

@@ -1,6 +1,6 @@
 # One SDLC path per file, so a changed path reds exactly one fixture — do not merge.
 @inmem
-Feature: rejected naive passes walk one fixed path through the steer gate to idle
+Feature: rejected naive passes walk one fixed path through the steer gate to the review gate
 
   With GTD_FLAG_RISK_TIER off, three rejected naive
   passes rest at the steer gate, where a human edit restarts the seam and the
@@ -40,7 +40,7 @@ Feature: rejected naive passes walk one fixed path through the steer gate to idl
       """
     And step "design.gate.answer" changes nothing
 
-  Scenario: three rejects rest at the steer gate, a steered rerun lands and runs to idle
+  Scenario: three rejects rest at the steer gate, a steered rerun lands and runs to the review gate
     Given step "seam.check" changes nothing
     And step "seam.naive" writes "src/acceptance.test.ts" with:
       """
@@ -100,7 +100,7 @@ Feature: rejected naive passes walk one fixed path through the steer gate to idl
     And step "implement.applying" runs its script
     When gtd lands
     And the process is driven
-    Then the process rests at "idle"
+    Then the process rests at "build.review.reviewing"
     And the commit subjects end with:
       """
       gtd(human): idle → unwind
@@ -124,7 +124,7 @@ Feature: rejected naive passes walk one fixed path through the steer gate to idl
       gtd(check): implement.applying → implement.health.check
       gtd(check): implement.health.check → implement.coverage
       gtd(judge): implement.coverage → implement.closing
-      gtd(check): implement.closing → idle
+      gtd(check): implement.closing → build.review.reviewing
       """
     And the commit "gtd(human): idle → unwind" has a body containing "Gtd-Var: flag_risk_tier=0"
     And the commit "gtd(agent): seam.naive → seam.check" has a body containing "Gtd-Kept:"

package/src/workflows/feature/seam.feature

@@ -152,7 +152,7 @@ Feature: the naive pass and seam judge decide how a feature is built
       [{"id":"AC-1","answer":"yes","p":0.9}]
       """
     When the process is driven
-    Then the process rests at "idle"
+    Then the process rests at "build.review.reviewing"
     And "src/calc.ts" contains "subtract"
     And the commit subjects end with:
       """
@@ -160,7 +160,7 @@ Feature: the naive pass and seam judge decide how a feature is built
       gtd(check): implement.applying → implement.health.check
       gtd(check): implement.health.check → implement.coverage
       gtd(judge): implement.coverage → implement.closing
-      gtd(check): implement.closing → idle
+      gtd(check): implement.closing → build.review.reviewing
       """
     And ".gtd/REQUIREMENTS.md" does not exist
 

package/src/workflows/feature/seam.ts

@@ -283,7 +283,7 @@ export interface ImplementOptions {
   /** Where the slice began: the coverage judge reads only the tests changed since. */
   readonly base?: string | undefined
   /** Not the last slice: `.gtd/REQUIREMENTS.md` and `.gtd/SLICES.md` stay for the next one. */
-  readonly more?: boolean | undefined
+  readonly more?: boolean | (() => boolean) | undefined
 }
 
 /** Resolves `false` when the tip no longer applies (the failure is in `.gtd/FEEDBACK.md`) or has nothing outside `.gtd/` to apply. */
@@ -351,14 +351,19 @@ export function implement(
   tier?: RiskTier,
   amend?: boolean,
 ): Promise<void>
-export function implement(
+export async function implement(
   first?: string | ImplementOptions,
   tier?: RiskTier,
   amend?: boolean,
 ): Promise<void> {
-  const options: ImplementOptions =
-    typeof first === "object" && first !== null ? first : { reference: first, tier, amend }
-  return scope("implement", async () => {
+  await implementing(
+    typeof first === "object" && first !== null ? first : { reference: first, tier, amend },
+  )
+}
+
+/** `implement`, resolving with the criterion IDs the requirements listed when it closed. */
+export const implementing = (options: ImplementOptions): Promise<readonly string[]> =>
+  scope("implement", async () => {
     const since = head()
     const acceptance = options.rebuild?.acceptance
     const built = options.naive === undefined || !(await applied(options.naive))
@@ -372,9 +377,14 @@ export function implement(
       built && acceptance !== undefined ? () => requireAcceptanceKept(acceptance) : undefined,
     )
     await requireCoverage(options.base, options.slice)
-    await closing(options.more === true)
+    const ids = criterionIds(read(REQUIREMENTS) ?? "")
+    await closing(moreToBuild(options.more))
+    return ids
   })
-}
+
+// Read at closing: a narrowing at `implement.oversized` may have emptied every later slice.
+const moreToBuild = (more: ImplementOptions["more"]): boolean =>
+  typeof more === "function" ? more() : more === true
 
 /** The last slice's closing, for a last slice a steer left with no criterion to build. */
 export const closeOut = (): Promise<void> => scope("implement", () => closing(false))

package/src/workflows/feature/slicing.feature

@@ -51,7 +51,7 @@ Feature: a change with more criteria than the cap is built in coarse slices
       [{"id":"AC-1","answer":"yes","p":0.9},{"id":"AC-2","answer":"yes","p":0.9}]
       """
     When the process is driven
-    Then the process rests at "idle"
+    Then the process rests at "build.review.reviewing"
     And the commit subjects end with:
       """
       gtd(human): design.gate.answer → seam.naive
@@ -60,7 +60,7 @@ Feature: a change with more criteria than the cap is built in coarse slices
       gtd(check): implement.applying → implement.health.check
       gtd(check): implement.health.check → implement.coverage
       gtd(judge): implement.coverage → implement.closing
-      gtd(check): implement.closing → idle
+      gtd(check): implement.closing → build.review.reviewing
       """
     And the output lines of gtd "slices" start with:
       """
@@ -112,7 +112,7 @@ Feature: a change with more criteria than the cap is built in coarse slices
       [{"id":"AC-2","answer":"yes","p":0.9}]
       """
     When the process is driven
-    Then the process rests at "idle"
+    Then the process rests at "build.review.reviewing"
     And the commit subjects end with:
       """
       gtd(agent): design.triage → design.gate.answer
@@ -129,7 +129,7 @@ Feature: a change with more criteria than the cap is built in coarse slices
       gtd(check): implement.applying → implement.health.check
       gtd(check): implement.health.check → implement.coverage
       gtd(judge): implement.coverage → implement.closing
-      gtd(check): implement.closing → idle
+      gtd(check): implement.closing → build.review.reviewing
       """
     And the output lines of gtd "slices" start with:
       """
@@ -223,3 +223,62 @@ Feature: a change with more criteria than the cap is built in coarse slices
       - AC-2
       """
     Then driving the process is refused with "wrote outside its write access"
+
+  Scenario: a steer that empties the last slice still ends at the review of the whole change
+    Given step "design.triage" writes ".gtd/REQUIREMENTS.md" with:
+      """
+      # Requirements
+
+      ## Acceptance Criteria
+
+      - AC-1: subtract(a, b) returns a - b.
+      - AC-2: multiply(a, b) returns a * b.
+      - AC-3: divide(a, b) returns a / b.
+      """
+    And step "design.slicing" writes ".gtd/SLICES.md" with:
+      """
+      # Slices
+
+      ## Subtract and divide
+
+      - AC-1
+      - AC-3
+
+      ## Multiply
+
+      - AC-2
+      """
+    And step "seam.naive" writes "src/sub.test.ts" with:
+      """
+      it("[AC-1] subtracts", () => {})
+      """
+    And judge step "implement.coverage" answers:
+      """
+      [{"id":"AC-1","answer":"yes","p":0.9}]
+      """
+    When the process is driven
+    Then the process rests at "seam.steer"
+    Given a file ".gtd/REQUIREMENTS.md" with:
+      """
+      # Requirements
+
+      ## Acceptance Criteria
+
+      - AC-1: subtract(a, b) returns a - b.
+      """
+    When gtd lands
+    And the process is driven
+    Then the process rests at "build.review.reviewing"
+    And the commit subjects end with:
+      """
+      gtd(human): seam.steer → seam.naive
+      gtd(agent): seam.naive → seam.check
+      gtd(check): seam.check → implement.applying
+      gtd(check): implement.applying → implement.health.check
+      gtd(check): implement.health.check → implement.coverage
+      gtd(judge): implement.coverage → implement.closing
+      gtd(check): implement.closing → build.review.reviewing
+      """
+    And ".gtd/REQUIREMENTS.md" does not exist
+    And ".gtd/SLICES.md" does not exist
+    And the output of gtd "slices" does not contain "feature-2"