Add GitHub workflow guidance

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,40 @@
+name: Bug report
+description: Report broken behavior, a regression, or a crash.
+labels:
+  - bug
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Search open and closed issues first, and keep the report focused on one problem.
+
+  - type: textarea
+    id: description
+    attributes:
+      label: Description
+      description: Explain what happened and what you expected to happen.
+    validations:
+      required: true
+
+  - type: textarea
+    id: reproduction
+    attributes:
+      label: Steps to reproduce
+      description: Provide the smallest reliable reproduction you have.
+      placeholder: |
+        1.
+        2.
+        3.
+
+  - type: input
+    id: environment
+    attributes:
+      label: Environment
+      description: Include the macOS version, PlexBar version, and Plex Media Server version when known.
+      placeholder: macOS 26.0, PlexBar 1.0, Plex Media Server 1.41.9
+
+  - type: textarea
+    id: evidence
+    attributes:
+      label: Additional evidence
+      description: Add relevant screenshots, recordings, logs, or crash reports. Redact sensitive information.

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1 @@
+blank_issues_enabled: true

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -0,0 +1,31 @@
+name: Feature request
+description: Propose a focused improvement or new capability.
+labels:
+  - enhancement
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Search open and closed issues first, and keep the request focused on one change.
+
+  - type: textarea
+    id: problem
+    attributes:
+      label: Problem or goal
+      description: Explain what is difficult, missing, or not possible today.
+    validations:
+      required: true
+
+  - type: textarea
+    id: proposal
+    attributes:
+      label: Proposed change
+      description: Describe the desired behavior and what would make the request complete.
+    validations:
+      required: true
+
+  - type: textarea
+    id: context
+    attributes:
+      label: Additional context
+      description: Add related issues, screenshots, mockups, examples, or references.

.github/pull_request_template.md

@@ -0,0 +1,22 @@
+## What Changed
+
+<!-- Describe the change clearly and keep scope tight. -->
+
+## Why
+
+<!-- Explain the problem being solved and why this approach was chosen. -->
+
+## UI Changes
+
+<!-- If this PR changes UI, include clear before/after screenshots.
+     If the change involves motion or interaction, include a short video.
+     Delete this section if not applicable. -->
+
+## Related Issues
+
+<!-- Link related issues, for example: Closes #123. Delete this section if not applicable. -->
+
+## Validation
+
+<!-- List the builds, tests, and manual checks performed, including results.
+     If none were performed, explain why. -->

AGENTS.md

@@ -31,6 +31,29 @@ This file defines project constraints for coding agents working in this reposito
 - Do not add heuristic fallback logic, automatic failover paths, multi-strategy retries, or "best effort" guessing unless a maintainer explicitly asks for that behavior.
 - When something fails, prefer surfacing the concrete failure and fixing the root cause over adding alternate code paths that mask the problem.
 
+## Branches, Commits, and Pull Requests
+
+- Use plain lowercase kebab-case for branch names. Keep names descriptive and do not include issue numbers, prefixes, or namespaces such as `feature/`, `fix/`, usernames, or agent names.
+- Before every commit or amend, show the exact current diff and validation, then get explicit approval. Branch or pull-request requests are not commit approval; later changes require fresh approval.
+- Never amend, rebase, squash, reset, rewrite history, or force-push without explicit approval for that exact operation.
+- Write commit messages entirely lowercase. Use the imperative mood for the subject, keep each commit focused on one logical change, do not use type or scope prefixes, and do not end the subject with a period. Add a body when the reason or important tradeoffs are not clear from the subject.
+- Keep each pull request focused on one coherent change.
+- Write concise, specific, imperative pull request titles in sentence case. Do not use prefixes or trailing periods, and make the title understandable without the branch name.
+- Pull request descriptions must include `What Changed`, `Why`, and `Validation`. Include `UI Changes` only when the pull request changes the UI. Include `Related Issues` when applicable. Keep descriptions concise, self-contained, complete, and accurate to the final diff.
+- Review the complete diff before opening a pull request. Update the title and description whenever the scope changes, and remove unrelated changes.
+
+## Issues
+
+- Search open and closed issues before creating a new issue.
+- Keep each issue focused on one problem or change.
+- Use a concise, specific, sentence-case title without type prefixes.
+- Give enough context to understand the issue without first inspecting the code.
+- For bugs, describe the current and expected behavior. Include reproduction steps, environment details, and supporting evidence when available.
+- For enhancements, explain the problem or goal, the desired outcome, and clear acceptance criteria.
+- For UI issues, include screenshots. Include a short video when motion or interaction is relevant.
+- Link any related issues and pull requests.
+- Apply the appropriate existing label when creating an issue: `bug` for bugs and `enhancement` for feature requests.
+
 ## Building
 
 From repo root (`/Users/austinsmith/Developer/Repos/PlexBar`), build with: