Replaced labels with icons in the SR and Action badges

README.md

@@ -37,11 +37,22 @@ If identity or roles cannot be validated, only these two features stay disabled;
 other opportunity features continue. Reload the page to refresh identity/roles.
 The unused identity token is discarded and redacted from debug responses.
 
+Consumer token recovery also handles HTTP 401/403, in addition to HTTP 200 with
+invalid JSON. It opens the existing SPA session URL in an inactive temporary tab,
+preserves the originating window and Firefox cookie store, and retries within
+the same five-attempt limit. Debug entries retain the HTTP status and recovery
+reason. The auxiliary tab is closed after valid JSON or exhausted retries.
+
 After a completed product-loading cycle with fresh API results, `resquestCrmServiceRequest` fetches all pages of
 `CRMServiceRequest` records with `SVC_PENDING_DELIVERY` and `ORA_SVC_MY_SR_TEAM_SRS`,
 using the existing general tokenrelay Bearer. It uses the Fusion `searchResources/latest`
 query endpoint, independently of the opportunity query version. Calls appear in
 the Service Requests debug category with masked credentials.
+After a complete successful SR query (HTTP 200 with valid responses on all pages),
+its result is reused for subsequent Reference/product cycles in the current page
+session. Refresh all explicitly clears it. Failed pages are retried up to five
+total attempts each; completed pages are not requested again. Resetting the query
+stops further retries from the previous run.
 
 Records are linked by `OpportunityName_Id_c.OptyNumber`. A green SR badge indicates
 one or more matches; its tooltip lists each SR number, title, reported hours, owner,
@@ -60,7 +71,8 @@ Products loaded from cache restore matching activity entries without network cal
 Missing, expired or mismatched entries are not treated as confirmed empty results;
 they wait for a real product refresh before a new activity query is allowed.
 Empty and entirely failed product cycles do not query activities. In mixed cycles,
-only fresh products permit activity API calls on cache misses; SR refreshes once.
+only fresh products permit activity API calls on cache misses; an already-loaded
+SR result is reused and associated with the new product update.
 Activity lookups do not advance the existing Last update timestamp.
 Closing and reopening the modal preserves results and does not
 reload products or trigger these lookups. Already-running product requests may
@@ -68,6 +80,12 @@ finish in the background and update their related activities.
 
 ## Workload Actions
 
+The missing Act badge includes a separate plus control that opens an Action form
+with Team, Start date, End Date, Status, Complexity and Notes. This is currently
+UI-only: Save is disabled and the form never submits a request. Cancel or
+Escape dismisses the form. Creation options and API integration are pending;
+the form is unavailable to SALES_REP users, like the other Action features.
+
 SR and Action filter badges appear before Status for users allowed to view these
 activities. They filter the loaded data without issuing requests and combine with
 the existing opportunity filters. The SR below 4h option replaces the other SR
@@ -78,7 +96,11 @@ with both positive and negative options selected, all activity states remain
 visible. These selections are kept in memory, not persisted.
 
 Workload Actions are queried in the background after the product cycle completes,
-using only fresh API results. Each distinct `RevnId` uses `requestWlActions` with
+and only after SR has completed successfully (or was restored/reused). If SR is
+unavailable, Actions are not requested and remain unknown rather than absent.
+Each failed workload lookup gets up to five total attempts, stopping on success
+or when its session is superseded. Cached products still do not trigger network
+lookups. Each distinct `RevnId` uses `requestWlActions` with
 the `WWB-TS` credential in `Wwb-Provider-Authorization`. The Act badge beside SR
 aggregates all products: green means an action's `owner` matches the general
 tokenrelay response's `principal`; red means no matching owner was found. `Act ?`