kind 6.0.0 → 6.0.1

data/CLAUDE.md

@@ -0,0 +1,117 @@
+# CLAUDE.md
+
+Notes for AI assistants working in `kind`.
+
+## How to work in this repo
+
+### 1. Think before coding
+
+**Don't assume. Don't hide confusion. Surface tradeoffs.**
+
+- State assumptions explicitly. If uncertain, ask.
+- If multiple interpretations exist, present them — don't pick silently.
+- If a simpler approach exists, say so. Push back when warranted.
+- If something is unclear, stop. Name what's confusing. Ask.
+
+### 2. Simplicity first
+
+**Minimum code that solves the problem. Nothing speculative.**
+
+- No features beyond what was asked.
+- No abstractions for single-use code.
+- No "flexibility" or "configurability" that wasn't requested.
+- No error handling for impossible scenarios.
+- If you write 200 lines and it could be 50, rewrite it.
+
+Ask yourself: "Would a senior engineer say this is overcomplicated?" If yes,
+simplify.
+
+### 3. Surgical changes
+
+**Touch only what you must. Clean up only your own mess.**
+
+- Don't "improve" adjacent code, comments, or formatting.
+- Don't refactor things that aren't broken.
+- Match existing style, even if you'd do it differently.
+- If you notice unrelated dead code, mention it — don't delete it.
+- Remove imports/variables/functions that _your_ changes orphaned. Don't
+  remove pre-existing dead code unless asked.
+
+The test: every changed line should trace directly to the user's request.
+
+### 4. Goal-driven execution
+
+**Define success criteria. Loop until verified.**
+
+Turn vague tasks into verifiable goals:
+
+- "Add validation" → "Write tests for invalid inputs, then make them pass"
+- "Fix the bug" → "Write a test that reproduces it, then make it pass"
+- "Refactor X" → "Ensure tests pass before and after"
+
+For multi-step work, state a brief plan with a verification check per step.
+
+---
+
+## What this is
+
+`kind` is a zero-runtime-dependency Ruby toolkit organized as a collection of
+small, cohesive modules under `lib/kind/` — type handlers (`Kind::String`,
+`Kind::Of()`, `Kind.object`), monads (`Kind::Maybe`, `Kind::Either`,
+`Kind::Result`), enums (`Kind::Enum`), immutable objects
+(`Kind::ImmutableAttributes`), business-logic helpers (`Kind::Action`,
+`Kind::Functional::Steps`, `Kind::Functional::Action`), and an optional
+ActiveModel validator (`Kind::Validator`). Everything is modularized: callers
+require what they want (`require 'kind/basic'`, `require 'kind/either'`,
+`require 'kind/any'`, …), and the umbrella `require 'kind'` loads the lot.
+Because `kind` is a leaf dependency for `u-case` and other downstream gems,
+behavior changes — especially anything affecting the public API or the
+supported `ruby` / `activemodel` matrix — are highly visible.
+
+## Running tests
+
+```bash
+bundle exec rake test                  # default suite, current bundle
+bundle exec appraisal <name> rake test # one ActiveModel appraisal (see Appraisals)
+bundle exec rake test_basic_modules    # per-module isolation runs (KIND_BASIC) + KIND_STRICT
+bundle exec rake matrix                # full local matrix for the active Ruby
+```
+
+`bin/setup` re-installs and refreshes appraisals. `bin/matrix` reinstalls then
+runs `rake matrix`. CI runs the matrix across the full Ruby × ActiveModel grid
+plus the per-module (`KIND_BASIC`) and `KIND_STRICT` axes. Tests are the
+success criterion for any behavior change — write or update a test first, then
+make it pass (rule 4).
+
+## CHANGELOG and README are part of every change
+
+Both files are user-facing — keep them in sync with the code:
+
+- **`CHANGELOG.md`**: follows [Keep a Changelog 1.1.0](https://keepachangelog.com/en/1.1.0/).
+  Every user-visible change (new API, behavior change, breaking change, dep
+  bump that shifts the supported matrix, security fix) gets a bullet under
+  the appropriate section (`Added` / `Changed` / `Deprecated` / `Removed` /
+  `Fixed` / `Security`). Pure README/CI/internal-refactor changes generally
+  don't need an entry.
+- **`README.md`**: the **Documentation** table and the **Compatibility** table
+  at the top reference the latest released version and its supported Ruby ×
+  ActiveModel bounds. Update them when you cut a release. If you change a
+  documented API, update the relevant section in the same commit.
+
+## Bumping the version
+
+1. Edit `lib/kind/version.rb` — change `Kind::VERSION`. Follow
+   [SemVer](https://semver.org/): patch for fixes, minor for additive
+   user-visible changes, major for breaking changes.
+2. Add a new top entry in `CHANGELOG.md` (`## [X.Y.Z] - YYYY-MM-DD`) and a
+   matching compare link at the bottom (`[X.Y.Z]: …/compare/vPREV...vX.Y.Z`).
+3. Update `README.md`:
+   - **Documentation** table → bump the `v6.x` (or current major) row's
+     version label.
+   - **Compatibility** table → if supported Ruby / ActiveModel bounds
+     changed, add a new row; otherwise bump the existing row's version label.
+4. If the supported matrix moved, double-check the Compatibility table, the
+   Ruby × Rails CI matrix below it, and the `Appraisals` file reflect the
+   new bounds.
+
+Don't tag, push, or `gem release` — humans do that.

data/README.md

@@ -26,7 +26,7 @@ So, I invite you to check out these features to see how they could be useful for
 Version    | Documentation
 ---------- | -------------
 unreleased | https://github.com/serradura/kind/blob/main/README.md
-6.0.0      | https://github.com/serradura/kind/blob/v6.x/README.md
+6.0.1      | https://github.com/serradura/kind/blob/v6.x/README.md
 5.10.0     | https://github.com/serradura/kind/blob/v5.x/README.md
 
 ## Table of Contents <!-- omit in toc -->
@@ -106,7 +106,7 @@ unreleased | https://github.com/serradura/kind/blob/main/README.md
 | kind             | branch | ruby     | activemodel    |
 | ---------------- | ------ | -------- | -------------- |
 | unreleased       | main   | >= 2.7   | >= 6.0         |
-| 6.0.0            | v6.x   | >= 2.7   | >= 6.0         |
+| 6.0.1            | v6.x   | >= 2.7   | >= 6.0         |
 | 5.10.0           | v5.x   | >= 2.1.0, <= 3.0.0 | >= 3.2, < 7.0  |
 
 This library is tested (CI matrix) against:

data/kind.gemspec

@@ -15,6 +15,7 @@ Gem::Specification.new do |spec|
   spec.metadata['homepage_uri'] = spec.homepage
   spec.metadata['source_code_uri'] = 'https://github.com/serradura/kind'
   spec.metadata['changelog_uri'] = 'https://github.com/serradura/kind/blob/main/CHANGELOG.md'
+  spec.metadata['bug_tracker_uri'] = "#{spec.homepage}/issues"
 
   # Specify which files should be added to the gem when it is released.
   # The `git ls-files -z` loads the files in the RubyGem that have been added into git.

data/lib/kind/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module Kind
-  VERSION = '6.0.0'
+  VERSION = '6.0.1'
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: kind
 version: !ruby/object:Gem::Version
-  version: 6.0.0
+  version: 6.0.1
 platform: ruby
 authors:
 - Rodrigo Serradura
@@ -66,6 +66,7 @@ files:
 - ".vscode/settings.json"
 - Appraisals
 - CHANGELOG.md
+- CLAUDE.md
 - CODE_OF_CONDUCT.md
 - Gemfile
 - LICENSE.txt
@@ -173,6 +174,7 @@ metadata:
   homepage_uri: https://github.com/serradura/kind
   source_code_uri: https://github.com/serradura/kind
   changelog_uri: https://github.com/serradura/kind/blob/main/CHANGELOG.md
+  bug_tracker_uri: https://github.com/serradura/kind/issues
 rdoc_options: []
 require_paths:
 - lib
@@ -187,7 +189,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 4.0.7
+rubygems_version: 4.0.12
 specification_version: 4
 summary: A development toolkit for Ruby with several small/cohesive abstractions to
   empower your development workflow.