@jonit-dev/night-watch-cli 1.8.12-beta.1 → 1.8.12-beta.11

package/dist/templates/night-watch.config.json

@@ -55,6 +55,27 @@
       "audit": 10
     }
   },
+  "webhookTriggers": {
+    "enabled": false,
+    "secretEnv": "NIGHT_WATCH_WEBHOOK_SECRET",
+    "allowedJobIds": [
+      "executor",
+      "reviewer",
+      "pr-resolver",
+      "slicer",
+      "qa",
+      "audit",
+      "analytics",
+      "merger"
+    ],
+    "requireTimestamp": false,
+    "maxSkewSeconds": 300,
+    "github": {
+      "enabled": false,
+      "events": [],
+      "rules": []
+    }
+  },
   "jobProviders": {},
   "autoMerge": false,
   "autoMergeMethod": "squash",

package/dist/templates/pr-reviewer.md

@@ -1,7 +1,7 @@
 You are the Night Watch PR Reviewer agent. Your job is to check open PRs for three things:
 
 1. Merge conflicts -- rebase onto the base branch and resolve them.
-2. Review comments with a score below 80 -- address the feedback.
+2. Review comments with a score below 80 or unresolved review feedback -- address the feedback.
 3. Failed CI jobs -- diagnose and fix the failures.
 
 ## Context
@@ -10,7 +10,7 @@ The repo can have multiple PR checks/workflows (project CI plus Night Watch auto
 Common examples include `typecheck`, `lint`, `test`, `build`, `verify`, `executor`, `qa`, and `audit`.
 Treat `gh pr checks <number> --json name,state,conclusion` as the source of truth for which checks failed.
 
-A PR needs attention if **any** of the following: merge conflicts present, review score below 80, or any CI job failed.
+A PR needs attention if **any** of the following: merge conflicts present, no review score yet, review score below 80, unresolved review feedback, or any CI job failed.
 
 ## PRD Context
 
@@ -21,7 +21,7 @@ If current PR code or review feedback conflicts with the PRD context, call out t
 ## Important: Early Exit
 
 - If there are **no open PRs** on `night-watch/` or `feat/` branches, **stop immediately** and report "No PRs to review."
-- If all open PRs have **no merge conflicts**, **passing CI**, and **review score >= 80**, **stop immediately** and report "All PRs are in good shape."
+- If all open PRs have **no merge conflicts**, **passing CI**, **review score >= 80**, and **no unresolved review feedback**, **stop immediately** and report "All PRs are in good shape."
 - If a PR has no review score yet, it needs a first review — do NOT skip it.
 - Do **NOT** loop or retry. Process each PR **once** per run. After processing all PRs, stop.
 - Do **NOT** re-check PRs after pushing fixes -- the CI will re-run automatically on the next push.
@@ -90,8 +90,8 @@ Parse the review score from the comment body. Look for patterns like:
   Extract the numeric score. If multiple comments have scores, use the **most recent** one.
 
 3. **Determine if PR needs work**:
-   - If no merge conflicts **AND** score >= 80 **AND** all CI checks pass --> skip this PR.
-   - If merge conflicts present **OR** score < 80 **OR** any CI check failed --> fix the issues.
+   - If no merge conflicts **AND** score >= 80 **AND** no unresolved review feedback **AND** all CI checks pass --> skip this PR.
+   - If merge conflicts present **OR** score < 80 **OR** unresolved review feedback exists **OR** any CI check failed --> fix the issues.
 
 4. **Fix the PR**:
 
@@ -122,8 +122,9 @@ Parse the review score from the comment body. Look for patterns like:
    - Push the clean branch: `git push --force-with-lease origin <branch-name>`
    - **Do NOT leave any conflict markers (`<<<<<<<`, `=======`, `>>>>>>>`) in any file.**
 
-   c. **Address review feedback** (if score < 80):
+   c. **Address review feedback** (if score < 80 or pending review feedback exists):
    - Read the review comments carefully. Extract areas for improvement, bugs found, issues found, and specific file/line suggestions.
+   - If `pending review feedback` is greater than 0 in the cron-provided preflight data, inspect review conversations with `gh pr view <number> --comments` and the GitHub PR review UI/API as needed.
    - For each review suggestion:
      - If you agree, implement the change.
      - If you do not agree, do not implement it blindly. Capture a short technical reason and include that reason in the PR comment.

package/dist/templates/slicer.md

@@ -32,6 +32,8 @@ The PRD directory is: `{{PRD_DIR}}`
 
 3. **Write a Complete PRD** — Follow the exact template structure below. Every section must be filled with concrete information. No placeholder text.
 
+   The PRD MUST include these sections: Context (with Problem, Files Analyzed, Current Behavior, Integration Points), Solution (with Approach, Key Decisions), Execution Phases (with Files, Implementation steps, Tests), and Acceptance Criteria.
+
 4. **Write the PRD File** — Use the Write tool to create the PRD file at `{{OUTPUT_FILE_PATH}}`.
 
 ---
@@ -146,6 +148,7 @@ sequenceDiagram
 ## 4. Execution Phases
 
 Critical rules:
+
 1. Each phase = ONE user-testable vertical slice
 2. Max 5 files per phase (split if larger)
 3. Each phase MUST include concrete tests