diff --git a/AGENTS.md b/AGENTS.md index b12d3f7..146ecd8 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -36,6 +36,7 @@ Use `.env.local` for local secrets. Keep `.env.local` and any real token-bearing - `vite.config.ts` emits `dist/manifest.json` during production builds. - `dist/` is the deployable output directory. Deployment or Chrome load-unpacked flows should point directly at `dist/`. - `dist/` is generated output and should not be edited directly. +- Static extension assets live in `public/`; the current favicon source is `public/favicon.svg`. - `npm run build` runs `scripts/verify-dist.mjs` after Vite to ensure the generated output has the required extension files. - Host permissions are derived from `VITE_GITEA_BASE_URL`. Rebuild after changing the base URL. - Runtime API calls are centralized in `src/api.ts`. diff --git a/README.md b/README.md index bf3a5ce..7a54233 100644 --- a/README.md +++ b/README.md @@ -24,6 +24,8 @@ npm run build The deployable extension output is `dist/`. Load `dist/` in Chrome as an unpacked extension, or point deployment tooling at that folder. `npm run build` runs TypeScript, Vite, and a post-build check that verifies `dist/manifest.json` and the popup entry exist. +Static assets, including the favicon, live in `public/` and are copied into `dist/` during the build. + ## Extension Management See [docs/extension-management.md](docs/extension-management.md) before loading, reloading, testing, or automating the Chrome extension. diff --git a/index.html b/index.html index 41b31e2..4978324 100644 --- a/index.html +++ b/index.html @@ -3,6 +3,7 @@
+