Add side panel issue creation workflow

docs/extension-management.md

@@ -1,6 +1,6 @@
 # Extension Management
 
-This project builds a Chrome extension from the generated `dist/` directory. Run `npm run build` before loading or reloading the unpacked extension.
+This project builds a Chrome side panel extension from the generated `dist/` directory. Run `npm run build` before loading or reloading the unpacked extension.
 
 ## Required Chrome Profile
 
@@ -13,7 +13,7 @@ This rule applies to:
 - Opening Chrome for extension work.
 - Loading `dist/` as an unpacked extension.
 - Reloading the extension after a build.
-- Inspecting extension popups, background/service worker behavior, or permissions.
+- Inspecting extension side panel, background/service worker behavior, or permissions.
 - Any browser automation that depends on extension state.
 
 ## Build Output
@@ -35,6 +35,14 @@ Required variables:
 - `VITE_GITEA_REPO_OWNER`
 - `VITE_GITEA_REPO_NAME`
 
+## Issue Creation
+
+- Add Issue is enabled only when the active tab's base URL is already in the URLs list and that URL is linked to a Gitea repo.
+- The Add Issue view must show the Gitea repo that will receive the issue.
+- Screenshot capture uses Chrome's visible-tab capture API and requires the extension's `activeTab` permission.
+- Created issue bodies must include `Chrome profile: Silma`.
+- When Ready is checked, create the issue, upload screenshots/files as Gitea issue assets, then apply the `ready` label last.
+
 ## Agent Checklist
 
 1. Run `npm run build`.