Revert back to Async::Service::Generic.

Author: samuel-williams-shopify

context/best-practices.md

@@ -201,7 +201,7 @@ end
 
 ### Use `Managed::Service` as Base Class
 
-Prefer `Async::Service::ManagedService` over `GenericService` for most services:
+Prefer `Async::Service::ManagedService` over `Generic` for most services:
 
 ```ruby
 class WebService < Async::Service::ManagedService

context/getting-started.md

@@ -14,13 +14,13 @@ $ bundle add async-service
 
 `async-service` has several core concepts:
 
-- A {ruby Async::Service::GenericService} which represents the base class for implementing services.
+- A {ruby Async::Service::Generic} which represents the base class for implementing services.
 - A {ruby Async::Service::Configuration} which manages service configurations and environments.
 - A {ruby Async::Service::Controller} which handles starting, stopping, and managing services.
 
 ## Usage
 
-Services are long-running processes that can be managed as a group. Each service extends `Async::Service::GenericService` and implements a `setup` method that defines how the service runs.
+Services are long-running processes that can be managed as a group. Each service extends `Async::Service::Generic` and implements a `setup` method that defines how the service runs.
 
 ### Basic Service
 
@@ -31,7 +31,7 @@ Create a simple service that runs continuously:
 
 require "async/service"
 
-class HelloService < Async::Service::GenericService
+class HelloService < Async::Service::Generic
 	def setup(container)
 		super
 
@@ -73,7 +73,7 @@ end
 In your service implementation, you can access these values through the environment and evaluator:
 
 ```ruby
-class WebServerService < Async::Service::GenericService
+class WebServerService < Async::Service::Generic
 	def setup(container)
 		super
 
@@ -103,7 +103,7 @@ You can define multiple services in a single configuration file:
 
 require "async/service"
 
-class WebService < Async::Service::GenericService
+class WebService < Async::Service::Generic
 	def setup(container)
 		super
 
@@ -115,7 +115,7 @@ class WebService < Async::Service::GenericService
 	end
 end
 
-class WorkerService < Async::Service::GenericService
+class WorkerService < Async::Service::Generic
 	def setup(container)
 		super
 

context/service-architecture.md

@@ -82,14 +82,14 @@ end
 
 ## Service
 
-The {ruby Async::Service::GenericService} represents the service implementation layer. It handles the actual business logic of your services, provides access to configuration through environment evaluators, and manages the service lifecycle including startup, execution, and shutdown phases.
+The {ruby Async::Service::Generic} represents the service implementation layer. It handles the actual business logic of your services, provides access to configuration through environment evaluators, and manages the service lifecycle including startup, execution, and shutdown phases.
 
 ### Business Logic
 
 Services contain the actual implementation of what your service does:
 
 ```ruby
-class WebService < Async::Service::GenericService
+class WebService < Async::Service::Generic
 	def setup(container)
 		super
 
@@ -148,7 +148,7 @@ By evaluating the log_path in the child process, you ensure that each instance h
 Services define their startup, running, and shutdown behavior:
 
 ```ruby
-class MyService < Async::Service::GenericService
+class MyService < Async::Service::Generic
 	def start
 		super
 		# Service-specific startup logic including pre-loading libraries and binding to network interfaces before forking.
@@ -264,7 +264,7 @@ end
 
 For services using `Async::Service::ManagedService`, health checking is handled automatically. The service sends `status!` messages during startup to prevent premature health check timeouts, then transitions to sending `ready!` messages once the service is actually ready.
 
-For services extending `GenericService`, you can set up health checking manually:
+For services extending `Generic`, you can set up health checking manually:
 
 ```ruby
 def setup(container)
@@ -334,7 +334,7 @@ end
 
 ```ruby
 # Services are defined using environments:
-class WebService < Async::Service::GenericService
+class WebService < Async::Service::Generic
 	def setup(container)
 		super
 
@@ -493,7 +493,7 @@ end
 Build service hierarchies:
 
 ```ruby
-class BaseWebService < Async::Service::GenericService
+class BaseWebService < Async::Service::Generic
 	def setup(container)
 		super
 		# Common web service setup

examples/hello/hello.rb

@@ -4,7 +4,7 @@
 # Released under the MIT License.
 # Copyright, 2024-2025, by Samuel Williams.
 
-class SleepService < Async::Service::GenericService
+class SleepService < Async::Service::Generic
 	def setup(container)
 		super
 

examples/hello/readme.md

@@ -27,7 +27,7 @@ Press `Ctrl+C` to stop the service.
 The example defines a simple service class:
 
 ~~~ ruby
-class SleepService < Async::Service::GenericService
+class SleepService < Async::Service::Generic
 	def setup(container)
 		super
 
@@ -45,7 +45,7 @@ end
 
 Key points:
 
-- **Inherits from `Async::Service::GenericService`**: Provides the basic service interface
+- **Inherits from `Async::Service::Generic`**: Provides the basic service interface
 - **Implements `setup(container)`**: Defines how the service runs
 - **Uses `container.run`**: Creates one instance with automatic restart
 - **Calls `instance.ready!`**: Signals the service is ready

examples/ipc/client.rb

@@ -16,7 +16,7 @@
 	ipc_socket_path File.expand_path("service.ipc", Dir.pwd)
 end
 
-class IPCClient < Async::Service::GenericService
+class IPCClient < Async::Service::Generic
 	def setup(container)
 		super
 

examples/ipc/server.rb

@@ -15,7 +15,7 @@
 	ipc_socket_path File.expand_path("service.ipc", Dir.pwd)
 end
 
-class IPCServer < Async::Service::GenericService
+class IPCServer < Async::Service::Generic
 	def setup(container)
 		super
 

fixtures/async/service/sleep_service.rb

@@ -3,11 +3,11 @@
 # Released under the MIT License.
 # Copyright, 2025, by Samuel Williams.
 
-require "async/service/generic_service"
+require "async/service/generic"
 
 module Async
 	module Service
-		class SleepService < Async::Service::GenericService
+		class SleepService < Async::Service::Generic
 			def setup(container)
 				super
 

guides/best-practices/readme.md

@@ -201,7 +201,7 @@ end
 
 ### Use `Managed::Service` as Base Class
 
-Prefer `Async::Service::ManagedService` over `GenericService` for most services:
+Prefer `Async::Service::ManagedService` over `Generic` for most services:
 
 ```ruby
 class WebService < Async::Service::ManagedService

guides/getting-started/index.md

@@ -37,7 +37,7 @@ Create a file called `hello_service.rb`:
 
 require 'async/service'
 
-class HelloService < Async::Service::GenericService
+class HelloService < Async::Service::Generic
 	def setup(container)
 		super
 
@@ -82,7 +82,7 @@ Let's break down the example:
 ### Service Class
 
 ~~~ ruby
-class HelloService < Async::Service::GenericService
+class HelloService < Async::Service::Generic
 	def setup(container)
 		super
 
@@ -95,7 +95,7 @@ class HelloService < Async::Service::GenericService
 end
 ~~~
 
-- **Inherit from `Async::Service::GenericService`**: This provides the basic service interface
+- **Inherit from `Async::Service::Generic`**: This provides the basic service interface
 - **Implement `setup(container)`**: This method configures how your service runs
 - **Call `super`**: Always call the parent's setup method
 - **Use `container.run`**: Define how many instances to run and restart behavior
@@ -146,7 +146,7 @@ You can define multiple services in a single configuration file:
 
 require 'async/service'
 
-class WebService < Async::Service::GenericService
+class WebService < Async::Service::Generic
 	def setup(container)
 		super
 
@@ -160,7 +160,7 @@ class WebService < Async::Service::GenericService
 	end
 end
 
-class WorkerService < Async::Service::GenericService
+class WorkerService < Async::Service::Generic
 	def setup(container)
 		super
 
@@ -224,7 +224,7 @@ Async::Service::Controller.run(configuration)
 Services automatically handle errors and provide logging:
 
 ~~~ ruby
-class RobustService < Async::Service::GenericService
+class RobustService < Async::Service::Generic
 	def setup(container)
 		super
 
@@ -269,7 +269,7 @@ Check out the [examples](../../examples/) directory for more complex service imp
 require 'async/http/server'
 require 'async/http/endpoint'
 
-class HTTPService < Async::Service::GenericService
+class HTTPService < Async::Service::Generic
 	def setup(container)
 		super
 
@@ -290,7 +290,7 @@ end
 ### Periodic Task Service
 
 ~~~ ruby
-class PeriodicService < Async::Service::GenericService
+class PeriodicService < Async::Service::Generic
 	def setup(container)
 		super