@pmelab/gtd 52.1.0 → 53.0.0

package/src/workflows/feature/continuation.feature

@@ -1,209 +0,0 @@
-@inmem
-Feature: a turn stopped at its context limit is snapshotted and continued
-
-  A naive pass, refactor or build turn told to stop at its context limit
-  writes its handoff note to `.gtd/HANDOFF.md`. That turn is the snapshot —
-  the naive pass's kept tip, or the refactor's or build's own commit — and a
-  continuation in a fresh conversation (`<phase>.continue.<step>`) picks up
-  from it with the note and what is still open. After `continuations` (3) of
-  them, or `continuationStall` (2) in a row that close nothing still open, the
-  phase rests at `<phase>.oversized`.
-
-  Background:
-    Given the shipped workflows, as gtd install scaffolds them
-    And an environment variable "GTD_QUALITYREVIEWS" set to ""
-    And an environment variable "GTD_REFACTORQUALITYREVIEWS" set to ""
-    And an environment variable "GTD_FLAG_RISK_TIER" set to "0"
-    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 and multiply
-      """
-    And step "unwind" changes nothing
-    And step "start-gate.check" changes nothing
-    And step "design.triage" writes ".gtd/REQUIREMENTS.md" with:
-      """
-      # Requirements
-
-      ## Impact
-
-      - the greeting module
-
-      ## Acceptance Criteria
-
-      - AC-1: `subtract(5, 3)` returns 2.
-      - AC-2: `multiply(2, 3)` returns 6.
-      """
-    And step "design.gate.answer" changes nothing
-    And step "seam.check" changes nothing
-
-  Scenario: a naive pass stopped at its context limit is continued from its kept tip with the open IDs
-    Given step "seam.naive" writes "tests/calc.test.ts" with:
-      """
-      it("[AC-1] subtracts", () => {})
-      """
-    And step "seam.naive" writes ".gtd/HANDOFF.md" with:
-      """
-      Wrote subtract and its test; multiply was next.
-      """
-    When the process is driven
-    Then the process rests at "seam.continue.naive"
-    And the resting step's content contains "Your previous turn stopped at its context limit"
-    And the resting step's content contains "Still open: AC-2."
-    And the resting step's content contains "Wrote subtract and its test; multiply was next."
-    And the resting step's content contains "':(top)' ':(top,exclude).gtd/HANDOFF.md' | git apply"
-    And ".gtd/HANDOFF.md" does not exist
-    And the output of gtd "next --json" contains "\"resume\":false"
-    And the output of gtd "next --json" contains "\"memory\":\"seam.continue#"
-
-    Given step "seam.continue.naive" writes "tests/calc.test.ts" with:
-      """
-      it("[AC-1] subtracts", () => {})
-      it("[AC-2] multiplies", () => {})
-      """
-    When the process is driven
-    Then the process rests at "implement.applying"
-    And the commit subjects end with:
-      """
-      gtd(human): design.gate.answer → seam.naive
-      gtd(agent): seam.naive → seam.continue.naive
-      gtd(agent): seam.continue.naive → seam.check
-      gtd(check): seam.check → implement.applying
-      """
-
-  Scenario: two continuations in a row that close nothing rest for a person
-    Given step "seam.naive" writes "tests/calc.test.ts" with:
-      """
-      it("[AC-1] subtracts", () => {})
-      """
-    And step "seam.naive" writes ".gtd/HANDOFF.md" with:
-      """
-      Subtract is tested; multiply was next.
-      """
-    And step "seam.continue.naive" writes ".gtd/HANDOFF.md" with:
-      """
-      Still on multiply.
-      """
-    When the process is driven
-    Then the process rests at "seam.oversized"
-    And the resting step's content contains "the last 2 continuations closed nothing still open"
-    And the commit subjects end with:
-      """
-      gtd(human): design.gate.answer → seam.naive
-      gtd(agent): seam.naive → seam.continue.naive
-      gtd(agent): seam.continue.naive
-      gtd(agent): seam.continue.naive → seam.oversized
-      """
-
-  Scenario: a refactor stopped at its context limit is run green before its continuation
-    Given step "seam.naive" writes "tests/calc.test.ts" with:
-      """
-      it("[AC-1] subtracts", () => {})
-      it("[AC-2] multiplies", () => {})
-      """
-    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
-      export const multiply = (a: number, b: number) => a * b
-      """
-    And judge step "seam.judge" answers:
-      """
-      [{"id":"shape","answer":"refactor-first","p":0.9}]
-      """
-    And step "seam.note" writes ".gtd/REFACTOR-NOTE.md" with:
-      """
-      Seam: a shared `op` in src/calc.ts.
-      """
-    And step "refactor.deriving" runs its script
-    And step "refactor.building" writes ".gtd/HANDOFF.md" with:
-      """
-      Started on op; nothing changed yet.
-      """
-    And step "refactor.health.check" changes nothing
-    When the process is driven
-    Then the process rests at "refactor.continue.building"
-    And the resting step's content contains "Still open: src/calc.ts."
-    And the resting step's content contains "Started on op; nothing changed yet."
-    And the commit subjects end with:
-      """
-      gtd(agent): refactor.building → refactor.health.check
-      gtd(check): refactor.health.check → refactor.continue.building
-      """
-
-  Scenario: a refactor continuation that leaves the note in place stopped again
-    Given step "seam.naive" writes "tests/calc.test.ts" with:
-      """
-      it("[AC-1] subtracts", () => {})
-      it("[AC-2] multiplies", () => {})
-      """
-    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 judge step "seam.judge" answers:
-      """
-      [{"id":"shape","answer":"refactor-first","p":0.9}]
-      """
-    And step "seam.note" writes ".gtd/REFACTOR-NOTE.md" with:
-      """
-      Seam: a shared `op` in src/calc.ts.
-      """
-    And step "refactor.deriving" runs its script
-    And step "refactor.building" writes "src/calc.ts" with:
-      """
-      export const op = (a: number, b: number, sign: number) => a + sign * b
-      export const add = (a: number, b: number) => a + b
-      """
-    And step "refactor.building" writes ".gtd/HANDOFF.md" with:
-      """
-      op is in; routing add through it was next.
-      """
-    And step "refactor.health.check" changes nothing
-    And step "refactor.continue.building" writes "src/calc.ts" with:
-      """
-      export const op = (a: number, b: number, sign: number) => a + sign * b
-      export const add = (a: number, b: number) => op(a, b, 1)
-      """
-    When the process is driven
-    Then the process rests at "refactor.continue.building"
-    And the commit subjects end with:
-      """
-      gtd(agent): refactor.building → refactor.health.check
-      gtd(check): refactor.health.check → refactor.continue.building
-      gtd(agent): refactor.continue.building → refactor.health.check
-      gtd(check): refactor.health.check → refactor.continue.building
-      gtd(agent): refactor.continue.building
-      """
-
-  Scenario: once a naive pass has continued, its retry runs in a fresh conversation, not as a continuation
-    Given step "seam.naive" writes "tests/calc.test.ts" with:
-      """
-      it("[AC-1] subtracts", () => {})
-      """
-    And step "seam.naive" writes ".gtd/HANDOFF.md" with:
-      """
-      Multiply was next.
-      """
-    And step "seam.continue.naive" writes "tests/calc.test.ts" with:
-      """
-      it("[AC-1] subtracts", () => {})
-      it("[AC-2] multiplies", () => {})
-      """
-    And step "seam.continue.naive" writes "src/calc.ts" with:
-      """
-      export const add = (a: number, b: number) => a - b
-      """
-    And judge step "seam.judge" answers:
-      """
-      [{"id":"shape","answer":"reject","p":0.9}]
-      """
-    When the process is driven
-    Then the process rests at "seam.fresh.naive"
-    And the resting step's content contains "rejected"
-    And the output of gtd "next --json" contains "\"resume\":false"

package/src/workflows/feature/slice-findings.feature

@@ -1,256 +0,0 @@
-@inmem
-Feature: every slice's quality lap is triaged, and its leftovers wait for the review
-
-  A judge sorts each slice's findings like the last slice's (see
-  `lens-review.feature`): mechanical ones are fixed, noise is dropped, design
-  ones are never sent to the fixer. Nothing between slices asks a person
-  anything — what a lap leaves is carried to the review after the last slice,
-  each finding naming its slice and lens.
-
-  Background:
-    Given the shipped workflows, as gtd install scaffolds them
-    And an environment variable "GTD_PROTOTYPEROUNDS" set to "0"
-    And an environment variable "GTD_QUALITYREVIEWS" set to "correctness"
-    And an environment variable "GTD_FLAGMODE" set to "false"
-    And an environment variable "GTD_SLICEMAXCRITERIA" set to "1"
-    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:
-      """
-      # More arithmetic
-
-      subtract and multiply.
-      """
-    And step "unwind" changes nothing
-    And step "start-gate.check" changes nothing
-    And step "design.triage" writes ".gtd/REQUIREMENTS.md" with:
-      """
-      # Requirements
-
-      ## Impact
-
-      - the greeting module
-
-      ## Acceptance Criteria
-
-      - AC-1: subtract(a, b) returns a - b.
-      - AC-2: multiply(a, b) returns a * b.
-      """
-    And step "design.gate.answer" changes nothing
-    And step "design.slicing" writes ".gtd/SLICES.md" with:
-      """
-      # Slices
-
-      ## Subtract
-
-      - AC-1
-
-      ## Multiply
-
-      - AC-2
-      """
-    And step "seam.naive", when prompted with "This slice builds AC-1 only", writes "src/sub.test.ts" with:
-      """
-      it("[AC-1] subtracts", () => {})
-      """
-    And step "seam.naive", when prompted with "This slice builds AC-2 only", writes "src/mul.test.ts" with:
-      """
-      it("[AC-2] multiplies", () => {})
-      """
-    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 step "build.quality.sorting" runs its script
-    And step "build.quality.closing" runs its script
-    And step "build.health.check" changes nothing
-    And step "build.review.carrying" runs its script
-    And judge step "build.review.ranking" answers:
-      """
-      []
-      """
-
-  Scenario: a finding questioning a criterion reaches the final review, never the fixer
-    Given step "build.quality.correctness.reviewing" writes ".gtd/QUALITY.md" with:
-      """
-      # Quality
-
-      ## AC-1 ignores floating point
-
-      Should subtract round? The criterion does not say.
-      """
-    And judge step "build.quality.triage" answers:
-      """
-      [{"id":"Q1","answer":"design","p":0.9}]
-      """
-    And step "build.review.reviewing" writes ".gtd/REVIEW.md" with:
-      """
-      # Review: abc1234
-
-      <!-- base: 0000000 -->
-
-      ## Subtract and multiply
-
-      - [ ] ./src/sub.test.ts#1-1 — subtract
-      - [ ] ./src/mul.test.ts#1-1 — multiply
-
-      ## AC-1 ignores floating point
-
-      - [ ] ./src/sub.test.ts#1-1 — where it applies
-
-      ## AC-1 ignores floating point (2)
-
-      - [ ] ./src/sub.test.ts#1-1 — where it applies
-      """
-    When the process is driven
-    Then the process rests at "build.review.await-review"
-    And no commit body contains "build.fix.quality.fixing"
-    And ".gtd/QUALITY.md" does not exist
-    And ".gtd/REVIEW.md" contains:
-      """
-      ### AC-1 ignores floating point
-
-      _critical: judge unsure_
-
-      _From slice 1, lens correctness._
-
-      Should subtract round? The criterion does not say.
-      """
-    And ".gtd/REVIEW.md" contains:
-      """
-      ### AC-1 ignores floating point (2)
-
-      _critical: judge unsure_
-
-      _From slice 2, lens correctness._
-      """
-    And the commit subjects end with:
-      """
-      gtd(check): implement.closing → build.quality.correctness.reviewing
-      gtd(agent): build.quality.correctness.reviewing → build.quality.triage
-      gtd(judge): build.quality.triage → build.quality.sorting
-      gtd(check): build.quality.sorting → 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.closing
-      gtd(check): implement.closing → build.quality.correctness.reviewing
-      gtd(agent): build.quality.correctness.reviewing → build.quality.triage
-      gtd(judge): build.quality.triage → build.quality.sorting
-      gtd(check): build.quality.sorting → build.review.reviewing
-      gtd(agent): build.review.reviewing → build.review.ranking
-      gtd(judge): build.review.ranking → build.review.carrying
-      gtd(check): build.review.carrying → build.review.await-review
-      """
-
-  Scenario: a mechanical finding the fix cap leaves in an early slice is carried, never escalated
-    Given step "build.quality.correctness.reviewing" writes ".gtd/QUALITY.md" with:
-      """
-      # Quality
-
-      ## subtract has no negative test
-
-      Add a test subtracting a larger number.
-      """
-    And judge step "build.quality.triage" answers:
-      """
-      [{"id":"Q1","answer":"mechanical","p":0.9}]
-      """
-    And step "build.fix.quality.fixing" changes nothing
-    And step "build.review.reviewing" writes ".gtd/REVIEW.md" with:
-      """
-      # Review: abc1234
-
-      <!-- base: 0000000 -->
-
-      ## Subtract and multiply
-
-      - [ ] ./src/sub.test.ts#1-1 — subtract
-      - [ ] ./src/mul.test.ts#1-1 — multiply
-
-      ## subtract has no negative test
-
-      - [ ] ./src/sub.test.ts#1-1 — where it applies
-
-      ## subtract has no negative test (2)
-
-      - [ ] ./src/sub.test.ts#1-1 — where it applies
-      """
-    When the process is driven
-    Then the process rests at "build.review.await-review"
-    And no commit body contains "build.health.describe"
-    And ".gtd/REVIEW.md" contains:
-      """
-      ### subtract has no negative test
-
-      _critical: judge unsure_
-
-      _From slice 1, lens correctness._
-
-      _The fixer left this unresolved._
-      """
-    And the commit subjects end with:
-      """
-      gtd(check): implement.closing → build.quality.correctness.reviewing
-      gtd(agent): build.quality.correctness.reviewing → build.quality.triage
-      gtd(judge): build.quality.triage → build.fix.quality.fixing
-      gtd(agent): build.fix.quality.fixing
-      gtd(agent): build.fix.quality.fixing
-      gtd(agent): build.fix.quality.fixing → build.health.check
-      gtd(check): build.health.check → build.quality.closing
-      gtd(check): build.quality.closing → 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.closing
-      gtd(check): implement.closing → build.quality.correctness.reviewing
-      gtd(agent): build.quality.correctness.reviewing → build.quality.triage
-      gtd(judge): build.quality.triage → build.fix.quality.fixing
-      gtd(agent): build.fix.quality.fixing
-      gtd(agent): build.fix.quality.fixing
-      gtd(agent): build.fix.quality.fixing → build.health.check
-      gtd(check): build.health.check → build.quality.closing
-      gtd(check): build.quality.closing → build.review.reviewing
-      gtd(agent): build.review.reviewing → build.review.ranking
-      gtd(judge): build.review.ranking → build.review.carrying
-      gtd(check): build.review.carrying → build.review.await-review
-      """
-
-  Scenario: the final review lists every slice's fixes with their commits
-    Given step "build.quality.correctness.reviewing" writes ".gtd/QUALITY.md" with:
-      """
-      # Quality
-
-      ## subtract has no negative test
-
-      Add a test subtracting a larger number.
-      """
-    And judge step "build.quality.triage" answers:
-      """
-      [{"id":"Q1","answer":"mechanical","p":0.9}]
-      """
-    And step "build.fix.quality.fixing" writes "src/edge.test.ts" with:
-      """
-      it("subtracts a larger number", () => {})
-      """
-    And step "build.fix.quality.fixing" deletes ".gtd/QUALITY.md"
-    And step "build.review.reviewing" writes ".gtd/REVIEW.md" with:
-      """
-      # Review: abc1234
-
-      <!-- base: 0000000 -->
-
-      ## Subtract and multiply
-
-      - [ ] ./src/sub.test.ts#1-1 — subtract
-      - [ ] ./src/mul.test.ts#1-1 — multiply
-      """
-    When the process is driven
-    Then the process rests at "build.review.await-review"
-    And ".gtd/REVIEW.md" contains ", slice 1, lens correctness)"
-    And ".gtd/REVIEW.md" contains ", slice 2, lens correctness)"
-    And ".gtd/REVIEW.md" contains the short hash of the commit "gtd(agent): build.fix.quality.fixing → build.health.check"
-    And no commit body contains "build.quality.closing"

package/src/workflows/feature/slicing-cap.feature

@@ -1,23 +0,0 @@
-@inmem
-Feature: a bad sliceMaxCriteria refuses the landing that would pin it
-
-  The cap is read right after idle, so a value that is not a positive integer
-  never gets pinned into a process that would refuse every later landing.
-
-  Scenario: a zero cap refuses the idle landing
-    Given the shipped workflows, as gtd install scaffolds them
-    And an environment variable "GTD_SLICEMAXCRITERIA" set to "0"
-    And a file "TODO.md" with:
-      """
-      # Something
-      """
-    Then driving the process is refused with "sliceMaxCriteria must be a positive integer, got \"0\""
-
-  Scenario: a prototypeRounds that is not a whole number refuses the idle landing
-    Given the shipped workflows, as gtd install scaffolds them
-    And an environment variable "GTD_PROTOTYPEROUNDS" set to "-1"
-    And a file "TODO.md" with:
-      """
-      # Something
-      """
-    Then driving the process is refused with "prototypeRounds must be a non-negative integer, got \"-1\""