Always key mermaid nodes with descriptive IDs; never delete mermaid diagrams in unbloat

[Copilot]

Two workflow prompt gaps allowed mermaid diagrams to be silently deleted during unbloat runs, and Archie generated diagrams with opaque single-letter node IDs (A, B, C) that broke traceability across edits.

unbloat-docs.md

• Adds Mermaid diagram code blocks to the DO NOT REMOVE list — ```mermaid blocks must never be deleted
• Adds §6a: when single-letter node IDs are encountered, upgrade them descriptively in-place as part of the same edit:

  # Before
  graph TD
      A[Start] --> B[Process]
      B --> C{Decision}
  
  # After
  graph TD
      Start[Start] --> Process[Process]
      Process --> Decision{Decision}
  

archie.md

• Updates the bundled flowchart example to use descriptive IDs so the template models correct practice
• Adds guideline Add workflow: githubnext/agentics/weekly-research #5: always use descriptive node IDs; never single-letter
• Adds a validation checklist item and success criterion enforcing the same rule

[Copilot]

Pull request overview

This PR updates the repository’s workflow prompt documentation to (1) prevent Mermaid diagrams from being deleted during “unbloat” runs and (2) standardize Mermaid diagrams on descriptive node IDs for traceability across edits.

Changes:

• Extend unbloat-docs.md preservation rules to explicitly forbid deleting mermaid blocks and add an “upgrade single-letter node IDs” rule.
• Update archie.md guidance, examples, and validation/success criteria to require descriptive Mermaid node IDs.
• Modify .github/aw/actions-lock.json by removing cached pins for github/gh-aw-actions/setup* at v0.78.3.

Show a summary per file

File	Description
.github/workflows/unbloat-docs.md	Adds “don’t delete Mermaid blocks” plus guidance to rename single-letter Mermaid node IDs in-place.
.github/workflows/archie.md	Enforces descriptive Mermaid node IDs in guidelines, examples, checklist, and success criteria.
.github/aw/actions-lock.json	Removes github/gh-aw-actions/setup* cache entries (potentially affecting pin sync / compilation fallback behavior).

Copilot's findings

Tip

Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

• Files reviewed: 2/2 changed files
• Comments generated: 1