shirobai 2026.0920.1100 → 2026.1011.1700

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: f65a6269e60ead3a7b5175cad5be36b3364bb5ee6025dd7bcc3a2b82d69466c6
-  data.tar.gz: 6af011435008fec04f1a8bced1d5e5d620160b465b6a290963fcfcda1561a8a2
+  metadata.gz: 97a258d6becce46c59a16ce1659d18d250d8892010e53b7209490c92bac0dcd8
+  data.tar.gz: 1bbeb45364147af576d9f9e8e5cbc5921744d810b6a728d66f6c4703d006b8af
 SHA512:
-  metadata.gz: d88a4fc322d82e59683f33de8d8a3ae93a62f59ac358dc583a83201ccf3db4021a5076ac60a4a5ba60802d557ab8d18ad3771d6be40a1c01268582aa4083e743
-  data.tar.gz: 2cee35078890630d5291e962e5fb6d6a9c2f49a4595bd1b212ead6db8aaff8a73aa8460845e11d49d2360d26680d2006bbde79b2ba7c2646e6fbbbefa2b48032
+  metadata.gz: ac3a9f7f093637230f0f1e5272994b8e39e70fc15b351fcca3352549480bd79767fc8f3f0a8de6697779b4b066a335010ab0af7b05f55a41552f127840ba03b1
+  data.tar.gz: 12762cd7df2a9be40e98236f569ac8ba1dda3e6ea6d3385129d94428063d0659b774a872dc74887d4065fe2c067a242fbb3dbf19d2c4ae1354ac99b0814e4d01

data/Cargo.lock

@@ -356,7 +356,7 @@ checksum = "dc6fe69c597f9c37bfeeeeeb33da3530379845f10be461a66d16d03eca2ded77"
 
 [[package]]
 name = "shirobai"
-version = "2026.920.1100"
+version = "2026.1011.1700"
 dependencies = [
  "magnus",
  "shirobai-core",
@@ -364,7 +364,7 @@ dependencies = [
 
 [[package]]
 name = "shirobai-core"
-version = "2026.920.1100"
+version = "2026.1011.1700"
 dependencies = [
  "libc",
  "ruby-prism",

data/Cargo.toml

@@ -7,7 +7,7 @@ resolver = "3"
 # is crate 2026.709.0 -- cargo rejects leading zeros in numeric segments, and
 # Gem::Version normalizes to the same integers, so the two stay value-equal).
 [workspace.package]
-version = "2026.920.1100"
+version = "2026.1011.1700"
 
 # Release tuning. The hot path crosses crate boundaries (ext cdylib -> core
 # check_* -> ruby-prism); without LTO the cross-crate calls are not inlined and

data/crates/shirobai-core/src/rules/abc_size.rs

@@ -45,6 +45,7 @@ use super::complexity::{define_method_info, is_iterating};
 /// Per-method ABC result. The Ruby side derives the score
 /// (`Math.sqrt(a**2 + b**2 + c**2).round(2)`), the vector string and the
 /// offense message, so floats never cross the FFI boundary.
+#[derive(Debug)]
 pub struct AbcMethod {
     pub start_offset: usize,
     pub end_offset: usize,

data/crates/shirobai-core/src/rules/access_modifier_indentation.rs

@@ -55,6 +55,7 @@ pub struct Config {
 /// non-zero (the wrapper then emits an offense and an `AlignmentCorrector`
 /// shift); `None` means the modifier already aligns with the configured style
 /// (the wrapper calls `correct_style_detected`).
+#[derive(Debug)]
 pub struct AccessModifierIndentationRecord {
     /// `bare_access_modifier?` send range (offense highlight).
     pub start: usize,
@@ -63,6 +64,7 @@ pub struct AccessModifierIndentationRecord {
     pub offense: Option<AccessModifierIndentationOffense>,
 }
 
+#[derive(Debug)]
 pub struct AccessModifierIndentationOffense {
     /// Formatted stock `MSG`: `"<Style> access modifiers like `<name>`."`.
     pub message: String,

data/crates/shirobai-core/src/rules/argument_alignment.rs

@@ -19,6 +19,7 @@ use super::line_index::LineIndex;
 /// One misaligned argument. `column_delta` is `base_column - actual_column`
 /// (display columns). `autocorrect` is false for offenses nested inside an
 /// already-registered offense range (the mixin's `within?` rule).
+#[derive(Debug)]
 pub struct ArgAlignOffense {
     pub start_offset: usize,
     pub end_offset: usize,

data/crates/shirobai-core/src/rules/arguments_forwarding.rs

@@ -61,6 +61,7 @@ pub struct Config {
 }
 
 /// One `add_offense` call in stock's order (range + message + corrector ops).
+#[derive(Debug)]
 pub struct AfOffense {
     pub start: usize,
     pub end: usize,
@@ -70,6 +71,7 @@ pub struct AfOffense {
 }
 
 /// A corrector op. `kind`: 0 replace, 1 remove, 2 insert_before, 3 insert_after.
+#[derive(Debug)]
 pub struct AfOp {
     pub kind: u8,
     pub start: usize,

data/crates/shirobai-core/src/rules/array_alignment.rs

@@ -35,6 +35,7 @@ use super::line_index::LineIndex;
 /// One misaligned element. `column_delta` is `base_column - actual_column`
 /// (display columns). `autocorrect` is false for offenses nested inside an
 /// already-registered offense range (the mixin's `within?` rule).
+#[derive(Debug)]
 pub struct ArrayAlignOffense {
     pub start_offset: usize,
     pub end_offset: usize,

data/crates/shirobai-core/src/rules/assignment_indentation.rs

@@ -40,6 +40,7 @@ use super::line_index::LineIndex;
 /// One misindented RHS first-line. `column_delta` is
 /// `expected_column - actual_column` (positive => the RHS line must move
 /// right). The message is fixed at `MSG`.
+#[derive(Debug)]
 pub struct AssignmentIndentationOffense {
     /// `[rhs_start, rhs_end)` is the RHS's full source range. The offense
     /// reports against this range; autocorrect shifts every line of it.

data/crates/shirobai-core/src/rules/block_alignment.rs

@@ -47,6 +47,7 @@ const STYLE_START_OF_BLOCK: u8 = 1;
 const STYLE_START_OF_LINE: u8 = 2;
 
 /// One checked block whose closing token is misaligned (an offense).
+#[derive(Debug)]
 pub struct BlockAlignmentOffense {
     /// Closing token range (`end` or `}`) — the offense location.
     pub end_start: usize,

data/crates/shirobai-core/src/rules/block_delimiters.rs

@@ -62,6 +62,7 @@ pub struct Candidate {
 }
 
 /// The resolved (all-offenses-enabled) outcome for one source.
+#[derive(Debug, Default)]
 pub struct BlockDelimitersResult {
     pub offenses: Vec<Candidate>,
     /// Blocks ignored by `on_send`, for the wrapper's cross-pass bookkeeping.

data/crates/shirobai-core/src/rules/block_length.rs

@@ -8,6 +8,7 @@ use super::code_length::{CodeLength, Fold};
 /// `AllowedMethods` exclusion (incl. receiver-qualified entries) is applied
 /// here too; the regex-based `AllowedPatterns` filtering always stays on the
 /// Ruby side, which has the exact regexp semantics.
+#[derive(Debug)]
 pub struct BlockLengthCandidate {
     pub start_offset: usize,
     pub end_offset: usize,

data/crates/shirobai-core/src/rules/block_nesting.rs

@@ -16,6 +16,7 @@ use ruby_prism::{Node, Visit};
 /// One reportable offense: the byte range of the offending node. The highlight
 /// is truncated to the first line by RuboCop's offense formatter, so only the
 /// start offset (caret position) and first-line span matter.
+#[derive(Debug)]
 pub struct BlockNestingOffense {
     pub start_offset: usize,
     pub end_offset: usize,