Chrome Extension

Build and Release Constraints

Build entry points, manifest constraints, content-script output rules, and contributor expectations

Build and Release Constraints

Unified Build Entry

The extension build should go through:

npm run build:extension

It will:

bump the extension patch version
run TypeScript validation
emit products/chrome-extension/dist

Why Local Partial Builds Are Not Enough

The extension has a few hard constraints:

manifest.json depends on stable file names
the content script cannot silently turn into a module/chunk graph
Extension Popup, options, and Inline Composer should be validated together

Contributor Expectations

always rebuild after extension changes
if user-facing behavior changes, update /docs
if architecture, build rules, or implementation boundaries change, update /devdocs

Inline Composer and Shortcuts

The content-script interaction layer, Shadow DOM UI, selection trigger, shortcuts, and state handling

Design and Interaction Specs

UI architecture, interaction boundaries, and product design direction for contributors

Table of Contents

Build and Release Constraints Unified Build Entry Why Local Partial Builds Are Not Enough Contributor Expectations