Removed mention of deprecated feature

Author: JoeShade

README.md

@@ -138,11 +138,6 @@ Downloads/
 
 Password and token fields are blank when the settings page opens, and each field has a local show/hide button for checking typed values. New values are kept for the current browser session by default. Tick the relevant `Remember ... on this device` box only if you accept the risk of storing that secret in the browser profile.
 
-For authenticated SamacSys ZIP downloads, upstream auth precedence is:
-
-1. Generated Basic auth from `SamacSys username` and `SamacSys password`.
-2. No upstream auth header.
-
 ## <img src="docs/assets/readme/icon-faq.svg" alt="" width="20" height="20" align="absmiddle"> FAQ
 
 <details>

systemDesign.md

@@ -52,9 +52,6 @@ The current repository does not implement:
 - In Firefox relay mode, the service worker forwards matching `componentsearchengine.com` cookies through the relay so authenticated ZIP downloads can reuse the user's upstream browser session.
 - Firefox relay mode can send a separate relay `Authorization` header on the Worker POST when the user configures helper-service auth.
 - Firefox relay mode can forward an upstream SamacSys `Authorization` header for ZIP endpoints that rely on HTTP Basic auth instead of cookies alone.
-- Across authenticated SamacSys ZIP flows, upstream auth precedence is:
-  - locally generated HTTP Basic auth header from SamacSys username and password stored for the session or explicitly remembered on this device
-  - no upstream authorization header
 - The Manifest V3 background is declared for both Chrome and Firefox: Chrome uses `background.service_worker`, while Firefox uses the background-document fallback from `background.scripts`. This combined manifest relies on Firefox 121 or newer.
 - The configurable library download root must remain relative to the browser's Downloads directory.