@zigrivers/scaffold 3.33.4 → 3.33.5

package/content/knowledge/VERSION

@@ -1 +1 @@
-0.1.8
+0.1.10

package/content/knowledge/browser-extension/browser-extension-architecture.md

@@ -1,13 +1,25 @@
 ---
 name: browser-extension-architecture
-description: Component isolation across content scripts, background service workers, and popup pages; message passing patterns; and state synchronization strategies
-topics: [browser-extension, architecture, message-passing, state-synchronization, service-worker, content-scripts]
+description: >-
+  Component isolation across content scripts, background service workers, and popup pages; message passing patterns; and
+  state synchronization strategies
+topics:
+  - browser-extension
+  - architecture
+  - message-passing
+  - state-synchronization
+  - service-worker
+  - content-scripts
 volatility: evolving
-last-reviewed: null
-version-pin: 'Manifest V3'
+last-reviewed: 2026-06-05
+version-pin: Manifest V3
 sources:
   - url: https://developer.chrome.com/docs/extensions/mv3/architecture-overview
+    hash: sha256:138a4d2e5659d81c90bdf5914adef0d119793f3e665aeea5183863b06f469d12
+    retrieved: 2026-06-05
   - url: https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/Anatomy_of_a_WebExtension
+    hash: sha256:25478eeaaec350aa31f533f52c1c34042cd13a133bd5add6d23f567265ce862b
+    retrieved: 2026-06-05
 ---
 
 Browser extension architecture is fundamentally different from web app architecture because the application is split across multiple isolated execution environments that cannot share memory directly. Content scripts run inside host pages but in an isolated JavaScript world. Service workers run in a separate context that is terminated and re-created between events. Popup pages are ephemeral — they exist only while the popup is open. These constraints drive every architectural decision: communication is via message passing, state must be externalized to `chrome.storage`, and every component must tolerate being initialized from scratch at any time.

package/content/knowledge/browser-extension/browser-extension-content-scripts.md

@@ -1,13 +1,25 @@
 ---
 name: browser-extension-content-scripts
-description: DOM manipulation from content scripts, isolated worlds, CSS injection, and communicating with the host page via postMessage
-topics: [browser-extension, content-scripts, dom-manipulation, isolated-worlds, css-injection, postmessage]
+description: >-
+  DOM manipulation from content scripts, isolated worlds, CSS injection, and communicating with the host page via
+  postMessage
+topics:
+  - browser-extension
+  - content-scripts
+  - dom-manipulation
+  - isolated-worlds
+  - css-injection
+  - postmessage
 volatility: fast-moving
-last-reviewed: null
-version-pin: 'Manifest V3'
+last-reviewed: 2026-06-05
+version-pin: Manifest V3
 sources:
   - url: https://developer.chrome.com/docs/extensions/develop/concepts/content-scripts
+    hash: sha256:21d93ef79a4d62b9593ff5f7c28e095031baace9884dbc1128b18ea26194cec2
+    retrieved: 2026-06-05
   - url: https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/Content_scripts
+    hash: sha256:6089f52945b1b44a6c9361351c91f0304634dc429bb822fa83c4e7ff109a37c2
+    retrieved: 2026-06-05
 ---
 
 Content scripts are the extension's interface with the web page. They run inside the page's DOM but in an isolated JavaScript world — they see the same HTML and can manipulate the same elements, but they cannot access the page's JavaScript variables or prototype chain without explicitly crossing the world boundary. Understanding this isolation is essential for writing content scripts that are both functional and secure.

package/content/knowledge/browser-extension/browser-extension-conventions.md

@@ -1,13 +1,23 @@
 ---
 name: browser-extension-conventions
 description: Naming conventions for manifests, message action types, file organization, and i18n structure in browser extensions
-topics: [browser-extension, conventions, naming, i18n, file-organization, messaging]
+topics:
+  - browser-extension
+  - conventions
+  - naming
+  - i18n
+  - file-organization
+  - messaging
 volatility: evolving
-last-reviewed: null
-version-pin: 'Manifest V3'
+last-reviewed: 2026-06-05
+version-pin: Manifest V3
 sources:
   - url: https://developer.chrome.com/docs/extensions/reference/manifest
+    hash: sha256:873da4e4724c4352c91929415bcb9e7b98b79f7773e26bf4387ad0137ae69753
+    retrieved: 2026-06-05
   - url: https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/Internationalization
+    hash: sha256:55fd96d3c9e92a0d13221f3485b9c7b82192a2fb95fa96586bfd2c091240ba04
+    retrieved: 2026-06-05
 ---
 
 Browser extensions accumulate technical debt faster than typical web apps because they span multiple execution contexts — content scripts, service workers, popup pages, options pages — each with distinct constraints. Consistent naming conventions and file organization make cross-context code navigable and reduce the cognitive overhead of working across these boundaries. Establish conventions before writing code.

package/content/knowledge/browser-extension/browser-extension-cross-browser.md

@@ -1,13 +1,26 @@
 ---
 name: browser-extension-cross-browser
-description: Using webextension-polyfill for API compatibility, manifest differences between Chrome and Firefox, browser-specific APIs, and managing a multi-browser build matrix
-topics: [browser-extension, cross-browser, firefox, chrome, webextension-polyfill, compatibility, build-matrix]
+description: >-
+  Using webextension-polyfill for API compatibility, manifest differences between Chrome and Firefox, browser-specific
+  APIs, and managing a multi-browser build matrix
+topics:
+  - browser-extension
+  - cross-browser
+  - firefox
+  - chrome
+  - webextension-polyfill
+  - compatibility
+  - build-matrix
 volatility: evolving
-last-reviewed: null
+last-reviewed: 2026-06-05
 version-pin: null
 sources:
   - url: https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/Browser_support_for_JavaScript_APIs
+    hash: sha256:4b0a8d2d7f7db598b7c1b745e49b32e5408a7ca6a58a99450aea1e3bd01fde60
+    retrieved: 2026-06-05
   - url: https://developer.chrome.com/docs/extensions/develop/migrate
+    hash: sha256:63ca45e8137178af34a42b750639120fe28502a27a59c476cfc77fb778f14b14
+    retrieved: 2026-06-05
 ---
 
 Browser extensions that target both Chrome and Firefox share most of their codebase, but the differences between the two platforms are significant enough to require explicit management. API namespaces differ, manifest syntax diverges in subtle ways, and some APIs exist only in Chrome or only in Firefox. A systematic cross-browser strategy prevents the "works in Chrome, broken in Firefox" class of bugs.

package/content/knowledge/browser-extension/browser-extension-dev-environment.md

@@ -1,13 +1,26 @@
 ---
 name: browser-extension-dev-environment
-description: Build tooling with Webpack/Vite, hot reload via web-ext and crx-hotreload, and browser launch configuration for extension development
-topics: [browser-extension, dev-environment, vite, webpack, hot-reload, web-ext, build]
+description: >-
+  Build tooling with Webpack/Vite, hot reload via web-ext and crx-hotreload, and browser launch configuration for
+  extension development
+topics:
+  - browser-extension
+  - dev-environment
+  - vite
+  - webpack
+  - hot-reload
+  - web-ext
+  - build
 volatility: evolving
-last-reviewed: null
+last-reviewed: 2026-06-05
 version-pin: null
 sources:
   - url: https://developer.chrome.com/docs/extensions/get-started/tutorial/hello-world
+    hash: sha256:dc673d9b594c057cf68896851b5c211552f4b7f3876c22a568c95348b0155075
+    retrieved: 2026-06-05
   - url: https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/Your_first_WebExtension
+    hash: sha256:0f4e414a029b2c3f6e6c1ba5709dd88822fc61cddde1ac58af60f3dffad8d53d
+    retrieved: 2026-06-05
 ---
 
 Browser extension development requires a different local setup than web app development. There is no dev server to navigate to — the extension must be loaded into a real browser instance, and changes require either a manual reload or a dedicated hot-reload tool. Getting this setup right at the start of the project eliminates the most friction-heavy part of the development loop.

package/content/knowledge/browser-extension/browser-extension-manifest.md

@@ -1,13 +1,26 @@
 ---
 name: browser-extension-manifest
-description: Manifest V3 schema, permissions declarations, host_permissions, content_scripts configuration, and background service_worker setup
-topics: [browser-extension, manifest, manifest-v3, permissions, content-scripts, service-worker, host-permissions]
+description: >-
+  Manifest V3 schema, permissions declarations, host_permissions, content_scripts configuration, and background
+  service_worker setup
+topics:
+  - browser-extension
+  - manifest
+  - manifest-v3
+  - permissions
+  - content-scripts
+  - service-worker
+  - host-permissions
 volatility: fast-moving
-last-reviewed: null
-version-pin: 'Manifest V3'
+last-reviewed: 2026-06-05
+version-pin: Manifest V3
 sources:
   - url: https://developer.chrome.com/docs/extensions/reference/manifest
+    hash: sha256:0bbe598d0affd4b9431dabcde7a0410f81e95b38092d6b258bf796135c438ab6
+    retrieved: 2026-06-05
   - url: https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/manifest.json
+    hash: sha256:cea8bb2558b2918998720b80649d5e9551491afec633fede6d338f913b55a5bc
+    retrieved: 2026-06-05
 ---
 
 The `manifest.json` is the contract between your extension and the browser. Every capability your extension uses must be declared here before it can be used. Manifest V3 (MV3) is the current standard, having replaced Manifest V2 (MV2) in Chrome. Understanding the MV3 schema in depth prevents runtime errors, store rejections, and security review failures.

package/content/knowledge/browser-extension/browser-extension-project-structure.md

@@ -1,13 +1,24 @@
 ---
 name: browser-extension-project-structure
-description: Directory layout for browser extensions covering src/popup, src/content, src/background, src/options, public/icons, and _locales
-topics: [browser-extension, project-structure, file-organization, build, icons]
+description: >-
+  Directory layout for browser extensions covering src/popup, src/content, src/background, src/options, public/icons,
+  and _locales
+topics:
+  - browser-extension
+  - project-structure
+  - file-organization
+  - build
+  - icons
 volatility: evolving
-last-reviewed: null
-version-pin: 'Manifest V3'
+last-reviewed: 2026-06-05
+version-pin: Manifest V3
 sources:
   - url: https://developer.chrome.com/docs/extensions/develop
+    hash: sha256:fc24f69c0d484d9806c95229ddf1c29a1fd9a03cc81ccc9f837548725171a5ef
+    retrieved: 2026-06-05
   - url: https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/Anatomy_of_a_WebExtension
+    hash: sha256:25478eeaaec350aa31f533f52c1c34042cd13a133bd5add6d23f567265ce862b
+    retrieved: 2026-06-05
 ---
 
 Browser extension project structure must account for multiple compilation targets (one bundle per execution context), static assets that bypass the build pipeline, and locale files consumed by the WebExtensions runtime. A well-organized project structure makes build configuration straightforward, keeps context-specific code isolated, and prevents accidentally importing browser APIs that are unavailable in a given context.

package/content/knowledge/browser-extension/browser-extension-requirements.md

@@ -1,13 +1,25 @@
 ---
 name: browser-extension-requirements
-description: User permissions model, store policies (Chrome Web Store, AMO), accessibility requirements, and performance budgets for browser extensions
-topics: [browser-extension, requirements, permissions, store-policies, accessibility, performance]
+description: >-
+  User permissions model, store policies (Chrome Web Store, AMO), accessibility requirements, and performance budgets
+  for browser extensions
+topics:
+  - browser-extension
+  - requirements
+  - permissions
+  - store-policies
+  - accessibility
+  - performance
 volatility: evolving
-last-reviewed: null
-version-pin: 'Manifest V3'
+last-reviewed: 2026-06-05
+version-pin: Manifest V3
 sources:
   - url: https://developer.chrome.com/docs/webstore/program-policies
+    hash: sha256:b920f88cdb7ee59c5e91d45357680c06a781db04bdfc72aa242e3dde71862838
+    retrieved: 2026-06-05
   - url: https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/AMO/Policy
+    hash: sha256:9791bbdf9ed9ecd0f0b6b8478bda286ab4fce4c7544a0100186b5fa28988daa1
+    retrieved: 2026-06-05
 ---
 
 Browser extension requirements differ fundamentally from web app requirements because the extension operates inside a user's browser with elevated trust and broad access to browsing data. Every permission requested must be justified, every store policy must be understood before writing code, and performance budgets must be set early because extensions run on every page a user visits — regressions directly degrade the entire browsing experience.

package/content/knowledge/browser-extension/browser-extension-security.md

@@ -1,14 +1,29 @@
 ---
 name: browser-extension-security
-description: Content Security Policy for extensions, prohibitions on eval and inline scripts, host permissions principle of least privilege, and XSS prevention in extension UIs
-topics: [browser-extension, security, csp, xss, permissions, least-privilege, eval]
+description: >-
+  Content Security Policy for extensions, prohibitions on eval and inline scripts, host permissions principle of least
+  privilege, and XSS prevention in extension UIs
+topics:
+  - browser-extension
+  - security
+  - csp
+  - xss
+  - permissions
+  - least-privilege
+  - eval
 volatility: evolving
-last-reviewed: null
-version-pin: 'Manifest V3'
+last-reviewed: 2026-06-05
+version-pin: Manifest V3
 sources:
   - url: https://developer.chrome.com/docs/extensions/reference/manifest/content-security-policy
+    hash: sha256:e4c7c42933e4e917edd5cf2b5aa3e3d6a13f07ebdfad927d4bda567f6c8c175f
+    retrieved: 2026-06-05
   - url: https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/Content_Security_Policy
+    hash: sha256:d06e2e28a6173edd2dfd58b02f2d5c5e0665a76da98dea2b4f9a8f07c2ecfb4d
+    retrieved: 2026-06-05
   - url: https://owasp.org/www-community/attacks/xss/
+    hash: sha256:e2d634a57647ee73a8aced85e0950560020e44324931468de07e36d1bba49c1d
+    retrieved: 2026-06-05
 ---
 
 Browser extensions run with elevated browser privileges compared to ordinary web pages. A compromised extension can read browsing history, intercept network requests, steal cookies, and inject content into any page it has permission to access. Security is not optional — it is a first-class requirement enforced by the browser, the store review process, and the trust of every user who installs the extension.

package/content/knowledge/browser-extension/browser-extension-service-workers.md

@@ -1,13 +1,26 @@
 ---
 name: browser-extension-service-workers
-description: Extension service worker lifecycle (install/activate), event-driven programming model, alarms API for recurring tasks, and persistent state via chrome.storage
-topics: [browser-extension, service-worker, lifecycle, alarms, chrome-storage, event-driven, background]
+description: >-
+  Extension service worker lifecycle (install/activate), event-driven programming model, alarms API for recurring tasks,
+  and persistent state via chrome.storage
+topics:
+  - browser-extension
+  - service-worker
+  - lifecycle
+  - alarms
+  - chrome-storage
+  - event-driven
+  - background
 volatility: fast-moving
-last-reviewed: null
-version-pin: 'Manifest V3'
+last-reviewed: 2026-06-05
+version-pin: Manifest V3
 sources:
   - url: https://developer.chrome.com/docs/extensions/develop/concepts/service-workers
+    hash: sha256:088fdeebf41909724c31ae64f779d25853ce91dab3d30d48fe6876beb697984a
+    retrieved: 2026-06-05
   - url: https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/Background_scripts
+    hash: sha256:74c09f9ce0e40ed769c4c1128493ee5749df7b9d5359b7a815c6dfbd18069aff
+    retrieved: 2026-06-05
 ---
 
 The Manifest V3 background service worker is the most architecturally disruptive change from MV2. The persistent background page that could hold state indefinitely is gone. Service workers are event-driven and ephemeral — Chrome terminates them when idle and restarts them when events arrive. Every design decision for background logic must account for this constraint.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@zigrivers/scaffold",
-  "version": "3.33.4",
+  "version": "3.33.5",
   "description": "AI-powered software project scaffolding pipeline",
   "type": "module",
   "workspaces": [