--- name: owner-templates description: "Owner's \"templates\" — UI/code elements to PRESERVE (not delete) as reusable templates, disabled from active code" metadata: node_type: memory type: feedback originSessionId: 0b7c5f41-bb34-4ab4-93be-fdb363f5eb40 --- The owner keeps certain unused/dead UI elements as "TEMPLATES": do NOT delete them in cleanup/refactors. Instead, turn each into a reusable template — kept in the codebase but DISABLED from active code (not rendered/used) — so it can be repurposed for a future feature. When any audit (code-quality, mobile, etc.) flags one of these as "dead code → remove," OVERRIDE that: convert to template, don't remove. **Why:** Owner (2026-06-28): "keep update banner, we'll use it for something else. turn it into a template and disable it from active code … remember my templates." They want a saved, reusable inventory of disabled-but-kept components. **Template registry (preserve as templates, never delete):** - **#updateBanner** — the old non-blocking update banner (CSS + keyframes in terminal.css; A4/A5 flagged as dead code). KEEP as a template; owner will reuse it for something else. Disable from active code, keep the markup/CSS definition cleanly labeled as a template. - **FO3 "no data until 2.0.0" warning** — the message stating FO3 has no data until version 2.0.0 (owner clarified 2026-06-28 this is the specific element). Turn into a template too — kept + disabled, reusable. DESIGNATED REUSE (owner 2026-06-29): repurpose this template for FALLOUT 4's initial no-data state — show it for the FO4 context, relabeled to "4," until FO4 data is populated. See [[parked-fallout4-support]]. **How to apply:** maintain this list; add any new element the owner designates a "template." In any plan or implementation, the disposition for these is "convert to template (kept, disabled)," NOT "remove." TIMING DECIDED (owner 2026-06-28): FOLD the template conversion INTO the broader implementation work — do NOT do it as a standalone task. *Corrected 2026-07-20: removed a note asserting which registry files exist under `js/` — that is a code fact, look it up in `library/CODE_MAP.md`.*