feat: persistent model caching, premium prompt templates, and UI selectors

[Mr-Dark-debug]

Description

This PR introduces several significant features and optimizations to ReddJSON:

1. Persistent Model Caching:

   • Cache fetched model lists from OpenRouter and Groq in local storage.
   • Prevents redundant, slow API requests on every settings tab opening, improving load time and protecting API rate limits.

2. Premium LinkedIn Post Templates:

   • Seeds 4 custom-tailored writing styles:
     • LinkedIn Viral Staircase (highly scannable ladder layout, bold hooks)
     • Narrative Storyteller (engaging problem-solving narrative structure)
     • Actionable Playbook (clear how-to masterclass style)
     • Contrarian Debate (thoughtful analysis of misconceptions/unpopular views)
   • Automatically migrates/seeds on install or update without overwriting custom templates.

3. Context-Specific Template Switchers (UI/UX):

   • Reddit 'Post' Button Right-Click: Right-click the 'Post' button on Reddit to choose a template.
   • Sidebar History Post Generation: Instantly generate posts from saved History JSON using any prompt template.

4. General Quality-of-Life Improvements:

   • Dark Mode: High-contrast, premium dark mode auto-detected and toggleable.
   • Export/Import: JSON export/import for history and AI posts history.
   • Search Debouncing: Efficient local-memory search filtering.
   • Escape Key: Quick modal closing.
   • Sidebar Toasts: Non-intrusive feedback indicators.

🤖 Generated with Claude Code

[gemini-code-assist]

Code Review

This pull request updates the ReddJSON extension to version 2.1, introducing a dark mode theme, export/import capabilities for history and AI posts, keyboard shortcuts, JSON filtering options (Full Thread vs. Post Only), and storage size optimizations. The review feedback identifies several critical and medium-severity issues, including a bug where settings can be overwritten with null during history import, a logic flaw in the cache eviction policy for processed post IDs, a portability issue with detached DOM nodes during export, a missing safety guard for uninitialized settings providers, and unhandled promise rejections when communicating with disconnected content scripts.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[gemini-code-assist]

Critical Bug: Settings Overwritten with null on History Import

When importing history, the code attempts to save settings by calling chrome.runtime.sendMessage with settings: currentSettings.

However, currentSettings is initialized to null and is only populated when the user visits the Settings tab. If a user imports history immediately after opening the sidebar (without visiting the Settings tab first), currentSettings will be null. This will send null to the background script, which completely overwrites and wipes out all of the user's configured API keys, default models, and custom prompts in chrome.storage.local.

Since saving settings is completely unnecessary during a history import, this call should be removed entirely.

                const merged = [...newEntries, ...existing].slice(0, 50);
                await chrome.storage.local.set({ reddjson_history: merged });

[gemini-code-assist]

Portability Issue: Detached DOM Node Click

Calling .click() on a detached <a> element (one that is not appended to the document DOM) fails to trigger a download in several browsers (such as Firefox) and under strict security policies in Chrome.

To ensure cross-browser compatibility and robust download behavior, temporarily append the element to document.body before clicking it, and then remove it immediately afterward.

Suggested change

	function exportAsJSON(data, filename) {
	const blob = new Blob([JSON.stringify(data, null, 2)], { type: 'application/json' });
	const url = URL.createObjectURL(blob);
	const a = document.createElement('a');
	a.href = url;
	a.download = `${filename}-${new Date().toISOString().slice(0, 10)}.json`;
	a.click();
	URL.revokeObjectURL(url);
	}
	function exportAsJSON(data, filename) {
	const blob = new Blob([JSON.stringify(data, null, 2)], { type: 'application/json' });
	const url = URL.createObjectURL(blob);
	const a = document.createElement('a');
	a.href = url;
	a.download = `${filename}-${new Date().toISOString().slice(0, 10)}.json`;
	document.body.appendChild(a);
	a.click();
	document.body.removeChild(a);
	URL.revokeObjectURL(url);
	}

[gemini-code-assist]

Missing Safety Guard for currentSettings.providers

If currentSettings.providers is undefined (e.g., if settings are uninitialized or cleared), accessing currentSettings.providers[pid] will throw a TypeError and crash the click handler.

Add a defensive check to ensure currentSettings.providers is initialized as an object before accessing its properties, similar to how it is handled in other parts of the file.

Suggested change

	if (!currentSettings.providers[pid]) currentSettings.providers[pid] = {};
	currentSettings.providers[pid].selectedModel = modelId;
	if (!currentSettings.providers) currentSettings.providers = {};
	if (!currentSettings.providers[pid]) currentSettings.providers[pid] = {};
	currentSettings.providers[pid].selectedModel = modelId;

[gemini-code-assist]

Logic Bug in Cache Eviction Policy

In the current implementation of trackPostId, if the added id is already present in the processedPostIds Set and the Set size is at the limit (CONFIG.maxProcessedIds), the code will evict the first element from the Set and then add the id. Since the id is already in the Set, adding it is a no-op, which incorrectly shrinks the Set size by 1.

To fix this and implement a proper FIFO/LRU update, check if the Set already has the id first. If it does, delete it so that re-adding it moves it to the end (refreshing its freshness) without evicting any other elements.

  if (processedPostIds.has(id)) {
    processedPostIds.delete(id);
  } else if (processedPostIds.size >= CONFIG.maxProcessedIds) {
    const first = processedPostIds.values().next().value;
    processedPostIds.delete(first);
  }
  processedPostIds.add(id);

[gemini-code-assist]

Unhandled Promise Rejection in chrome.tabs.sendMessage

If the content script is not active, has been unloaded, or is disconnected (e.g., on special Reddit pages or immediately after an extension update), calling chrome.tabs.sendMessage will throw an error: "Could not establish connection. Receiving end does not exist."

Since this is an asynchronous call, leaving it unhandled will trigger an unhandled promise rejection. Add a .catch() block to handle this gracefully.

Suggested change

	if (!result.success) {
	chrome.tabs.sendMessage(tab.id, { action: 'showToast', message: result.error, type: 'error' });
	return;
	}
	if (!result.success) {
	chrome.tabs.sendMessage(tab.id, { action: 'showToast', message: result.error, type: 'error' }).catch(() => {});
	return;
	}

[gemini-code-assist]

Unhandled Promise Rejection in chrome.tabs.sendMessage

Similar to other message sending calls, if the content script is disconnected or not loaded, chrome.tabs.sendMessage will throw an error. Add a .catch() block to prevent unhandled promise rejections.

Suggested change

	const pretty = JSON.stringify(result.data, null, 2);
	chrome.tabs.sendMessage(tab.id, { action: 'copyToClipboard', text: pretty });
	const pretty = JSON.stringify(result.data, null, 2);
	chrome.tabs.sendMessage(tab.id, { action: 'copyToClipboard', text: pretty }).catch(() => {});