[q] Always key mermaid nodes; never delete mermaid diagrams in unbloat

[github-actions]

Q Workflow Optimization Report

Trigger: /q update unbloat agentic workflows to always key mermaid diagrams. never deleted them.

Changes Made

unbloat-docs.md — preserve mermaid diagrams

• Added Mermaid diagram blocks to the DO NOT REMOVE list with an explicit note that these blocks must never be deleted — even if surrounding prose is trimmed, the diagram itself stays.
• Added a keying rule: when the workflow encounters mermaid nodes with single-letter IDs (A, B, C), it must update them to short, descriptive snake_case keys that reflect the concept (e.g. schedule, orch, repo_a).

archie.md — enforce meaningful node keys at generation time

• Added guideline 4: Always Key Nodes — every node must have a descriptive snake_case ID; single-letter IDs like A/B/C are explicitly prohibited.
• Updated the example flowchart to use meaningful keys (start, process, decision, action_yes, action_no) instead of A–E.
• Added a validation checklist item: All node IDs are meaningful snake_case keys.

Expected Improvements

• Mermaid diagrams in docs are never accidentally deleted by the unbloat agent.
• All mermaid diagrams generated by Archie use descriptive node IDs that survive edits and remain traceable.
• Any legacy single-letter node IDs encountered during unbloat runs will be upgraded in-place.

Validation

All modified workflows compiled successfully:

• ✅ unbloat-docs — no errors, no warnings
• ✅ archie — no errors, no warnings

Note: .lock.yml files will be regenerated automatically after merge.

---

Warning

Protected Files — Push Permission Denied

This was originally intended as a pull request, but the patch modifies protected files. A human must create the pull request manually.

Protected files

• .github/workflows/archie.md

• .github/workflows/unbloat-docs.md

The push was rejected because GitHub Actions does not have workflows permission to push these changes, and is never allowed to make such changes, or other authorization being used does not have this permission.

Create the pull request manually

# Download the patch from the workflow run
gh run download 27158765218 -n agent -D /tmp/agent-27158765218

# Create a new branch
git checkout -b q/mermaid-keying-rules-ea0082e11d27285a main

# Apply the patch (--3way handles cross-repo patches)
git am --3way /tmp/agent-27158765218/aw-q-mermaid-keying-rules.patch

# Push the branch and create the pull request
git push origin q/mermaid-keying-rules-ea0082e11d27285a
gh pr create --title '[q] Always key mermaid nodes; never delete mermaid diagrams in unbloat' --base main --head q/mermaid-keying-rules-ea0082e11d27285a --repo github/gh-aw

🎩 Equipped by Q · ⌖ 13.7 AIC · ◷

• expires on Jun 10, 2026, 10:48 AM UTC-08:00