ccqa 1.58.1 → 1.58.2

package/dist/bin/ccqa.mjs

@@ -8710,16 +8710,14 @@ function rulesReview(guides) {
 				""
 			])
 		],
-		answerShape: "{ \"findings\": [ { \"stepId\": \"step-05\", \"problem\": \"…\" } ], \"ruleViolations\": [ { \"file\": \"…\", \"guide\": \"…\", \"rule\": \"…\", \"code\": \"…\", \"severity\": \"blocking\" } ] }",
+		answerShape: "{ \"findings\": [ { \"stepId\": \"step-05\", \"problem\": \"…\" } ], \"ruleViolations\": [ { \"file\": \"…\", \"guide\": \"…\", \"rule\": \"…\", \"code\": \"…\" } ] }",
 		answerNote: [
 			"",
 			"In `ruleViolations`: `file` is the file's path in this repository, and `code`",
 			"the lines that break the rule. `guide` and `rule` are where the rule comes",
 			"from and what it says — the document's path and its own words when you can",
 			"quote one; otherwise the path of a file you read that shows the convention,",
-			"and what you counted (\"N of M files under <dir> do X\"). `severity` is",
-			"\"blocking\" when you would hold the change until it is fixed, and \"advisory\"",
-			"when it is worth saying but you would approve anyway. An empty",
+			"and what you counted (\"N of M files under <dir> do X\"). An empty",
 			"`ruleViolations` means every file follows every rule you could quote or",
 			"count — write the key either way."
 		]
@@ -9150,8 +9148,7 @@ const ViolationSchema = z.object({
 	file: z.string(),
 	guide: z.string(),
 	rule: z.string(),
-	code: z.string(),
-	severity: z.enum(["blocking", "advisory"]).catch("blocking")
+	code: z.string()
 });
 const ViolationsSchema = z.object({ ruleViolations: z.array(z.unknown()) });
 /**
@@ -9239,14 +9236,11 @@ function formatFinding(finding, labels = evidenceLabels()) {
 }
 /**
 * The warning a rule violation becomes: the file, the rule in the words it was
-* judged by, and where that came from. An advisory one says so — a reader must
-* be able to tell a line that was worth a fix round from one that was not. The
-* offending code is left out: it is what the fix pass needs, not what a reader
-* scanning a log does.
+* judged by, and where that came from. The offending code is left out: it is
+* what the fix pass needs, not what a reader scanning a log does.
 */
 function formatViolation(violation) {
-	const advisory = violation.severity === "advisory" ? ", advisory" : "";
-	return `${violation.file}: ${violation.rule} (${violation.guide}${advisory})`;
+	return `${violation.file}: ${violation.rule} (${violation.guide})`;
 }
 /**
 * Hand the written files to a reviewer who knows nothing about where they came
@@ -15179,13 +15173,12 @@ function uncheckedSteps(review, alreadyAsked = /* @__PURE__ */ new Set()) {
 * arrived. Absent violations are absent either way — there is nothing here to
 * act on when that half never came.
 *
-* Only what the reviewer would hold the change for. It is asked to sort its
-* own violations, because the alternative is a round spent on a line it would
-* have approved anyway. Every violation is still reported: `warnings` carries
-* the advisory ones too, marked as such.
+* Every violation the reviewer reports: a rule the project wrote down, or a
+* convention its files share, is the project's decision, not the reviewer's to
+* waive.
 */
 function guideViolations(review, alreadyAsked = /* @__PURE__ */ new Set()) {
-	const violations = (review?.ruleViolations ?? []).filter((v) => v.severity === "blocking" && !alreadyAsked.has(violationKey(v)));
+	const violations = (review?.ruleViolations ?? []).filter((v) => !alreadyAsked.has(violationKey(v)));
 	if (violations.length === 0) return null;
 	return {
 		exitCode: 1,

package/dist/package.json

@@ -1,6 +1,6 @@
 {
   "name": "ccqa",
-  "version": "1.58.1",
+  "version": "1.58.2",
   "type": "module",
   "description": "Browser test recorder powered by Claude Code and agent-browser",
   "repository": {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "ccqa",
-  "version": "1.58.1",
+  "version": "1.58.2",
   "type": "module",
   "description": "Browser test recorder powered by Claude Code and agent-browser",
   "repository": {