docs: seventh-pass archive unsafe legacy references

documentation/PROJECT__Documentation_Refresh_and_Archive_Plan_2026.md

@@ -44,6 +44,9 @@ Do not delete historical context; move to `documentation/archive/` with clear na
 - Validated all `documentation/*.md` references in active docs; no missing targets remain.
 - Added ownership and review-trigger metadata to the bootstrap, task list, and docs index.
 - Reviewed active project docs for archive eligibility. Object Field Editor and Site Passcode Security remain active and were added to the docs index.
+- Archived legacy API-object, component-inventory, data-structure, performance, and UI-pattern references that contradicted V3 IDs, Svelte 5, or current private-route execution rules.
+- Refreshed `AE__Architecture.md` and `AE__Naming_Conventions.md` as the active replacements.
+- Added `documentation/archive/README.md` to explain archive categories and restoration policy.
 
 ### Next archive candidates (review + approve)
 - Older style-review snapshots once current style guide references are centralized.
@@ -61,6 +64,6 @@ Monthly lightweight review:
 ## 5) Immediate Follow-Up Tasks
 
 1. Run a quarterly archive review: identify stale `PROJECT__` docs with no TODO or index linkage and move them to `documentation/archive/`.
-2. Review `AE__*` reference docs for overlap, outdated stack assumptions, and inconsistent naming.
+2. Review remaining `AE__*` docs (`Permissions`, Docker policy, and UI future ideas) against current source and decide whether each remains active reference or proposal material.
 3. Review module docs against current routes and store names rather than relying only on filename/header freshness.
 4. Add a lightweight reusable link-check script if manual path validation becomes frequent.