@ccoalm/ccl-skills 0.10.0 → 0.12.0

package/dist/assets/marketplace/plugins/ccl-skills/skills/skill-extraction-workflow/scripts/contract-anchors.tsv

@@ -13,3 +13,4 @@ burn-rate-page-row-reference	skills/platform-observability/references/sli-slo-de
 coverage-tier-provenance	skills/testing-strategy/references/test-code-authoring-patterns.md	60% acceptable / 75% commendable / 90% exemplary 分档	071-chainC-r1f4: externally verified coverage tiers (specs/071 source-verification)
 pairwise-trigger-range	skills/test-artifact-management/references/classical-test-design-techniques.md	2-way 累计触发 53–97%	071-chainC-r1f4: NIST SP 800-142 empirical range, externally verified (specs/071 source-verification)
 bva-two-vs-three-value	skills/test-artifact-management/references/classical-test-design-techniques.md	2-value（边界 + 下一格）和 3-value（边界 + 两侧）	071-chainC-r1f4: ISTQB v4 BVA variant definitions, externally verified (specs/071 source-verification)
+merge-side-ledger-binding-failclosed	skills/skill-extraction-workflow/scripts/review_ledger_binding.py	return 0 if args.allow_unevaluated else 2	084-r4f1: the no-base fail-closed branch; flipping it to an unconditional 0 restores a gate that passes having checked nothing

package/dist/assets/marketplace/plugins/ccl-skills/skills/skill-extraction-workflow/scripts/impact-chain-gate.rb

@@ -1327,19 +1327,48 @@ if upstream.any? || routing_entrypoint_changed || changed_paths.include?(LEDGER_
     # path is broken gets the firing-path message; every other failure shape
     # gets the behavior-evidence message. (A declared wording-only row can
     # never be a RED row, so no exclusion is needed here.)
-    firing_path_incomplete = evaluated.any? do |entry|
-      entry[:red_declared] && !entry[:firing_path_valid]
-    end
-    if firing_path_incomplete
-      firing_path_failures << path
+    # Name the OFFENDING ROWS, not just the owner. The owner-level `all?` above
+    # means one bad row reddens the package, so an owner-only diagnostic sends the
+    # author to inspect whichever row they were just writing — which is usually the
+    # correct one. Observed: a round whose new row was fine failed because an
+    # unrelated ALREADY-COMMITTED ledger row had been edited by an unbounded string
+    # replace; the edit made that old row an added row of this round, so its own
+    # original anchor no longer resolved here. Three iterations went into rewriting
+    # the good anchor before the real offender was found by patching debug output
+    # into this script. The row identity is what closes that gap.
+    offending_rows = evaluated.each_index.select do |index|
+      evaluated[index][:red_declared] && !evaluated[index][:firing_path_valid]
+    end.map { |index| owner_rows[index] }
+    if offending_rows.any?
+      firing_path_failures << { path: path, rows: offending_rows }
     else
       behavior_failures << path
     end
   end
+  # First cell of a ledger row, bounded: enough to recognise which row is meant
+  # without dumping a multi-thousand-character evidence cell into the diagnostic.
+  # This renders REPOSITORY TEXT a contributor controls onto a terminal/CI channel,
+  # so it is scrubbed before it is printed, not merely bounded. C0/C1 controls,
+  # bidi overrides, and zero-width characters can erase earlier output, restyle it,
+  # or reorder the rendered row so the named offender is not the one a reader sees —
+  # a length cap does nothing about any of that. Invalid bytes are replaced first so
+  # the escape pass cannot raise on a malformed cell. Both reviewer lanes raised this
+  # independently.
+  CONTROL_OR_INVISIBLE = /[\u0000-\u001F\u007F-\u009F\u200B-\u200F\u2028-\u202E\u2060-\u2064\u206A-\u206F\uFEFF]/.freeze
+  row_label = lambda do |row|
+    cell = row[:line].to_s.sub(/\A\+/, "").split("|")[1].to_s.strip
+    cell = cell.empty? ? row[:line].to_s.strip : cell
+    visible = cell.scrub("?").gsub(CONTROL_OR_INVISIBLE) { |ch| format("\\u%04X", ch.ord) }
+    visible.length > 120 ? "#{visible[0, 117]}..." : visible
+  end
   unless firing_path_failures.empty?
     warn "impact_chain_firing_path_missing: RED-baseline row has no owner-scoped firing path in this committed diff"
     warn "  fix: point to this owner with `firing-path: command:<changed repo executable>` or `firing-path: file:<changed markdown>#<unique token on a changed numbered/list rule with a normative action>`"
-    firing_path_failures.each { |path| warn "  incomplete: #{path}" }
+    warn "  note: the rows named below are the ones that failed — every RED row bound to an owner must resolve, so a row you did not intend to touch can redden the owner. If a named row is one you only EDITED, it became an added row of this round and its original anchor no longer resolves against this round's diff: restore that row rather than rewriting an anchor that was already correct."
+    firing_path_failures.each do |entry|
+      warn "  incomplete: #{entry[:path]}"
+      entry[:rows].each { |row| warn "    offending row: #{row_label.call(row)}" }
+    end
     exit 1
   end
   unless behavior_failures.empty?