Add agentic workflow unbloat-docs

.github/workflows/shared/docs-server-lifecycle.md

@@ -0,0 +1,73 @@
+---
+# Documentation Server Lifecycle Management
+# 
+# This shared workflow provides instructions for starting, waiting for readiness,
+# and cleaning up the Astro Starlight documentation preview server.
+#
+# Prerequisites:
+# - Documentation must be built first (npm run build in docs/ directory)
+# - Bash permissions: npm *, curl *, kill *, echo *, sleep *
+# - Working directory should be in repository root
+---
+
+## Starting the Documentation Preview Server
+
+**Context**: The documentation has been pre-built using `npm run build`. Use the preview server to serve the static build.
+
+Navigate to the docs directory and start the preview server in the background:
+
+```bash
+cd docs
+npm run preview > /tmp/preview.log 2>&1 &
+echo $! > /tmp/server.pid
+```
+
+This will:
+- Start the preview server on port 4321
+- Redirect output to `/tmp/preview.log`
+- Save the process ID to `/tmp/server.pid` for later cleanup
+
+## Waiting for Server Readiness
+
+Poll the server with curl to ensure it's ready before use:
+
+```bash
+for i in {1..30}; do
+  curl -s http://localhost:4321 > /dev/null && echo "Server ready!" && break
+  echo "Waiting for server... ($i/30)" && sleep 2
+done
+```
+
+This will:
+- Attempt to connect up to 30 times (60 seconds total)
+- Wait 2 seconds between attempts
+- Exit successfully when server responds
+
+## Verifying Server Accessibility (Optional)
+
+Optionally verify the server is serving content:
+
+```bash
+curl -s http://localhost:4321/gh-aw/ | head -20
+```
+
+## Stopping the Documentation Server
+
+After you're done using the server, clean up the process:
+
+```bash
+kill $(cat /tmp/server.pid) 2>/dev/null || true
+rm -f /tmp/server.pid /tmp/preview.log
+```
+
+This will:
+- Kill the server process using the saved PID
+- Remove temporary files
+- Ignore errors if the process already stopped
+
+## Usage Notes
+
+- The server runs on `http://localhost:4321`
+- Documentation is accessible at `http://localhost:4321/gh-aw/`
+- Always clean up the server when done to avoid orphan processes
+- If the server fails to start, check `/tmp/preview.log` for errors

.github/workflows/shared/mood.md

@@ -0,0 +1 @@
+.

.github/workflows/shared/reporting.md

@@ -0,0 +1,73 @@
+---
+# Report formatting guidelines
+---
+
+## Report Structure Guidelines
+
+### 1. Header Levels
+**Use h3 (###) or lower for all headers in your issue report to maintain proper document hierarchy.**
+
+When creating GitHub issues or discussions:
+- Use `###` (h3) for main sections (e.g., "### Test Summary")
+- Use `####` (h4) for subsections (e.g., "#### Device-Specific Results")
+- Never use `##` (h2) or `#` (h1) in reports - these are reserved for titles
+
+### 2. Progressive Disclosure
+**Wrap detailed test results in `<details><summary><b>Section Name</b></summary>` tags to improve readability and reduce scrolling.**
+
+Use collapsible sections for:
+- Verbose details (full test logs, raw data)
+- Secondary information (minor warnings, extra context)
+- Per-item breakdowns when there are many items
+
+Always keep critical information visible (summary, critical issues, key metrics).
+
+### 3. Report Structure Pattern
+
+1. **Overview**: 1-2 paragraphs summarizing key findings
+2. **Critical Information**: Show immediately (summary stats, critical issues)
+3. **Details**: Use `<details><summary><b>Section Name</b></summary>` for expanded content
+4. **Context**: Add helpful metadata (workflow run, date, trigger)
+
+### Design Principles (Airbnb-Inspired)
+
+Reports should:
+- **Build trust through clarity**: Most important info immediately visible
+- **Exceed expectations**: Add helpful context like trends, comparisons
+- **Create delight**: Use progressive disclosure to reduce overwhelm
+- **Maintain consistency**: Follow patterns across all reports
+
+### Example Report Structure
+
+```markdown
+### Summary
+- Key metric 1: value
+- Key metric 2: value
+- Status: ✅/⚠️/❌
+
+### Critical Issues
+[Always visible - these are important]
+
+<details>
+<summary><b>View Detailed Results</b></summary>
+
+[Comprehensive details, logs, traces]
+
+</details>
+
+<details>
+<summary><b>View All Warnings</b></summary>
+
+[Minor issues and potential problems]
+
+</details>
+
+### Recommendations
+[Actionable next steps - keep visible]
+```
+
+## Workflow Run References
+
+- Format run IDs as links: `[§12345](https://github.com/owner/repo/actions/runs/12345)`
+- Include up to 3 most relevant run URLs at end under `**References:**`
+- Do NOT add footer attribution (system adds automatically)