@windyroad/risk-scorer 0.18.2 → 0.18.3-preview.990

package/.claude-plugin/plugin.json

@@ -310,5 +310,5 @@
     }
   },
   "name": "wr-risk-scorer",
-  "version": "0.18.2"
+  "version": "0.18.3"
 }

package/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "wr-risk-scorer",
-  "version": "0.18.2",
+  "version": "0.18.3",
   "description": "Pipeline risk scoring, commit/push gates, and secret leak detection",
   "author": {
     "name": "Windy Road Technology",

package/agents/pipeline.md

@@ -168,7 +168,7 @@ criteria above.
 
 ## Below-Appetite Output Rule (ADR-013 Rule 5)
 
-When ALL cumulative scores are within appetite (≤ the appetite threshold in `RISK-POLICY.md` § Risk Appetite — read it; `Threshold: N`, default 4/Low when absent; do NOT hardcode 4), your output MUST contain ONLY:
+When ALL cumulative scores are within appetite (≤ the appetite threshold in `RISK-POLICY.md` § Risk Appetite — read it; `Threshold: N`, default 5/Low when absent; do NOT hardcode), your output MUST contain ONLY:
 1. The Pipeline Risk Report structure (layers, risk items, summary table)
 2. `RISK_SCORES: commit=N push=N release=N`
 3. `RISK_BYPASS: reducing` (if applicable)
@@ -177,7 +177,7 @@ Do NOT emit: "Suggested Actions", "Your call:", advisory warnings, back-pressure
 
 ## Above-Appetite Remediations
 
-When ANY cumulative score exceeds appetite (> the RISK-POLICY.md appetite threshold, default 4 — read it, do NOT hardcode), the verbal verdict is **STOP**.
+When ANY cumulative score exceeds appetite (> the RISK-POLICY.md appetite threshold, default 5 — read it, do NOT hardcode), the verbal verdict is **STOP**.
 The scorer is not the primary decision-maker — the hook gate will block the
 action — but the scorer's verdict must match the structured score so the agent
 does not waste tool calls acting on an ambiguous nudge.
@@ -203,8 +203,8 @@ Column definitions:
 - **description**: free-form prose. The agent reads this and decides what to do. No structured action_class column.
 
 Include downstream back-pressure in the remediation list:
-- **Commit**: If adding this commit would push the push queue risk >= 5, include a remediation to split the commit.
-- **Push**: If pushing would push the release queue risk >= 5, include a remediation to release first.
+- **Commit**: If adding this commit would make the push queue exceed appetite, include a remediation to split the commit.
+- **Push**: If pushing would make the release queue exceed appetite, include a remediation to release first.
 
 Do NOT emit free-text "Your call:" or "consider splitting" prose. The structured `RISK_REMEDIATIONS:` block is the only output for above-appetite guidance.
 
@@ -214,7 +214,7 @@ When a pipeline run identifies a **register-worthy risk shape**, emit a structur
 
 ### Trigger conditions (emit a hint when ANY fire)
 
-1. **Above-appetite residual** — any cumulative residual score exceeds the appetite threshold declared in `RISK-POLICY.md` § Risk Appetite (default 4; read it, do NOT hardcode). A risk that breaches appetite on this change is a standing-risk candidate, not just a one-off remediation target.
+1. **Above-appetite residual** — any cumulative residual score exceeds the appetite threshold declared in `RISK-POLICY.md` § Risk Appetite (default 5; read it, do NOT hardcode). A risk that breaches appetite on this change is a standing-risk candidate, not just a one-off remediation target.
 2. **Confidentiality disclosure** — the Confidential Information Disclosure check (below) flagged business metrics (revenue, user counts, pricing, client names, traffic volumes) in the diff. Confidentiality leaks are standing-risk-shaped even after the immediate remediation.
 3. **User-stated precondition** — the User-Stated Preconditions Check (below) flagged an unmet paired capability as a standalone Risk item. Unmet preconditions are standing-risk-shaped because the dependency gap persists until the paired capability ships.
 
@@ -272,7 +272,7 @@ Do NOT emit `RISK_REGISTER_HINT:` when all cumulative scores are within appetite
 
 ## Held-Changeset Graduation Evaluation (ADR-061)
 
-When the pipeline state indicates **within-appetite drain mode** (cumulative push and release residual both ≤ 4/25 per `RISK-POLICY.md`) AND `docs/changesets-holding/` contains entries, evaluate each held changeset against ADR-061 Rule 1's symmetric graduation criterion: **reinstate when `release-risk(pipeline with held changeset hypothetically reinstated) ≤ problem-ticket Priority`**.
+When the pipeline state indicates **within-appetite drain mode** (cumulative push and release residual both ≤ the threshold in `RISK-POLICY.md`, default 5) AND `docs/changesets-holding/` contains entries, evaluate each held changeset against ADR-061 Rule 1's symmetric graduation criterion: **reinstate when `release-risk(pipeline with held changeset hypothetically reinstated) ≤ problem-ticket Priority`**.
 
 This is the symmetric counterpart to ADR-042 Rule 2's move-to-holding contract. Material flows in when release-risk would exceed appetite; material flows out when release-risk falls at or below the originating problem-ticket Priority.
 

package/agents/plan.md

@@ -18,7 +18,7 @@ You are the Risk Scorer in plan review mode. Assess both the plan's own risk AND
 5. Consider what controls will be in place (CI, hooks, tests, preview deploys)
 6. Estimate the plan's own residual risk after controls
 7. **Project release risk**: what would the release look like if the plan's changes were added to the existing unreleased queue?
-8. **Apply back-pressure**: if projected release risk >= appetite and the plan doesn't include a release strategy, FAIL.
+8. **Apply back-pressure**: if projected release risk exceeds appetite and the plan doesn't include a release strategy, FAIL.
 
 ## Verdict Logic
 
@@ -122,4 +122,4 @@ User warnings outrank technical control discovery.
 | 4 Significant | 4 | 8 | 12 | 16 | 20 |
 | 5 Severe | 5 | 10 | 15 | 20 | 25 |
 
-Label Bands: 1-2 Very Low, 3-4 Low, 5-9 Medium, 10-16 High, 17-25 Very High.
+Label Bands: 1-2 Very Low, 3-5 Low, 6-9 Medium, 10-16 High, 17-25 Very High.

package/agents/wip.md

@@ -47,11 +47,11 @@ Always provide the cumulative risk picture:
 
 ### Below-Appetite Rule (ADR-013 Rule 5)
 
-If cumulative risk is **within appetite** (≤ the appetite threshold in `RISK-POLICY.md` § Risk Appetite — read it; `Threshold: N`, default 4/Low when absent; do NOT hardcode): provide the assessment table and verdict only. Do NOT emit advisory prose, recommendations, or suggestions. The verdict is `RISK_VERDICT: CONTINUE`.
+If cumulative risk is **within appetite** (≤ the appetite threshold in `RISK-POLICY.md` § Risk Appetite — read it; `Threshold: N`, default 5/Low when absent; do NOT hardcode): provide the assessment table and verdict only. Do NOT emit advisory prose, recommendations, or suggestions. The verdict is `RISK_VERDICT: CONTINUE`.
 
 ### Above-Appetite Remediations
 
-If cumulative risk **exceeds appetite** (>= 5), the verbal verdict is **PAUSE**
+If cumulative risk **exceeds the configured appetite threshold**, the verbal verdict is **PAUSE**
 (the wip-mode equivalent of STOP).
 
 **Do NOT emit** "Proceed", "Continue", "OK to edit", "You may commit", or any
@@ -89,7 +89,7 @@ After assessing the risk profile, check whether uncommitted changes represent **
 - `packages/*/skills/**/*.bats`
 - `docs/decisions/*.md`
 
-AND cumulative risk is **within appetite** (≤ the RISK-POLICY.md appetite threshold, default 4; read it, do NOT hardcode), AND at least one completion signal is present:
+AND cumulative risk is **within appetite** (≤ the RISK-POLICY.md appetite threshold, default 5; read it, do NOT hardcode), AND at least one completion signal is present:
 - A problem file diff contains "Fix Released" or a status transition keyword. Under the flat layout this surfaces as a `.known-error.md` / `.closed.md` filename suffix; under the per-state subdir layout it surfaces as a path move into `docs/problems/known-error/` or `docs/problems/closed/`.
 - A SKILL.md was modified alongside a problem file update
 
@@ -145,4 +145,4 @@ assessment.
 | 4 Significant | 4 | 8 | 12 | 16 | 20 |
 | 5 Severe | 5 | 10 | 15 | 20 | 25 |
 
-Label Bands: 1-2 Very Low, 3-4 Low, 5-9 Medium, 10-16 High, 17-25 Very High.
+Label Bands: 1-2 Very Low, 3-5 Low, 6-9 Medium, 10-16 High, 17-25 Very High.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@windyroad/risk-scorer",
-  "version": "0.18.2",
+  "version": "0.18.3-preview.990",
   "description": "Pipeline risk scoring, commit/push gates, and secret leak detection",
   "scripts": {
     "prepack": "node scripts/sync-codex-skills.mjs --pack",

package/skills/assess-release/SKILL.md

@@ -84,7 +84,7 @@ Wait for the wrapper to return. The wrapper invokes the pipeline agent internall
 
 Present the full risk report to the user. Highlight:
 - The three risk scores (commit / push / release) and their labels
-- Any risks above appetite (score ≥ 5 per RISK-POLICY.md)
+- Any risks above appetite (score > the threshold configured in RISK-POLICY.md; default 5)
 - Whether the gate is now pre-satisfied for the current session (i.e., a subsequent `git commit` will reuse the bypass marker without re-triggering the scorer)
 
 If any score is above appetite, the action is **framework-mediated, not a user decision** (P377/RFC-029; ADR-044 category-3 explicitly excludes above-appetite). Per **ADR-042 Rule 1**: auto-apply scorer remediations incrementally until residual risk is within appetite, OR halt per ADR-042 Rule 5 if the scorer cannot converge. **MUST NOT commit/push/release above appetite, and MUST NOT use `request_user_input` to ask whether to proceed anyway** — there is no "proceed anyway (bypass)" option; the answer is always reduce-risk-or-halt. The only sanctioned non-blocking path is the risk-reducing path (a genuinely risk-reducing change clears via the `reducing` bypass). Under non-interactive contexts the ADR-013 Rule 6 fail-safe is the terminal fallback: skip the action and report the uncommitted/unreleased state.