Add issue label selection

docs/extension-management.md

@@ -40,15 +40,17 @@ Required variables:
 - 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 and the active URL the extension believes it is attached to.
 - The Add Issue form must let the user select the agent file for handoff. Agents are managed in the Agents view, persisted in `chrome.storage.local`, and the initial agent is `GLOBAL AGENT` backed by `AGENTS.md`.
-- The Add Issue view intentionally omits the redundant view header title/description and keeps the Ready checkbox label short.
+- The Add Issue view intentionally omits the redundant view header title/description.
+- Add Issue and selected issue editing expose these label options: `Change Request`, `Idea`, `Tabitha`, `Orson`, `Belisarius`, `Ozymandias`, and `Ready`.
+- New issues default to `Change Request` selected unless the user changes the label selection.
+- Do not show the old Ready checkbox; `Ready` is now a selectable label.
 - Screenshot capture uses Chrome's visible-tab capture API and requires the extension's `activeTab` permission plus `<all_urls>` host permission so capture still works after the side panel remains open across tab changes.
 - Captured screenshots should appear immediately in Add Issue as thumbnail rows.
 - Captured screenshots can be expanded, closed, removed, or cropped before upload. The crop UI should use a plain draggable/resizable crop box instead of shaded slider-based controls, and the preview panel should fit the available viewport without horizontal scrolling.
 - File attachments are accumulated across picker selections and all selected files must be uploaded to Gitea.
 - Created issue bodies must include `Chrome profile: Silma` and the selected agent.
 - Created issues must upload the selected rendered agent file as a Gitea issue asset. Supported template variables in agent content are `{{git}}`, `{{repo}}`, `{{workspace}}`, `{{url}}`, `{{baseUrl}}`, `{{profile}}`, and `{{issue}}`.
-- Newly created issues must include the `Change Request` label.
-- When Ready is checked, create the issue, upload the rendered agent file plus screenshots/files as Gitea issue assets, then apply the `ready` label last.
+- Newly created issues must use the selected labels.
 
 ## Open Issues
 
@@ -57,11 +59,11 @@ Required variables:
 - The `Only current repo` checkbox defaults to checked and limits the table to the active URL's linked Gitea repo.
 - Turning off `Only current repo` loads recent issues from all repos already loaded in the extension.
 - The status dropdown defaults to `Open` and supports `Open`, `Closed`, and `Open + Closed`.
-- Selecting an issue shows a direct Open in Gitea link, editable issue subject/content fields, issue attachments, comment chain, and a comment form for text, additional screenshots, and file attachments.
+- Selecting an issue shows a direct Open in Gitea link, editable issue subject/content/label fields, issue attachments, comment chain, and a comment form for text, additional screenshots, and file attachments.
 - Saving selected issue edits must use the repo identity from the selected Open Issues row and must not fall back to the active tab's repo.
 - Issue comments should upload screenshots/files as issue assets first, then create a comment containing links to those attachments.
 - Existing issue attachments can be deleted from the selected issue.
-- Existing issue rows can apply the `ready` label or delete the issue. Deletion must require confirmation.
+- Existing issue rows can delete the issue. Issue labels are edited in the selected issue form. Deletion must require confirmation.
 - Typing in Add Issue, selected issue edit fields, Open Issues comments, or Agents editor fields must not blur the focused control.
 
 ## URL Management