fix instructions

Signed-off-by: Gregor Zeitlinger <gregor.zeitlinger@grafana.com>

Author: zeitlinger

CLAUDE.md

@@ -69,19 +69,46 @@ Pre-built instrumentations: `prometheus-metrics-instrumentation-jvm`, `-caffeine
 ## Code Style
 
 - **Formatter**: Google Java Format (enforced via Spotless)
-- **Line length**: 100 characters
+- **Line length**: 100 characters (enforced for ALL files including Markdown, Java, YAML, etc.)
 - **Indentation**: 2 spaces
 - **Static analysis**: Error Prone with NullAway (`io.prometheus.metrics` package)
 - **Logger naming**: Logger fields must be named `logger` (not `log`, `LOG`, or `LOGGER`)
 - **Assertions in tests**: Use static imports from AssertJ (`import static org.assertj.core.api.Assertions.assertThat`)
 - **Empty catch blocks**: Use `ignored` as the exception variable name
+- **Markdown code blocks**: Always specify language (e.g., ` ```java`, ` ```bash`, ` ```text`)
 
 ## Linting and Validation
 
-- **IMPORTANT**: Always run `mise run build` after modifying Java files to ensure all lints, code formatting (Spotless), static analysis (Error Prone), and checkstyle checks pass
-- **IMPORTANT**: Always run `mise run lint:super-linter` after modifying non-Java files (YAML, Markdown, shell scripts, JSON, etc.)
-- Super-linter is configured to only show ERROR-level messages via `LOG_LEVEL=ERROR` in `.github/super-linter.env`
-- Local super-linter version is pinned to match CI (see `.mise/tasks/lint/super-linter.sh`)
+**CRITICAL**: These checks MUST be run before creating any commits. CI will fail if these checks fail.
+
+### Java Files
+
+- **ALWAYS** run `mise run build` after modifying Java files to ensure:
+  - Code formatting (Spotless with Google Java Format)
+  - Static analysis (Error Prone with NullAway)
+  - Checkstyle validation
+  - All tests pass
+
+### Non-Java Files (Markdown, YAML, JSON, shell scripts, etc.)
+
+- **ALWAYS** run `mise run lint:super-linter` after modifying non-Java files
+- Super-linter will **auto-fix** many issues (formatting, trailing whitespace, etc.)
+- It only reports ERROR-level issues (configured via `LOG_LEVEL=ERROR` in `.github/super-linter.env`)
+- Common issues caught:
+  - Lines exceeding 100 characters in Markdown files
+  - Missing language tags in fenced code blocks
+  - Table formatting issues
+  - YAML/JSON syntax errors
+
+### Running Linters
+
+```bash
+# After modifying Java files (run BEFORE committing)
+mise run build
+
+# After modifying non-Java files (run BEFORE committing)
+mise run lint:super-linter
+```
 
 ## Testing
 

CUSTOM_BUCKETS_VERIFICATION.md

@@ -7,6 +7,7 @@ Prometheus converts them to native histograms with schema -53.
 ## What are Native Histograms with Custom Buckets?
 
 Native Histograms with Custom Buckets (NHCB) is a Prometheus feature that combines the benefits of:
+
 - **Custom bucket boundaries**: Precisely defined buckets optimized for your specific use case
 - **Native histograms**: Efficient storage and querying capabilities of native histograms
 
@@ -88,7 +89,7 @@ The Prometheus configuration enables NHCB conversion:
 ```yaml
 scrape_configs:
   - job_name: "custom-buckets-demo"
-    scrape_protocols: ['PrometheusProto']
+    scrape_protocols: ["PrometheusProto"]
     convert_classic_histograms_to_nhcb: true
     scrape_classic_histograms: true
 ```
@@ -111,6 +112,7 @@ api_request_duration_seconds
 ### 3. View in Grafana
 
 The Grafana dashboard at [http://localhost:3000](http://localhost:3000) shows:
+
 - p95 and p50 latencies for API endpoints (arbitrary custom buckets)
 - Queue size distribution (linear buckets)
 - Response size distribution (exponential buckets)
@@ -143,12 +145,12 @@ Consider using custom buckets (and NHCB) when:
 
 ## Differences from Standard Native Histograms
 
-| Feature | Standard Native Histograms | NHCB (Schema -53) |
-|---------|---------------------------|-------------------|
-| Bucket boundaries | Exponential (base 2^(2^-scale)) | Custom boundaries |
-| Use case | General-purpose | Specific distributions |
-| Mergeability | Can merge histograms with same schema | Cannot merge with different boundaries |
-| Configuration | Schema level (0-8) | Explicit boundary list |
+| Feature           | Standard Native Histograms            | NHCB (Schema -53)                      |
+| ----------------- | ------------------------------------- | -------------------------------------- |
+| Bucket boundaries | Exponential (base 2^(2^-scale))       | Custom boundaries                      |
+| Use case          | General-purpose                       | Specific distributions                 |
+| Mergeability      | Can merge histograms with same schema | Cannot merge with different boundaries |
+| Configuration     | Schema level (0-8)                    | Explicit boundary list                 |
 
 ## Cleanup
 

examples/example-custom-buckets/README.md

@@ -5,7 +5,7 @@ global:
 scrape_configs:
   - job_name: "custom-buckets-demo"
     # Use protobuf format to receive native histogram data
-    scrape_protocols: ['PrometheusProto']
+    scrape_protocols: ["PrometheusProto"]
     # Convert classic histograms with custom buckets to NHCB (schema -53)
     convert_classic_histograms_to_nhcb: true
     # Also scrape classic histograms for comparison