chore: rename Service Quality to Rewards Eligibility (#50)

* chore: rename service quality to rewards eligibility

* chore: complete file rename and fix unit tests

- Rename src/models/service_quality_oracle.py to rewards_eligibility_oracle.py
- Update technical-design.md to reference new module name
- Apply code formatting via ruff
- All 199 tests passing with 89% coverage

Author: MoonBoi9001

.github/CODEOWNERS

@@ -1,4 +1,4 @@
-# CODEOWNERS file for service-quality-oracle
+# CODEOWNERS file for rewards-eligibility-oracle
 # This file defines who will be requested for review when someone opens a pull request
 
 # Default owners for everything in the repo

.github/workflows/cd.yml

@@ -181,7 +181,7 @@ jobs:
             echo "Or use docker-compose:"
             echo '```yaml'
             echo "services:"
-            echo "  service-quality-oracle:"
+            echo "  rewards-eligibility-oracle:"
             echo "    image: ${{ env.REGISTRY }}/${{ env.IMAGE_NAME }}:${{ needs.version.outputs.version }}"
             echo '```'
           } > release_notes.md

.github/workflows/ci.yml

@@ -132,8 +132,8 @@ jobs:
 
       - name: Build and test Docker image
         run: |
-          docker build -t service-quality-oracle:test .
-          docker create --name test-container service-quality-oracle:test
+          docker build -t rewards-eligibility-oracle:test .
+          docker create --name test-container rewards-eligibility-oracle:test
           docker rm test-container
 
       - name: Validate Docker Compose

.github/workflows/release-please.yml

@@ -16,4 +16,4 @@ jobs:
       - uses: google-github-actions/release-please-action@v4
         with:
           release-type: python
-          package-name: service-quality-oracle
+          package-name: rewards-eligibility-oracle

.github/workflows/security.yml

@@ -105,10 +105,10 @@ jobs:
         uses: actions/checkout@v5
 
       - name: Build and scan image
-        run: docker build -t service-quality-oracle:security-scan .
+        run: docker build -t rewards-eligibility-oracle:security-scan .
 
       - name: Run vulnerability scan
         uses: aquasecurity/trivy-action@master
         with:
-          image-ref: 'service-quality-oracle:security-scan'
+          image-ref: 'rewards-eligibility-oracle:security-scan'
           format: 'table' 

.release-please-config.json

@@ -2,7 +2,7 @@
   "packages": {
     ".": {
       "release-type": "python",
-      "package-name": "service-quality-oracle",
+      "package-name": "rewards-eligibility-oracle",
       "changelog-path": "CHANGELOG.md",
       "bump-minor-pre-major": true,
       "bump-patch-for-minor-pre-major": true,

CHANGELOG.md

@@ -1,6 +1,6 @@
 # Changelog
 
-All notable changes to the Service Quality Oracle project will be documented in this file.
+All notable changes to the Rewards Eligibility Oracle project will be documented in this file.
 
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
@@ -43,7 +43,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 - Improved Google Cloud credential handling with better error messages (#42)
 - Renamed contract from IssuanceEligibilityOracle to RewardsEligibilityOracle (#39)
-- Updated contract ABI to match deployed ServiceQualityOracle (#24)
+- Updated contract ABI to match deployed RewardsEligibilityOracle (#24)
 - Updated to production Docker image configuration (#16, #25)
 - Python upgraded from 3.11-slim to 3.13.7-slim (#30)
 

CLAUDE.md

@@ -4,7 +4,7 @@ This file provides guidance to Claude Code (claude.ai/code) when working with co
 
 ## Project Overview
 
-Service Quality Oracle is a Python-based Docker containerized service that:
+Rewards Eligibility Oracle is a Python-based Docker containerized service that:
 
 - Fetches indexer performance data from Google BigQuery daily at 10:00 UTC
 - Processes data to determine indexer issuance rewards eligibility based on threshold algorithms
@@ -79,7 +79,7 @@ The system follows a clear data pipeline with daily scheduled execution:
 
 1. **Scheduler (src/models/scheduler.py)**: Main entry point that runs daily at configured time, manages catch-up runs for missed days, and handles the application lifecycle.
 
-2. **Orchestrator (src/models/service_quality_oracle.py)**: Coordinates the end-to-end oracle run process by managing the flow between components.
+2. **Orchestrator (src/models/rewards_eligibility_oracle.py)**: Coordinates the end-to-end oracle run process by managing the flow between components.
 
 3. **BigQuery Provider (src/models/bigquery_provider.py)**: Executes SQL queries against BigQuery to fetch indexer performance metrics.
 

Dockerfile

@@ -1,4 +1,4 @@
-# Dockerfile to create a clean, lightweight Docker Image for the Service Quality Oracle
+# Dockerfile to create a clean, lightweight Docker Image for the Rewards Eligibility Oracle
 
 # Use Python 3.13.7 slim as the base image for a lightweight container
 FROM python:3.13.7-slim
@@ -7,7 +7,7 @@ FROM python:3.13.7-slim
 ARG VERSION=dev
 
 # Add metadata labels
-LABEL description="Service Quality Oracle" \
+LABEL description="Rewards Eligibility Oracle" \
       version="${VERSION}"
 
 # Set working directory

ELIGIBILITY_CRITERIA.md

@@ -6,7 +6,7 @@ This document defines the requirements an Indexer must meet to be eligible for i
 
 ## Upcoming Eligibility Criteria
 
-**We will announce changes to the eligibility criteria in the table below.** Once the change goes live, it will be reflected in the [Active Eligibility Criteria](https://github.com/graphprotocol/service-quality-oracle/blob/main/ELIGIBILITY_CRITERIA.md#active-eligibility-criteria) section of this document.
+**We will announce changes to the eligibility criteria in the table below.** Once the change goes live, it will be reflected in the [Active Eligibility Criteria](https://github.com/graphprotocol/rewards-eligibility-oracle/blob/main/ELIGIBILITY_CRITERIA.md#active-eligibility-criteria) section of this document.
 
 | Upcoming Requirement | Justification | Date Requirement Will Be Updated/Introduced (YYYY-MM-DD) |
 |----------------------|---------------|----------------------------------------------------------|