chore(awareness-service): cap webhook delivery at 3 attempts

Lower the default AWARENESS_MAX_ATTEMPTS from 8 to 3.

Author: coodos

.env.example

@@ -145,7 +145,7 @@ AAAS_ADMIN_ENAMES=""
 # Secret used to sign AaaS portal session JWTs
 AAAS_JWT_SECRET="replace-with-a-strong-secret"
 # Webhook delivery tuning
-AWARENESS_MAX_ATTEMPTS=8
+AWARENESS_MAX_ATTEMPTS=3
 AWARENESS_DELIVERY_POLL_MS=2000
 # The one-time Neo4j backfill reuses the standard NEO4J_URI / NEO4J_USER /
 # NEO4J_PASSWORD vars at the top of this file - it reads evault-core's graph

docs/docs/Services/Awareness-as-a-Service.md

@@ -160,7 +160,7 @@ AaaS is designed to be dropped in with **zero receiver-side changes**:
 | `AWARENESS_SERVICE_URL` | (evault-core) where to POST packets |
 | `AAAS_ADMIN_ENAMES` | Comma-separated admin eNames |
 | `AAAS_JWT_SECRET` | Signs portal session JWTs |
-| `AWARENESS_MAX_ATTEMPTS` | Delivery attempts before dead-lettering (default 8) |
+| `AWARENESS_MAX_ATTEMPTS` | Delivery attempts before dead-lettering (default 3) |
 | `AWARENESS_DELIVERY_POLL_MS` | Delivery engine poll interval (default 2000) |
 | `NEO4J_URI` / `NEO4J_USER` / `NEO4J_PASSWORD` | Standard eVault Neo4j vars — reused by the one-time backfill |
 | `PUBLIC_AWARENESS_API_URL` | (portal) AaaS API base URL |

services/awareness-service/api/src/config.ts

@@ -27,7 +27,7 @@ export const config = {
         .filter(Boolean),
     /** Secret used to sign portal session JWTs. */
     jwtSecret: process.env.AAAS_JWT_SECRET ?? "awareness-dev-secret",
-    maxAttempts: parseInt(process.env.AWARENESS_MAX_ATTEMPTS ?? "8", 10),
+    maxAttempts: parseInt(process.env.AWARENESS_MAX_ATTEMPTS ?? "3", 10),
     deliveryPollMs: parseInt(
         process.env.AWARENESS_DELIVERY_POLL_MS ?? "2000",
         10,