strict-module 0.5.0__tar.gz

strict_module-0.5.0/.github/workflows/ci.yml

@@ -0,0 +1,25 @@
+name: CI
+
+on:
+  pull_request:
+  push:
+    branches: [main]
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        python-version: ["3.11", "3.12"]
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: ${{ matrix.python-version }}
+      - name: Install
+        run: pip install -e .[dev]
+      - name: Test
+        run: pytest tests/ -v
+      - name: Dogfood lint
+        run: strict-module strict_module/ --format github
+        continue-on-error: true

strict_module-0.5.0/.github/workflows/no-ai-attribution.yml

@@ -0,0 +1,73 @@
+name: Attribution Gate
+
+# Server-side enforcement: rejects pushes/PRs whose commit messages contain
+# Claude/Anthropic attribution. Catches GitHub squash-merge propagation that
+# bypasses local commit-msg, pre-push, and PreToolUse hooks.
+#
+# Per-repo copy of the canonical attribution gate.
+
+on:
+  push:
+  pull_request:
+
+permissions:
+  contents: read
+  pull-requests: read
+
+jobs:
+  scan:
+    name: Scan commit messages for attribution
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout (full history)
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+
+      - name: Determine commit range
+        id: range
+        env:
+          EVENT_NAME: ${{ github.event_name }}
+          PR_BASE: ${{ github.event.pull_request.base.sha }}
+          PR_HEAD: ${{ github.event.pull_request.head.sha }}
+          PUSH_BEFORE: ${{ github.event.before }}
+          PUSH_AFTER: ${{ github.event.after }}
+        run: |
+          set -euo pipefail
+          if [ "$EVENT_NAME" = "pull_request" ]; then
+            BASE="$PR_BASE"
+            HEAD="$PR_HEAD"
+          else
+            BASE="$PUSH_BEFORE"
+            HEAD="$PUSH_AFTER"
+            if [ "$BASE" = "0000000000000000000000000000000000000000" ] || [ -z "$BASE" ]; then
+              git fetch origin main:refs/remotes/origin/main 2>/dev/null || true
+              BASE=$(git merge-base origin/main "$HEAD" 2>/dev/null || git rev-list --max-parents=0 "$HEAD" | tail -1)
+            fi
+          fi
+          echo "base=$BASE" >> "$GITHUB_OUTPUT"
+          echo "head=$HEAD" >> "$GITHUB_OUTPUT"
+
+      - name: Scan for Claude/Anthropic attribution
+        env:
+          BASE: ${{ steps.range.outputs.base }}
+          HEAD: ${{ steps.range.outputs.head }}
+          PATTERN: 'co-authored-by.*(claude|anthropic)|generated with claude|@claude|noreply@anthropic|🤖'
+        run: |
+          set -uo pipefail
+          OFFENDING=""
+          for sha in $(git rev-list "$BASE..$HEAD"); do
+            MSG=$(git log -1 --pretty=format:"%B" "$sha")
+            if echo "$MSG" | grep -qiE "$PATTERN"; then
+              AUTHOR=$(git log -1 --pretty=format:"%an" "$sha")
+              SUBJECT=$(git log -1 --pretty=format:"%s" "$sha")
+              OFFENDING="${OFFENDING}  ${sha:0:8} | author=${AUTHOR} | ${SUBJECT}"$'\n'
+            fi
+          done
+          if [ -n "$OFFENDING" ]; then
+            echo "::error::Claude/Anthropic attribution detected in commit messages"
+            echo "Offending commits in range $BASE..$HEAD:"
+            printf '%s' "$OFFENDING"
+            exit 1
+          fi
+          echo "OK: no attribution detected in $BASE..$HEAD"

strict_module-0.5.0/.github/workflows/publish.yml

@@ -0,0 +1,35 @@
+name: Publish to PyPI
+
+on:
+  release:
+    types: [published]
+
+jobs:
+  publish:
+    name: Build + publish
+    runs-on: ubuntu-latest
+    environment: pypi  # second-layer GitHub deployment-environment gate
+    permissions:
+      id-token: write  # OIDC trusted publisher
+      contents: read
+
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+
+      - name: Set up Python
+        uses: actions/setup-python@v5
+        with:
+          python-version: '3.12'
+
+      - name: Install build deps
+        run: python -m pip install --upgrade build
+
+      - name: Build sdist + wheel
+        run: python -m build
+
+      - name: Verify artifacts
+        run: python -m pip install --upgrade twine && python -m twine check dist/*
+
+      - name: Publish to PyPI
+        uses: pypa/gh-action-pypi-publish@release/v1

strict_module-0.5.0/.github/workflows/ruff.yml

@@ -0,0 +1,29 @@
+name: Ruff
+
+# Ruff lint + format check. Pinned to 0.15.14 to match local version.
+# Format drift was previously undetected; this gate prevents future drift.
+
+on:
+  pull_request:
+  push:
+    branches: [main]
+
+concurrency:
+  group: ${{ github.workflow }}-${{ github.ref }}
+  cancel-in-progress: true
+
+permissions:
+  contents: read
+
+jobs:
+  ruff:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: astral-sh/setup-uv@v4
+        with:
+          enable-cache: true
+      - name: Ruff lint
+        run: uvx ruff@0.15.14 check strict_module/
+      - name: Ruff format check
+        run: uvx ruff@0.15.14 format --check strict_module/

strict_module-0.5.0/.github/workflows/strict-module.yml

@@ -0,0 +1,30 @@
+name: strict-module
+
+# DTO-discipline lint (frozen+slots, facade-ban, R001-R006). Per-repo copy of
+# the canonical gate; runs on the strict-module package itself (self-lint).
+# Lint step: source directory only.
+
+on:
+  pull_request:
+  push:
+    branches: [main]
+
+concurrency:
+  group: ${{ github.workflow }}-${{ github.ref }}
+  cancel-in-progress: true
+
+permissions:
+  contents: read
+
+jobs:
+  lint:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: astral-sh/setup-uv@v4
+        with:
+          enable-cache: true
+      - name: Install Python 3.12
+        run: uv python install 3.12
+      - name: Run strict-module
+        run: uv run --python 3.12 python -m strict_module.cli strict_module/ --format github

strict_module-0.5.0/.gitignore

@@ -0,0 +1,44 @@
+__pycache__/
+*.py[cod]
+*$py.class
+*.so
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+pip-wheel-metadata/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+.pytest_cache/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py,cover
+.hypothesis/
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+.idea/
+.vscode/
+*.swp
+*.swo
+*~
+.DS_Store

strict_module-0.5.0/CHANGELOG.md

@@ -0,0 +1,160 @@
+# Changelog
+
+All notable changes to this project will be documented in this file.
+
+## [Unreleased]
+
+### Added
+
+### Changed
+
+### Fixed
+
+## [0.5.0] - 2026-07-06
+
+### Changed
+
+- **Package renamed from `dto-strict` to `strict-module`** - Renamed to follow category-first naming conventions (strict- prefix). GitHub repository renamed to `github.com/jekhator/strict-module`. PyPI package name updated to `strict-module`.
+- **Flattened package layout** - Source code moved from `src/dto_strict/` to `strict_module/` at repository root, adopting the suite's standard flat-namespace layout.
+- **Version single-sourced in `strict_module/config/_version.py`** - Eliminates version drift between package metadata and source. Hatch now dynamically reads version from this file.
+
+### Added
+
+- **Backward-compatible config fallbacks** - Configuration loading now checks `[tool.strict-module]` first, then falls back to `[tool.dto-strict]` for compatibility with existing codebases. Both are supported; new code should use `[tool.strict-module]`.
+- **Backward-compatible baseline fallbacks** - Baseline file loading checks `.strict-module-baseline.json` first, then falls back to `.dto-strict-baseline.json`.
+- **Entry point alias** - The `dto-strict` CLI command remains available as a backward-compatibility alias, pointing to the same implementation as the new `strict-module` command.
+- **Comprehensive compatibility tests** - New test suite (`test_compat_fallback.py`) covers config and baseline file fallback scenarios.
+
+### Deprecated
+
+- `[tool.dto-strict]` configuration section - use `[tool.strict-module]` instead. Old section still works but will be removed in v1.0.
+- `dto-strict` CLI command name - use `strict-module` instead. Old name still works but will be removed in v1.0.
+- `.dto-strict-baseline.json` filename - use `.strict-module-baseline.json` instead. Old filename still works but will be removed in v1.0.
+
+## [0.4.1] - 2026-06-11
+
+### Fixed
+
+- **R002 no longer false-positives on dict literals returned from to_* serializer methods** - Dict literals returned from methods whose name starts with `to_` in a `@dataclass`-decorated class are now correctly exempted. The returned dict is the dataclass's serialized output, not an unconverted business shape. Non-dataclass classes and non-`to_*` methods remain flagged as before. Example: `class UserDTO` with `def to_dict(self) -> dict: return {"id": self.id, "name": self.name, "email": self.email}` now passes (no R002 violation).
+
+- **`dto-strict loc-cap` now exempts test files from the line-of-code cap** - Test files are automatically excluded from LOC enforcement, mirroring the v0.4.0 lint exemption set. A file is a test file if its basename is `conftest.py`, matches `test_*.py`, or is under a `tests/` directory. This prevents test fixtures and test helpers from inflating LOC metrics. Baseline files remain unaffected; improvements in test files are still reflected in ratchet calculations.
+
+### Changed
+
+- `is_test_file()` utility now checks for `/tests/` directory path segments in addition to basename patterns. This enables `loc-cap` to properly exempt test files found anywhere under a `tests/` directory structure.
+
+## [0.4.0] - 2026-06-07
+
+### Added
+
+- **Test file exemption from DTO rules (R001, R004, R006)** - Service-layer rules (R001, R004, R006) now automatically exempt test files from linting. A file is considered a test file if its basename is `conftest.py`, matches `test_*.py`, or contains a `/tests/` path segment. This prevents false positives in test fixtures and test helpers that may use `Dict[str, Any]`, module-level functions, or `typing.Any` for legitimate testing purposes.
+
+- **R007 - Pytest fixtures must be in conftest.py** - New rule that flags `@pytest.fixture` decorators defined in test files other than `conftest.py`. Fixtures are test infrastructure and belong in the module-level fixtures file (conftest.py), not scattered across test modules. Rule applies only to test files (basename `conftest.py`, `test_*.py`, or under `/tests/`).
+
+- **R008 - Bare module-level test functions** - New rule that flags test functions (matching `def test_*`) defined at module level in test files. Test functions must be organized into `Test<Concern>` classes for clarity and pytest discovery. Rule applies only to test files.
+
+### Changed
+
+- `is_service_path()` and `is_dto_path()` now check `is_test_file()` before pattern matching, ensuring test files never match service or DTO paths regardless of naming.
+
+### Improved
+
+- Configuration section for pytest discipline rules now documented in README (new "Pytest Discipline" section).
+
+## [0.3.0] - 2026-06-04
+
+### Added
+
+- **`dto-strict loc-cap` subcommand - per-file LOC-cap ratchet enforcer** - New CLI subcommand for enforcing line-of-code limits on Python files with configurable hard/soft caps and baseline-driven ratcheting. Ported from the per-repo `check_loc_cap.py` pattern into dto-strict's unified command surface.
+  - **Hard cap** (default: 694 LOC) - fails the check if any file exceeds this limit (NEW offenders fail immediately; baselined files that grew also fail).
+  - **Soft target** (default: 500 LOC) - warnings for files exceeding soft target but under hard cap (suggest decomposition).
+  - **Ratchet baseline** (via `--baseline .loc-cap-baseline.txt` or config `[tool.dto-strict.loc-cap].baseline_file`) - baselined files cannot exceed their recorded LOC; improvements are allowed.
+  - **Generate baseline** (via `--generate-baseline`) - outputs baseline in `path:loc` format (sorted by LOC descending) for capture into version control.
+  - CLI flags: `--hard-cap`, `--soft-target`, `--baseline`, `--generate-baseline`, `--config` (pyproject.toml path).
+  - Pyproject config section: `[tool.dto-strict.loc-cap]` with keys `hard_cap`, `soft_target`, `baseline_file` (CLI flags take precedence).
+  - Exclusion patterns: `migrations`, `management/commands` (hardcoded, Django-scoped).
+  - Exit code: 0 for pass (soft warnings allowed), 1 for hard violations.
+
+### Changed
+
+- **CLI now dispatches on subcommand**: `sys.argv[1] == "loc-cap"` routes to `handle_loc_cap()` before standard argparse. Bare `dto-strict <path>` DTO-discipline lint is unchanged (backcompat preserved).
+- **Added tomli backport dependency** for Python 3.10 (tomllib native in 3.11+), enabling pyproject.toml parsing for loc-cap config in both Python versions.
+
+### Improved
+
+- Configuration now loads `[tool.dto-strict.loc-cap]` section from pyproject.toml alongside existing `[tool.dto-strict]` linter options.
+## [0.2.2] - 2026-05-22
+
+### Fixed
+
+- **R002 no longer false-positives on annotated module-level / class-level constants** - Typed static data declarations like `DISPLAY_LABELS: dict[str, str] = {...}` are now correctly skipped. The explicit type annotation signals intent ("this is typed static data") distinct from R002's actual target ("inline dict literal as business shape in service code"). Now R002 skips:
+  - `ast.AnnAssign` at module scope (module-level typed constants)
+  - `ast.AnnAssign` inside class body (class-level typed constants)
+  
+  Still flags:
+  - `ast.Assign` without annotation at module scope (ambiguous intent)
+  - Inline dict literals inside function bodies (original intent)
+  Regression tests added in `tests/test_r002_annotated_constants.py`.
+
+- **Noqa suppression now correctly handles em-dashes and multi-line dicts** - v0.2.1's `has_noqa_comment` was broken for explanations using em-dashes (-) instead of hyphens (-). The function only stripped trailing hyphens (`-`), causing specs like `"dto-strict-R002 - explanation"` to remain unmatched. Now handles all dash variants: `-`, `–`, `-`. Additionally clarified that multi-line dict noqa comments must be on the opening brace line (ast node's `lineno`). Test suite `tests/test_noqa_r002.py` covers 7 scenarios: trailing-hyphen, trailing-emdash, opening-brace, no-noqa, wrong-rule, bare-noqa, and before-line (should NOT suppress).
+
+
+## [0.2.1] - 2026-05-21
+
+### Fixed
+
+- **`has_noqa_comment` is now implemented** - Previously a stub returning False, suppression via `# noqa: dto-strict-RXXX` comments was silently broken. Now properly parses and recognizes:
+  - `# noqa` (suppresses all rules)
+  - `# noqa: dto-strict` (suppresses all dto-strict rules)
+  - `# noqa: dto-strict-R001` (suppresses specific rule)
+  - `# noqa: dto-strict-R001, dto-strict-R002` (suppresses multiple rules)
+  All checkers now honor suppression comments.
+
+### Documentation
+
+- **Clarified R003 canonical-pivot wording** - Description now explicitly states "Flag `repr=False` in dataclasses (v0.2 canonical: plain `@dataclass(frozen=True, slots=True)` without `repr=False`)", making the v0.2 shift from v0.1 explicit.
+- **Added "PHI / Sensitive Data Handling (Pattern 1)" section** - Explains the intentional move from blanket `repr=False` to explicit `__repr__` overrides on sensitive DTOs. Includes healthcare/HIPAA context and example code for masking PII fields.
+- **Added "Suppressing Violations" section** - Documents the now-functional `# noqa: dto-strict-RXXX` syntax with practical examples.
+- **Mentioned healthcare/HIPAA use case in "Why dto-strict?"** - Added context on why DTO discipline is critical in regulated healthcare systems managing patient records and compliance documents.
+
+## [0.2.0] - 2026-05-13
+
+### Added
+
+- **Issue #1 - R004 auto-detect class-method-wrapping pattern**: R004 now auto-detects when module-level functions delegate to class methods, reducing false positives. Functions that exclusively wrap class methods (e.g., `return _service.method(...)` or `return ClassName.method(...)`) no longer require exception tags. Exception tags still work as override.
+
+- **Issue #2 - R002 configurable min_dict_keys threshold**: R002 now supports a configurable `min_dict_keys` setting (default: 3). This allows teams to enforce stricter or looser inline dict literal thresholds. Configure in `pyproject.toml`:
+  ```toml
+  [tool.dto-strict]
+  min_dict_keys = 2  # Flag dicts with 2+ keys instead of 3+
+  ```
+
+- **Issue #3 - R003 strict/relaxed modes for frozen+slots+repr=False trio**: R003 now supports `r003_strict_repr` mode (default: true in canonical mode).
+  - **Strict mode** (default): `repr=False` is flagged as anti-canonical. Canonical pattern is `@dataclass(frozen=True, slots=True)` WITHOUT `repr=False`.
+  - **Relaxed mode**: Only checks for `frozen=True, slots=True`; ignores `repr=False` (useful for gradual migrations). Configure:
+    ```toml
+    [tool.dto-strict]
+    r003_strict_repr = false  # Enable relaxed mode
+    ```
+
+- **Issue #4 - Baseline ratchet-from-baseline mode**: New `--generate-baseline` and `--baseline` CLI flags enable "technical debt ratcheting":
+  - `dto-strict apps/ --generate-baseline > .dto-strict-baseline.json` - Capture current violations as accepted debt.
+  - `dto-strict apps/ --baseline .dto-strict-baseline.json` - Subsequent runs accept baseline violations; new violations trigger failure (exit 1).
+  - Baseline entries are hashed by file + line + rule_id for stability against message wording changes.
+
+### Changed
+
+- R003 canonical mode now defaults to `r003_strict_repr=true`, treating `repr=False` as anti-canonical and flagging it for removal.
+- CLI argument `path` now optional when using `--generate-baseline` (path is required for normal linting).
+
+### Improved
+
+- Configuration loading now supports `min_dict_keys` and `r003_strict_repr` options in `[tool.dto-strict]` section of `pyproject.toml`.
+
+### Bug Fixes
+
+- None in v0.2.0.
+
+## [0.1.0] - Earlier Versions
+
+See git history for prior releases.

strict_module-0.5.0/CODE_OF_CONDUCT.md

@@ -0,0 +1,34 @@
+# Code of Conduct
+
+## Our Commitment
+
+We are committed to providing a welcoming and inclusive environment for all contributors. We pledge to make participation in this community a harassment-free experience regardless of age, body size, disability, ethnicity, gender identity, experience level, nationality, personal appearance, race, religion, sexual identity, or sexual orientation.
+
+## Our Standards
+
+Examples of behavior that contribute to creating a positive environment include:
+
+- Using welcoming and inclusive language
+- Being respectful of differing opinions, viewpoints, and experiences
+- Gracefully accepting constructive criticism
+- Focusing on what is best for the community
+- Showing empathy towards other community members
+
+Examples of unacceptable behavior include:
+
+- Harassment or discrimination of any kind
+- Offensive comments related to protected characteristics
+- Trolling, insulting comments, or personal attacks
+- Public or private harassment
+- Publishing others' private information without consent
+- Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the maintainers. All complaints will be reviewed and investigated.
+
+The project maintainers are obligated to maintain confidentiality with regard to the reporter of an incident.
+
+## Attribution
+
+This Code of Conduct is adapted from the Contributor Covenant, available at [https://www.contributor-covenant.org](https://www.contributor-covenant.org).

strict_module-0.5.0/CONTRIBUTING.md

@@ -0,0 +1,30 @@
+# Contributing
+
+Issues and pull requests welcome. Please include fixtures (good and bad examples) for new rules.
+
+When submitting a fix or feature:
+
+1. Ensure all tests pass: `python3.12 -m pytest tests/ -q`
+2. Format code: `ruff format src/ tests/`
+3. Lint code: `ruff check src/ tests/` and `dto-strict src/`
+4. Update CHANGELOG.md with your changes under an [Unreleased] section
+
+## Development Setup
+
+```bash
+git clone https://github.com/jekhator/dto-strict.git
+cd dto-strict
+python3.12 -m venv .venv
+source .venv/bin/activate
+pip install -e ".[dev]"
+```
+
+## Running Tests
+
+```bash
+python3.12 -m pytest tests/ -v
+```
+
+## License
+
+All contributions are licensed under the Apache License 2.0. See LICENSE for details.

strict_module-0.5.0/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation of a Source form, including but not limited to
+      compiled object code, generated documentation, conversions to other
+      media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and its Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give to any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if any Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file type. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 James Ekhator
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.