@pmelab/gtd 58.2.0 → 59.0.1

package/src/workflows/feature/risk-tier.feature

@@ -1,351 +0,0 @@
-@inmem
-Feature: the risk tier is proposed at triage and recorded behind GTD_FLAG_RISK_TIER
-
-  With GTD_FLAG_RISK_TIER on, design.triage asks
-  for a risk tier and production signals, and the design gate's exit lands them
-  as Gtd-Mark trailers: one `risk-tier=<low|high>`, one `production-signal`
-  per signal. A missing or unreadable tier is high. With the flag off, nothing
-  is asked and no commit carries a Gtd-Mark.
-
-  Background:
-    Given the shipped workflows, as gtd install scaffolds them
-    And an environment variable "GTD_QUALITYREVIEWS" set to ""
-
-  Rule: with GTD_FLAG_RISK_TIER on
-
-    Background:
-      Given an environment variable "GTD_FLAG_RISK_TIER" set to "1"
-      And a file "src/calc.ts" with:
-        """
-        export const add = (a: number, b: number) => a + b
-        """
-      And a file "src/calc.test.ts" with:
-        """
-        import { expect, it } from "vitest"
-        it("adds", () => expect(1 + 1).toBe(2))
-        """
-      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
-
-    Scenario: with the flag on the triage prompt asks for the tier and the signals
-      When the process is driven
-      Then the process rests at "design.triage"
-      And the resting step's content contains "## Risk Tier"
-      And the resting step's content contains "## Production Signals"
-      And the resting step's content contains "unsure means `high`"
-
-    Scenario: a low tier marks risk-tier=low on the design-exit commit
-      Given step "design.triage" writes ".gtd/REQUIREMENTS.md" with:
-        """
-        # Requirements
-
-        ## Risk Tier
-
-        low — trivial copy change
-
-        ## Impact
-
-        - the greeting module
-
-        ## Release Flag
-
-        new
-
-        ## Acceptance Criteria
-
-        - AC-1: the change behaves as described.
-        """
-      And step "design.gate.answer" changes nothing
-      When the process is driven
-      Then the process rests at "seam.naive"
-      And the last commit subject is "gtd(human): design.gate.answer → seam.naive"
-      And the last commit body contains "Gtd-Mark: risk-tier=low"
-
-    Scenario: a high tier marks the design-exit commit
-      Given step "design.triage" writes ".gtd/REQUIREMENTS.md" with:
-        """
-        # Requirements
-
-        ## Risk Tier
-
-        high — touches payments
-
-        ## Impact
-
-        - the greeting module
-
-        ## Release Flag
-
-        new
-
-        ## Acceptance Criteria
-
-        - AC-1: the change behaves as described.
-        """
-      And step "design.gate.answer" changes nothing
-      When the process is driven
-      Then the process rests at "seam.naive"
-      And the last commit subject is "gtd(human): design.gate.answer → seam.naive"
-      And the last commit body contains "Gtd-Mark: risk-tier=high"
-
-    Scenario Outline: a missing section or an unknown word counts as high
-      Given step "design.triage" writes ".gtd/REQUIREMENTS.md" with:
-        """
-        # Requirements
-
-        <tier section>
-        ## Concerns
-
-        ### Subtract
-
-        ## Impact
-
-        - the greeting module
-
-        ## Release Flag
-
-        new
-
-        ## Acceptance Criteria
-
-        - AC-1: the change behaves as described.
-        """
-      And step "design.gate.answer" changes nothing
-      When the process is driven
-      Then the process rests at "seam.naive"
-      And the last commit body contains "Gtd-Mark: risk-tier=high"
-
-      Examples:
-        | tier section                  |
-        |                               |
-        | ## Risk Tier\n\nmedium — hmm |
-        | ```\n## Risk Tier\n\nlow\n```\n |
-
-    Scenario Outline: signals written at triage land as marks for either tier
-      Given step "design.triage" writes ".gtd/REQUIREMENTS.md" with:
-        """
-        # Requirements
-
-        ## Risk Tier
-
-        <tier> — reason
-
-        ## Production Signals
-
-        - error rate on /subtract stays flat
-        - p95 latency
-
-        ## Impact
-
-        - the greeting module
-
-        ## Release Flag
-
-        new
-
-        ## Acceptance Criteria
-
-        - AC-1: the change behaves as described.
-        """
-      And step "design.gate.answer" changes nothing
-      When the process is driven
-      Then the process rests at "seam.naive"
-      And the last commit body contains "Gtd-Mark: production-signal=error rate on /subtract stays flat"
-      And the last commit body contains "Gtd-Mark: production-signal=p95 latency"
-
-      Examples:
-        | tier |
-        | low  |
-        | high |
-
-    Scenario: the tier a rebuilt pass is told comes from the requirements the final design gate lap accepted
-      Given step "design.triage" writes ".gtd/REQUIREMENTS.md" with:
-        """
-        # Requirements
-
-        ## Risk Tier
-
-        low — trivial copy change
-
-        ## Impact
-
-        - the greeting module
-
-        ## Release Flag
-
-        new
-
-        ## Acceptance Criteria
-
-        - AC-1: the change behaves as described.
-        """
-      And step "seam.check" writes "src/acceptance.test.ts" with:
-        """
-        it("[AC-1] holds elsewhere", () => {})
-        """
-      And step "implement.applying" runs its script
-      And step "seam.naive" writes "src/acceptance.test.ts" with:
-        """
-        it("[AC-1] holds", () => {})
-        """
-      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":"land","p":0.9}]
-        """
-      When the process is driven
-      Then the process rests at "design.gate.answer"
-      Given a file ".gtd/REQUIREMENTS.md" with:
-        """
-        # Requirements
-
-        ## Risk Tier
-
-        high — touches payments
-        """
-      And step "design.triage" from now on changes nothing
-      And step "design.triage" writes ".gtd/REQUIREMENTS.md" with:
-        """
-        # Requirements
-
-        ## Risk Tier
-
-        high — touches payments
-
-        ## Concerns
-
-        ### Subtract
-
-        ## Impact
-
-        - the greeting module
-
-        ## Release Flag
-
-        new
-
-        ## Acceptance Criteria
-
-        - AC-1: the change behaves as described.
-        """
-      And step "design.gate.answer" changes nothing
-      When the process is driven
-      Then the process rests at "implement.building"
-      And the resting step's content contains "Put the new behaviour behind a new release flag"
-      And the resting step's content does not contain "Add no release flag"
-
-  Rule: with GTD_FLAG_RISK_TIER off
-
-    Background:
-      Given 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 a file "src/calc.test.ts" with:
-        """
-        import { expect, it } from "vitest"
-        it("adds", () => expect(1 + 1).toBe(2))
-        """
-      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
-
-    Scenario: the flag-off twin asks for no tier and marks no commit
-      Given step "design.triage" writes ".gtd/REQUIREMENTS.md" with:
-        """
-        # Requirements
-
-        ## Risk Tier
-
-        low — trivial
-
-        ## Production Signals
-
-        - error rate stays flat
-
-        ## Impact
-
-        - the greeting module
-
-        ## Release Flag
-
-        new
-
-        ## Acceptance Criteria
-
-        - AC-1: the change behaves as described.
-        """
-      And step "design.gate.answer" changes nothing
-      When the process is driven
-      Then the process rests at "seam.naive"
-      And no commit body contains "Gtd-Mark"
-
-    Scenario: the flag-off twin's triage prompt has no tier section
-      When the process is driven
-      Then the process rests at "design.triage"
-      And the resting step's content does not contain "## Risk Tier"
-      And the resting step's content does not contain "## Production Signals"
-
-
-    Scenario: the flag-off twin keeps today's flag demand on a rebuilt pass
-      Given step "design.triage" writes ".gtd/REQUIREMENTS.md" with:
-        """
-        # Requirements
-
-        ## Risk Tier
-
-        low — trivial
-
-        ## Impact
-
-        - the greeting module
-
-        ## Release Flag
-
-        new
-
-        ## Acceptance Criteria
-
-        - AC-1: the change behaves as described.
-        """
-      And step "design.gate.answer" changes nothing
-      And step "seam.check" writes "src/acceptance.test.ts" with:
-        """
-        it("[AC-1] holds elsewhere", () => {})
-        """
-      And step "implement.applying" runs its script
-      And step "seam.naive" writes "src/acceptance.test.ts" with:
-        """
-        it("[AC-1] holds", () => {})
-        """
-      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":"land","p":0.9}]
-        """
-      When the process is driven
-      Then the process rests at "implement.building"
-      And the resting step's content contains "Put the new behaviour behind a new release flag"
-      And the resting step's content does not contain "Add no release flag"

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

@@ -1,146 +0,0 @@
-# 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 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
-  steered rerun lands. The flags are pinned so the per-flag test runs never
-  move it off its path.
-
-  Background:
-    Given the shipped workflows, as gtd install scaffolds them
-    And an environment variable "GTD_QUALITYREVIEWS" 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
-
-      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`.
-
-      ## Impact
-
-      - the greeting module
-
-      ## Release Flag
-
-      new
-
-      ## Acceptance Criteria
-
-      - AC-1: the change behaves as described.
-      """
-    And step "design.gate.answer" changes nothing
-
-  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:
-      """
-      it("[AC-1] holds", () => {})
-      """
-    And step "seam.naive" writes "src/calc.ts" with:
-      """
-      export const add = (a: number, b: number) => b + a
-      """
-    And step "implement.health.check" changes nothing
-    And step "implement.closing" runs its script
-    When the process is driven
-    Then the process rests at "seam.judge"
-
-    Given step "seam.naive" is prompted with "Your previous attempt was rejected"
-    And judge step "seam.judge" answers:
-      """
-      [{"id":"shape","answer":"reject","p":0.9}]
-      """
-    When the process is driven
-    Then the process rests at "seam.steer"
-    And the resting step's content contains "Overrule"
-    And the resting step's content contains "src/calc.ts"
-
-    Given a file ".gtd/REQUIREMENTS.md" with:
-      """
-      # Requirements
-
-      ## Concerns
-
-      ### Subtract
-
-      - `subtract(a, b)` returns `a - b`, in the calculator module.
-
-      ## Impact
-
-      - the greeting module
-
-      ## Release Flag
-
-      new
-
-      ## Acceptance Criteria
-
-      - AC-1: the change behaves as described.
-      """
-    And step "seam.naive" from now on changes nothing
-    And step "seam.naive" writes "src/acceptance.test.ts" with:
-      """
-      it("[AC-1] holds", () => {})
-      """
-    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":"land","p":0.9}]
-      """
-    And step "implement.applying" runs its script
-    When gtd lands
-    And the process is driven
-    Then the process rests at "build.review.reviewing"
-    And the commit subjects end with:
-      """
-      gtd(human): idle → unwind
-      gtd(check): unwind → start-gate.check
-      gtd(check): start-gate.check → design.triage
-      gtd(agent): design.triage → design.gate.answer
-      gtd(human): design.gate.answer → seam.naive
-      gtd(agent): seam.naive → seam.check
-      gtd(check): seam.check → seam.judge
-      gtd(judge): seam.judge → seam.naive
-      gtd(agent): seam.naive → seam.check
-      gtd(check): seam.check → seam.judge
-      gtd(judge): seam.judge → seam.naive
-      gtd(agent): seam.naive → seam.check
-      gtd(check): seam.check → seam.judge
-      gtd(judge): seam.judge → seam.steer
-      gtd(human): seam.steer → seam.naive
-      gtd(agent): seam.naive → seam.check
-      gtd(check): seam.check → seam.judge
-      gtd(judge): seam.judge → implement.applying
-      gtd(check): implement.applying → implement.health.check
-      gtd(check): implement.health.check → implement.closing
-      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:"
-    And the commit "gtd(judge): seam.judge → seam.naive" has a body containing "\"answer\":\"reject\""
-    And the commit "gtd(judge): seam.judge → seam.steer" has a body containing "\"answer\":\"reject\""
-    And the commit "gtd(judge): seam.judge → implement.applying" has a body containing "\"answer\":\"land\""
-    And no commit body contains "Gtd-Approved:"
-    And no commit body contains "Gtd-Workflow:"