verify_it 0.1.0

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA256:
+  metadata.gz: ef477abbd90cd2cccf84c643e7d2f9701f0156a9f98d2ac8540af3faad6cc296
+  data.tar.gz: 45a42d67357c0fb8f57c40f371274b97c80d5c2369a386758f15be965e11e3c2
+SHA512:
+  metadata.gz: 8deb185375b951d67087946e05512db44eca245dde3a6054b664745b41f0753fecb2b5702efd6ce58ac461cf86413ef15634f5f4452d2738b31b17e076f5eb6c
+  data.tar.gz: bfe9967aad2dacc5c62bfa8dc16dd9adfbec268be7a2bf2e160d36c2edc18b5cdcbad33b41fc5aee2d4e8fb6ea630c4b9557a0e295f3c20794057afec292b705

data/AGENTS.md

@@ -0,0 +1,140 @@
+# AGENTS.md
+
+This file contains strict operational rules for AI agents working in this repository.
+
+These rules are mandatory.
+
+---
+
+# Agent Operating Guidelines
+
+## 1. Always Preserve and Expand Specs
+
+You MUST:
+
+- Create specs for all new behavior.
+- Update specs when modifying behavior.
+- Add regression specs for bug fixes.
+- Never delete existing specs unless replacing them.
+
+If behavior changes, specs must reflect that change.
+
+No implementation without specs.
+
+---
+
+## 2. Use Bundler Conventions Only
+
+This gem MUST follow Bundler’s official structure:
+
+https://bundler.io/guides/creating_gem.html
+
+Do not invent custom layouts.
+
+Standard structure:
+
+- lib/
+- lib/verify_it.rb
+- lib/verify_it/version.rb
+- spec/
+- verify_it.gemspec
+- Gemfile
+
+---
+
+## 3. Maintain Production-Grade Standards
+
+All generated code must:
+
+- Be thread-safe
+- Avoid global mutable state
+- Avoid monkey patching
+- Avoid runtime metaprogramming unless necessary
+- Avoid unexpected side effects
+
+---
+
+## 4. API Stability
+
+Agents must:
+
+- Treat public methods as stable API
+- Avoid renaming public methods
+- Avoid changing method signatures without version bump
+- Avoid altering return types silently
+
+If a breaking change is introduced:
+- Bump MAJOR version
+- Update changelog
+- Update README
+- Update specs
+
+---
+
+## 5. Dependency Discipline
+
+Agents MUST NOT:
+
+- Add runtime dependencies casually
+- Introduce large frameworks
+- Add HTTP clients unless required
+- Add ActiveSupport unless justified
+
+Prefer pure Ruby implementations.
+
+---
+
+## 6. Code Style Requirements
+
+- Ruby 3.x compatible
+- Frozen string literal headers
+- No unused variables
+- No commented-out code
+- No debug prints
+- RuboCop clean
+
+---
+
+## 7. Error Handling Rules
+
+- Raise explicit errors for invalid input.
+- Avoid silent failures.
+- Use custom error classes when appropriate.
+- Document raised exceptions.
+
+---
+
+## 8. Documentation Requirements
+
+Agents must update:
+
+- README.md for new features
+- CHANGELOG.md
+- YARD documentation
+
+Documentation is part of the feature.
+
+---
+
+## 9. Release Integrity
+
+Before suggesting a release:
+
+- All specs pass
+- Lint passes
+- Version is bumped correctly
+- Changelog updated
+- README updated
+
+---
+
+## 10. Golden Rule
+
+If uncertain:
+- Add a spec.
+- Prefer explicit behavior.
+- Avoid cleverness.
+- Prefer clarity.
+
+This gem is intended to be production-grade and long-lived.
+Act accordingly.

data/CHANGELOG.md

@@ -0,0 +1,32 @@
+## [Unreleased]
+
+### Added
+- CLI installer command (`verify_it install`) for Rails applications
+- Interactive storage backend selection (Memory, Redis, Database)
+- Automatic initializer generation with storage-specific configuration
+- Automatic migration generation for database storage
+- Comprehensive CLI specs
+
+## [0.1.0] - 2026-03-01
+
+### Added
+- Core verification system with send and verify operations
+- Storage adapters: Memory and Redis
+- Configurable rate limiting system
+- Support for SMS and Email delivery channels
+- Result object with comprehensive status information
+- Code generator with multiple formats (numeric, alphanumeric, alpha)
+- Thread-safe operations
+- Test mode for exposing codes without delivery
+- Rails integration via Railtie and Verifiable concern
+- Lifecycle callbacks (on_send, on_verify_success, on_verify_failure)
+- Namespace support for multi-tenant applications
+- Comprehensive RSpec test suite
+- Full API documentation in README
+
+### Security
+- Rate limiting for send attempts
+- Rate limiting for verification attempts
+- Rate limiting for identifier changes
+- Automatic lockout after max failed attempts
+- Code expiration with configurable TTL

data/CLAUDE.md

@@ -0,0 +1,132 @@
+# CLAUDE.md
+
+## Project Context
+
+This repository contains a production-grade Ruby gem built using Bundler
+(`bundle gem verify_it --test=rspec --ci=github --mit`).
+
+This gem is expected to:
+
+- Follow Ruby idioms and best practices
+- Be fully tested
+- Maintain backward compatibility
+- Be safe for production usage
+- Be suitable for publishing to RubyGems
+
+All development MUST preserve these guarantees.
+
+---
+
+## Core Development Rules
+
+### 1. Tests Are Mandatory
+
+- Every feature must include RSpec coverage.
+- Every bug fix must include a failing spec first.
+- Specs must be deterministic and not rely on external services.
+- No feature is complete without tests.
+
+If specs break, they must be fixed immediately.
+
+---
+
+### 2. Backward Compatibility
+
+This gem follows Semantic Versioning (SemVer):
+
+- PATCH: bug fixes
+- MINOR: backward-compatible features
+- MAJOR: breaking changes
+
+Do not introduce breaking changes without:
+
+- Updating the version
+- Documenting the change
+- Updating the changelog
+- Updating affected specs
+
+---
+
+### 3. Public API Discipline
+
+- Clearly separate public vs private methods.
+- Public methods must be documented with YARD.
+- Internal implementation details must not leak.
+
+Avoid expanding the public API surface unnecessarily.
+
+---
+
+### 4. Dependency Rules
+
+- Prefer zero runtime dependencies.
+- Every dependency must be justified.
+- Development dependencies go in the gemspec under development dependencies.
+- Do not introduce heavy dependencies without strong reason.
+
+---
+
+### 5. Code Quality Standards
+
+- Ruby 3.x compatible
+- Frozen string literal headers
+- RuboCop compliant
+- Small, composable objects
+- No global state
+- No monkey patching
+
+---
+
+### 6. Performance & Safety
+
+- Avoid unnecessary allocations
+- Avoid reflection-heavy logic unless justified
+- Fail fast on invalid inputs
+- Validate arguments explicitly
+
+---
+
+### 7. Documentation
+
+The following must always be maintained:
+
+- README.md
+- CHANGELOG.md
+- Inline YARD documentation
+- Usage examples
+
+Documentation must reflect real behavior.
+
+---
+
+### 8. CI Discipline
+
+CI must:
+
+- Run specs
+- Lint with RuboCop
+- Fail on warnings
+- Test multiple Ruby versions
+
+No PR should be merged if CI fails.
+
+---
+
+## Contributor Workflow
+
+When implementing changes:
+
+1. Write or update specs first.
+2. Implement feature.
+3. Run `bundle exec rspec`.
+4. Run `bundle exec rubocop`.
+5. Update documentation.
+6. Update CHANGELOG.md.
+
+---
+
+## Non-Negotiable Rule
+
+Never remove specs without replacing them.
+Never reduce coverage.
+Never ship untested code.

data/CODE_OF_CONDUCT.md

@@ -0,0 +1,10 @@
+# Code of Conduct
+
+"verify_it" follows [The Ruby Community Conduct Guideline](https://www.ruby-lang.org/en/conduct) in all "collaborative space", which is defined as community communications channels (such as mailing lists, submitted patches, commit comments, etc.):
+
+* Participants will be tolerant of opposing views.
+* Participants must ensure that their language and actions are free of personal attacks and disparaging personal remarks.
+* When interpreting the words and actions of others, participants should always assume good intentions.
+* Behaviour which can be reasonably considered harassment will not be tolerated.
+
+If you have any concerns about behaviour within this project, please contact us at ["iguanadejere4@googlemail.com"](mailto:"iguanadejere4@googlemail.com").

data/LICENSE.txt

@@ -0,0 +1,21 @@
+The MIT License (MIT)
+
+Copyright (c) 2026 Jeremias Ramirez
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.