blockmine 1.23.4 → 1.25.0

package/.claude/skills/build-engineering/SKILL.md

@@ -1,431 +0,0 @@
----
-description: Build engineering covering build systems (Make, Gradle, Maven, Bazel), compilation optimization, dependency management, artifact repositories, build pipelines, reproducible builds, build caching, monorepo strategies, supply chain security, and performance optimization. Use when creating build processes, optimizing build times, managing dependencies, or implementing CI build pipelines. (project)
----
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-🎯 SKILL ACTIVATED: build-engineering
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-
-# Build Engineering
-
-Comprehensive guide for build engineering covering build systems, compilation optimization, dependency management, artifact repositories, reproducible builds, and modern build practices for creating fast, reliable, and secure build pipelines.
-
-## When to Use This Skill
-
-Automatically activates when working on:
-- Build system configuration (Gradle, Maven, Bazel, Make)
-- Build performance optimization and caching strategies
-- Dependency management and version resolution
-- Artifact repository setup (Artifactory, Nexus)
-- Reproducible builds and hermetic building
-- Monorepo build strategies
-- CI/CD pipeline build optimization
-- Build supply chain security
-- Distributed and parallel builds
-
-## Overview
-
-**Purpose:** Enable teams to create efficient, reliable, and secure build processes that scale from small projects to large monorepos while maintaining build reproducibility and optimizing developer productivity.
-
-**Scope:**
-- Build systems (Make, Gradle, Maven, Bazel, npm/yarn/pnpm)
-- Compilation optimization and distributed builds
-- Dependency management and version pinning
-- Artifact repositories and binary management
-- CI/CD build pipelines and automation
-- Reproducible and hermetic builds
-- Build caching strategies
-- Monorepo build tools and strategies
-- Supply chain security (SBOM, signed artifacts)
-- Build performance optimization
-
-**This skill is for:**
-- Build engineers optimizing build performance
-- DevOps engineers creating CI/CD pipelines
-- Platform engineers managing build infrastructure
-- Developers improving build times
-- Security engineers implementing supply chain security
-
-## Quick Start Checklist
-
-When starting a build engineering task:
-
-- [ ] Choose appropriate build tool for your language/ecosystem
-- [ ] Implement dependency locking for reproducibility
-- [ ] Set up artifact caching (local and remote)
-- [ ] Configure incremental compilation
-- [ ] Implement parallel build execution
-- [ ] Set up artifact repository (Artifactory, Nexus, registry)
-- [ ] Define clear build stages (compile, test, package)
-- [ ] Implement build caching strategy
-- [ ] Add dependency vulnerability scanning
-- [ ] Monitor and optimize build performance
-
-## Core Concepts
-
-### 1. Build System Types
-
-**Make-based:**
-```
-Traditional, file-based dependencies
-Example: Make, CMake
-Best for: C/C++, system-level builds
-```
-
-**JVM-based:**
-```
-Dependency resolution, artifact management
-Example: Maven, Gradle
-Best for: Java, Kotlin, Scala
-```
-
-**Task-based:**
-```
-Flexible task execution
-Example: npm, Gulp, Rake
-Best for: JavaScript, Ruby, general automation
-```
-
-**Hermetic:**
-```
-Fully reproducible, sandboxed builds
-Example: Bazel, Buck, Pants
-Best for: Large monorepos, multi-language projects
-```
-
-### 2. Build Pipeline Stages
-
-```
-┌─────────────────────────────────────────────────┐
-│              Source Code                         │
-└──────────────────┬──────────────────────────────┘
-                   │
-         ┌─────────▼─────────┐
-         │  Dependency Fetch  │
-         │  (with caching)    │
-         └─────────┬─────────┘
-                   │
-         ┌─────────▼─────────┐
-         │   Compilation      │
-         │  (incremental)     │
-         └─────────┬─────────┘
-                   │
-         ┌─────────▼─────────┐
-         │      Testing       │
-         │   (unit, int)      │
-         └─────────┬─────────┘
-                   │
-         ┌─────────▼─────────┐
-         │     Packaging      │
-         │  (artifacts)       │
-         └─────────┬─────────┘
-                   │
-         ┌─────────▼─────────┐
-         │  Artifact Upload   │
-         │   (registry)       │
-         └───────────────────┘
-```
-
-### 3. Dependency Resolution
-
-**Semantic Versioning:**
-```
-MAJOR.MINOR.PATCH
-1.2.3
-
-Major: Breaking changes
-Minor: New features, backward compatible
-Patch: Bug fixes
-```
-
-**Version Constraints:**
-```
-Exact:       1.2.3
-Range:       >=1.2.0 <2.0.0
-Caret:       ^1.2.3  (>=1.2.3 <2.0.0)
-Tilde:       ~1.2.3  (>=1.2.3 <1.3.0)
-```
-
-### 4. Build Caching
-
-**Local Cache:**
-```
-┌──────────────┐
-│  Developer   │
-│   Machine    │
-│              │
-│ Local Cache  │
-│ (~/.cache)   │
-└──────────────┘
-```
-
-**Distributed Cache:**
-```
-┌──────────────┐     ┌──────────────┐     ┌──────────────┐
-│   Dev 1      │     │   Dev 2      │     │  CI Server   │
-└──────┬───────┘     └──────┬───────┘     └──────┬───────┘
-       │                    │                    │
-       └────────────┬───────┴────────────────────┘
-                    │
-            ┌───────▼────────┐
-            │  Remote Cache  │
-            │  (S3, Redis)   │
-            └────────────────┘
-```
-
-### 5. Artifact Versioning
-
-**Versioning Strategies:**
-```
-Semantic:       1.2.3
-Build number:   1.2.3-build.456
-Git commit:     1.2.3-a1b2c3d
-Timestamp:      1.2.3-20240101123045
-Snapshot:       1.2.3-SNAPSHOT
-```
-
-## Common Patterns
-
-### Pattern 1: Multi-Stage Build
-
-```dockerfile
-# Multi-stage Docker build
-FROM node:18 AS builder
-WORKDIR /app
-COPY package*.json ./
-RUN npm ci --only=production
-COPY . .
-RUN npm run build
-
-FROM node:18-alpine AS runtime
-WORKDIR /app
-COPY --from=builder /app/dist ./dist
-COPY --from=builder /app/node_modules ./node_modules
-EXPOSE 3000
-CMD ["node", "dist/index.js"]
-```
-
-### Pattern 2: Dependency Locking
-
-```json
-// package.json
-{
-  "dependencies": {
-    "express": "^4.18.0"
-  }
-}
-
-// package-lock.json (exact versions)
-{
-  "dependencies": {
-    "express": {
-      "version": "4.18.2",
-      "resolved": "https://registry.npmjs.org/express/-/express-4.18.2.tgz",
-      "integrity": "sha512-..."
-    }
-  }
-}
-```
-
-### Pattern 3: Build Matrix
-
-```yaml
-# GitHub Actions build matrix
-jobs:
-  build:
-    strategy:
-      matrix:
-        os: [ubuntu-latest, macos-latest, windows-latest]
-        node: [16, 18, 20]
-    runs-on: ${{ matrix.os }}
-    steps:
-      - uses: actions/checkout@v3
-      - uses: actions/setup-node@v3
-        with:
-          node-version: ${{ matrix.node }}
-      - run: npm ci
-      - run: npm test
-```
-
-### Pattern 4: Incremental Builds
-
-```groovy
-// Gradle incremental compilation
-tasks.withType(JavaCompile) {
-    options.incremental = true
-}
-
-// Only rebuild changed modules
-gradle build --parallel --build-cache --configure-on-demand
-```
-
-## Resource Files
-
-For detailed guidance on specific topics, see:
-
-### Build Systems
-- **[build-systems.md](resources/build-systems.md)** - Make, Gradle, Maven, Bazel, npm/yarn comparison, tool selection guide
-- **[compilation-optimization.md](resources/compilation-optimization.md)** - Compiler flags, incremental compilation, distributed builds, ccache
-- **[monorepo-builds.md](resources/monorepo-builds.md)** - Monorepo strategies, affected detection, Nx, Turborepo, Bazel
-
-### Dependency Management
-- **[dependency-management.md](resources/dependency-management.md)** - Version pinning, lock files, conflict resolution, vulnerability scanning
-- **[artifact-repositories.md](resources/artifact-repositories.md)** - Artifactory, Nexus, container registries, retention policies, promotion
-
-### Build Pipeline
-- **[build-pipelines.md](resources/build-pipelines.md)** - CI build stages, parallel builds, matrix builds, pipeline optimization
-- **[reproducible-builds.md](resources/reproducible-builds.md)** - Deterministic builds, hermetic builds, SLSA framework
-
-### Optimization
-- **[build-caching.md](resources/build-caching.md)** - Layer caching, distributed caching, cache invalidation strategies
-- **[performance-optimization.md](resources/performance-optimization.md)** - Build profiling, parallelization, metrics, bottleneck analysis
-
-### Security
-- **[build-security.md](resources/build-security.md)** - Supply chain security, signed artifacts, SBOM generation, dependency attestation
-
-## Best Practices
-
-### Build Performance
-
-1. **Enable caching:**
-   - Use local and remote build caches
-   - Cache dependencies separately from code
-   - Implement layer caching in Docker builds
-   - Use incremental compilation
-
-2. **Parallelize builds:**
-   - Build independent modules concurrently
-   - Use build tool parallelization features
-   - Distribute builds across multiple machines
-   - Leverage build matrix for testing
-
-3. **Optimize dependencies:**
-   - Remove unused dependencies
-   - Use exact versions in lock files
-   - Implement dependency caching
-   - Consider vendoring for critical dependencies
-
-### Build Reliability
-
-1. **Reproducible builds:**
-   - Pin all dependency versions
-   - Use deterministic build tools
-   - Avoid timestamps in artifacts
-   - Document build environment requirements
-
-2. **Dependency management:**
-   - Use lock files (package-lock.json, Gemfile.lock, go.sum)
-   - Scan for vulnerabilities regularly
-   - Update dependencies systematically
-   - Test dependency updates before merging
-
-3. **Artifact management:**
-   - Version all artifacts
-   - Store in artifact repository
-   - Implement retention policies
-   - Sign critical artifacts
-
-### Build Security
-
-1. **Supply chain security:**
-   - Generate SBOM (Software Bill of Materials)
-   - Sign build artifacts
-   - Verify dependency signatures
-   - Scan for vulnerabilities
-
-2. **Build isolation:**
-   - Use hermetic builds when possible
-   - Sandbox build processes
-   - Limit network access during builds
-   - Verify build inputs
-
-3. **Secret management:**
-   - Never commit secrets to version control
-   - Use secret management tools
-   - Rotate build secrets regularly
-   - Audit secret access
-
-## Anti-Patterns to Avoid
-
-❌ **Non-reproducible builds** - Different results from same source
-❌ **No dependency locking** - Floating versions break builds
-❌ **Rebuilding everything** - Wastes time and resources
-❌ **No build caching** - Repeated work on every build
-❌ **Ignored dependencies** - Outdated, vulnerable packages
-❌ **No artifact versioning** - Can't track what was deployed
-❌ **Serial builds** - Not leveraging parallelization
-❌ **No build metrics** - Can't identify bottlenecks
-❌ **Mixing build and runtime** - Bloated containers
-❌ **No vulnerability scanning** - Security risks in dependencies
-
-## Common Tasks
-
-### Task: Optimize Slow Build
-
-1. Profile build to identify bottlenecks
-2. Enable build caching (local and remote)
-3. Implement incremental compilation
-4. Parallelize independent build tasks
-5. Cache dependencies separately
-6. Use build tool's parallel features
-7. Consider distributed builds for large projects
-8. Monitor build metrics over time
-
-### Task: Set Up Artifact Repository
-
-1. Choose repository (Artifactory, Nexus, registry)
-2. Deploy and configure repository
-3. Set up authentication and access control
-4. Define retention policies
-5. Configure build tools to publish artifacts
-6. Implement versioning strategy
-7. Set up vulnerability scanning
-8. Document artifact promotion workflow
-
-### Task: Implement Reproducible Builds
-
-1. Pin all dependency versions
-2. Use lock files for dependencies
-3. Specify build tool versions
-4. Document build environment
-5. Remove non-deterministic elements (timestamps)
-6. Use hermetic build tools if possible
-7. Verify builds are reproducible
-8. Automate verification in CI
-
-## Integration Points
-
-This skill integrates with:
-- **release-engineering**: Deployment pipelines, versioning, artifact promotion
-- **devsecops**: Vulnerability scanning, SBOM, supply chain security
-- **platform-engineering**: Build infrastructure, container builds, Kubernetes
-- **cloud-engineering**: Cloud build services, artifact storage
-- **systems-engineering**: Compiler optimization, system dependencies
-
-## Triggers and Activation
-
-This skill activates when you:
-- Work with build files (Makefile, build.gradle, pom.xml, package.json)
-- Optimize build performance or reduce build times
-- Implement CI/CD pipelines
-- Manage dependencies or artifact repositories
-- Configure build caching or distributed builds
-- Set up monorepo build tooling
-- Implement reproducible builds
-- Address supply chain security
-
-## Next Steps
-
-For your specific build engineering task:
-1. Identify build system and language ecosystem
-2. Review relevant patterns and optimization strategies
-3. Implement caching and parallelization
-4. Set up artifact management
-5. Monitor and optimize build performance
-6. Implement security scanning and SBOM generation
-
----
-
-**Total Resources:** 10 detailed guides covering all aspects of build engineering
-**Pattern Library:** 100+ production-tested patterns for build optimization and reliability
-**Maintained by:** Build Engineering team based on real-world production experience

package/.claude/skills/build-engineering/resources/artifact-repositories.md

@@ -1,72 +0,0 @@
-# Artifact Repositories
-
-Guide to artifact repositories including Artifactory, Nexus, container registries, and retention policies.
-
-## Overview
-
-Artifact repositories store binary artifacts, providing versioning, access control, and efficient distribution.
-
-## Artifactory
-
-### Setup
-```yaml
-apiVersion: apps/v1
-kind: StatefulSet
-metadata:
-  name: artifactory
-spec:
-  serviceName: artifactory
-  replicas: 1
-  template:
-    spec:
-      containers:
-      - name: artifactory
-        image: docker.bintray.io/jfrog/artifactory-oss:latest
-        ports:
-        - containerPort: 8081
-        volumeMounts:
-        - name: data
-          mountPath: /var/opt/jfrog/artifactory
-```
-
-### Configuration
-```bash
-# Upload artifact
-curl -u user:password -T artifact.jar \
-  "http://artifactory:8081/artifactory/libs-release/com/example/artifact/1.0.0/artifact-1.0.0.jar"
-```
-
-## Nexus
-
-### Docker Registry
-```bash
-# Login
-docker login nexus.example.com
-
-# Push
-docker tag myapp:1.0 nexus.example.com/myapp:1.0
-docker push nexus.example.com/myapp:1.0
-```
-
-## Retention Policies
-
-### Time-based
-- Delete artifacts older than 90 days
-- Keep last N versions
-
-### Space-based
-- Delete when storage exceeds threshold
-- Keep minimum N versions
-
-## Best Practices
-
-1. **Implement retention** - Automatic cleanup
-2. **Use access control** - Role-based permissions
-3. **Enable replication** - Multi-region availability
-4. **Scan artifacts** - Vulnerability scanning
-5. **Version everything** - No overwrites
-6. **Use staging** - Promote through environments
-7. **Monitor usage** - Storage and bandwidth
-8. **Backup regularly** - Disaster recovery
-9. **Use CDN** - For public artifacts
-10. **Document policies** - Clear retention rules

package/.claude/skills/build-engineering/resources/build-caching.md

@@ -1,96 +0,0 @@
-# Build Caching
-
-Guide to build caching strategies including layer caching, distributed caching, and cache invalidation.
-
-## Overview
-
-Build caching dramatically reduces build times by reusing previously built artifacts.
-
-## Docker Layer Caching
-
-```dockerfile
-FROM node:18
-
-# Cache dependencies separately
-COPY package*.json ./
-RUN npm ci
-
-# Copy source (changes more frequently)
-COPY . .
-RUN npm run build
-```
-
-## Gradle Build Cache
-
-```kotlin
-// gradle.properties
-org.gradle.caching=true
-org.gradle.caching.debug=false
-
-// settings.gradle.kts
-buildCache {
-    local {
-        directory = File(rootDir, "build-cache")
-        removeUnusedEntriesAfterDays = 30
-    }
-    
-    remote<HttpBuildCache> {
-        url = uri("https://cache.example.com/cache/")
-        isPush = System.getenv("CI") != null
-        credentials {
-            username = "cache-user"
-            password = System.getenv("CACHE_PASSWORD")
-        }
-    }
-}
-```
-
-## npm/yarn Cache
-
-```bash
-# npm cache
-npm ci --cache /tmp/npm-cache
-
-# yarn cache
-yarn install --cache-folder /tmp/yarn-cache
-
-# pnpm store
-pnpm install --store-dir /tmp/pnpm-store
-```
-
-## Bazel Remote Cache
-
-```python
-# .bazelrc
-build --remote_cache=grpc://cache.example.com:8980
-build --experimental_remote_downloader=grpc://cache.example.com:8980
-```
-
-## Cache Invalidation
-
-### Content-Based
-```bash
-# Hash file contents
-CACHE_KEY=$(sha256sum package-lock.json | cut -d' ' -f1)
-```
-
-### Time-Based
-- Expire after N days
-- Refresh on access
-
-### Manual
-- Clear on major changes
-- Version-based invalidation
-
-## Best Practices
-
-1. **Layer wisely** - Dependencies before code
-2. **Use remote cache** - Team-wide benefits
-3. **Content-based keys** - Hash file contents
-4. **Set size limits** - Prevent unlimited growth
-5. **Monitor hit rate** - Track effectiveness
-6. **Clean old entries** - Automatic cleanup
-7. **Secure cache** - Access control
-8. **Test without cache** - Verify correctness
-9. **Document strategy** - Clear policies
-10. **Measure impact** - Before/after metrics

package/.claude/skills/build-engineering/resources/build-pipelines.md

@@ -1,105 +0,0 @@
-# Build Pipelines
-
-Guide to CI/CD build pipelines including stages, parallel builds, matrix builds, and optimization.
-
-## Overview
-
-Build pipelines automate the process from code commit to artifact creation.
-
-## Pipeline Stages
-
-```yaml
-# GitHub Actions
-name: Build Pipeline
-
-on: [push, pull_request]
-
-jobs:
-  build:
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v3
-      
-      - name: Setup Node
-        uses: actions/setup-node@v3
-        with:
-          node-version: 18
-          cache: 'npm'
-      
-      - name: Install
-        run: npm ci
-      
-      - name: Lint
-        run: npm run lint
-      
-      - name: Test
-        run: npm test
-      
-      - name: Build
-        run: npm run build
-      
-      - name: Upload Artifact
-        uses: actions/upload-artifact@v3
-        with:
-          name: dist
-          path: dist/
-```
-
-## Matrix Builds
-
-```yaml
-jobs:
-  test:
-    strategy:
-      matrix:
-        os: [ubuntu-latest, macos-latest, windows-latest]
-        node: [16, 18, 20]
-        include:
-          - os: ubuntu-latest
-            node: 20
-            coverage: true
-    runs-on: ${{ matrix.os }}
-    steps:
-      - uses: actions/checkout@v3
-      - uses: actions/setup-node@v3
-        with:
-          node-version: ${{ matrix.node }}
-      - run: npm ci
-      - run: npm test
-      - if: matrix.coverage
-        run: npm run coverage
-```
-
-## Parallel Execution
-
-```yaml
-jobs:
-  lint:
-    runs-on: ubuntu-latest
-    steps:
-      - run: npm run lint
-  
-  test:
-    runs-on: ubuntu-latest
-    steps:
-      - run: npm test
-  
-  build:
-    needs: [lint, test]
-    runs-on: ubuntu-latest
-    steps:
-      - run: npm run build
-```
-
-## Best Practices
-
-1. **Fail fast** - Run quick tests first
-2. **Parallel stages** - Independent steps in parallel
-3. **Cache dependencies** - Reuse between builds
-4. **Matrix builds** - Test multiple configurations
-5. **Artifact management** - Upload build outputs
-6. **Clear stages** - Logical separation
-7. **Timeout limits** - Prevent hanging builds
-8. **Retry failed steps** - Handle flaky tests
-9. **Environment parity** - Match production
-10. **Monitor metrics** - Track build times