Serve still-valid access tokens while a token refresh is in flight

.agents/skills/classloading-and-runtime-dev/SKILL.md

@@ -19,8 +19,10 @@ description: >
 - **Runtime code MUST NOT reference deployment classes.** Violations cause
   `ClassNotFoundException` at runtime.
 - **Deployment code CAN reference runtime classes.**
-- **Recorders bridge the gap.** A `@Recorder` lives in the runtime module but
-  is invoked from deployment build steps.
+- **Services bridge the gap.** Service lambdas are defined in deployment build
+  steps but execute at runtime. The lambda body can only reference runtime
+  classes; attempting to reference deployment classes will cause
+  `ClassNotFoundException` at runtime.
 
 ## Runtime-Dev Modules
 
@@ -74,7 +76,7 @@ Forgetting `conditionalDevDependencies` is particularly confusing because:
 ## Common Mistakes
 
 - Importing a deployment class in runtime code
-- Using a build-time-only library in a recorder
+- Using a build-time-only library in a service lambda
 - Accessing runtime config during augmentation (build time)
 - Putting user-facing API classes in deployment instead of runtime
 - Forgetting `conditionalDevDependencies` for `runtime-dev` modules

.agents/skills/coding-style/SKILL.md

@@ -21,7 +21,7 @@ description: >
 
 - Prefer package-private (default) visibility for internal implementation classes
 - Use `public` for user-facing API and for classes/methods that need to be accessed
-  across packages (e.g., processors, recorders, build items). Prefer package-private
+  across packages (e.g., processors, build items). Prefer package-private
   for purely internal implementation details
 - Use `protected` when designing for extension/subclassing
 - Internal classes should go in `.internal` or `.impl` sub-packages
@@ -30,7 +30,6 @@ description: >
 ## Naming
 
 - Deployment processors: `<Feature>Processor.java`
-- Recorders: `<Feature>Recorder.java`
 - Build items: `<Description>BuildItem.java`
 - Config interfaces: `<Feature>Config.java` or `<Feature>BuildTimeConfig.java` / `<Feature>RuntimeConfig.java`
 - Artifact IDs: `quarkus-<name>` (runtime), `quarkus-<name>-deployment` (deployment)