@open-code-review/agents 1.7.0 → 1.8.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@open-code-review/agents",
3
- "version": "1.7.0",
3
+ "version": "1.8.1",
4
4
  "description": "AI-native skills, commands, and reviewer personas for Open Code Review",
5
5
  "type": "module",
6
6
  "files": [
@@ -356,3 +356,5 @@ Full reviews available in session directory:
356
356
  5. **Author has autonomy** — For suggestions, the author decides what to address. Trust the engineer.
357
357
 
358
358
  6. **Tech Lead facilitates** — The Tech Lead synthesizes and recommends, but doesn't override individual blockers or suppress feedback.
359
+
360
+ 7. **`round-meta.json` matches `final.md`** — When piping data to `ocr state round-complete --stdin`, the `category` on each finding MUST reflect the **post-synthesis** classification. If discourse or synthesis promoted a `should_fix` to `blocker` (or any other re-categorization), update the `category` field in the JSON accordingly. The dashboard derives all counts from `round-meta.json` — a mismatch means wrong numbers on the dashboard.
@@ -645,7 +645,9 @@ See `references/discourse.md` for detailed instructions.
645
645
 
646
646
  > The CLI is the **sole writer** of `round-meta.json`. The orchestrator constructs JSON in memory and pipes it to the CLI, which validates the schema, writes the file to the correct session path, and records a `round_completed` orchestration event — all in one command.
647
647
 
648
- Construct the JSON from synthesis knowledge, then pipe to the CLI:
648
+ Construct the JSON from your **post-synthesis conclusions**, then pipe to the CLI.
649
+
650
+ > **CRITICAL — Category reflects synthesis, not original reviewer tags**: The `category` field on each finding must match the final synthesized classification — NOT the category the individual reviewer originally used. If discourse or synthesis promoted a `should_fix` to `blocker` (or demoted a `blocker` to `should_fix`), the JSON you pipe here MUST use the **promoted/demoted category**. The dashboard derives all counts from these categories. If they don't match `final.md`, the dashboard will show wrong numbers.
649
651
 
650
652
  ```bash
651
653
  cat <<'JSON' | ocr state round-complete --stdin