docs: Documentation analysis and improvement

[github-actions]

Closes #1003

Summary of files analyzed

• docs/workflows/gh-aw-automerge.md
• .github/workflows/gh-aw-automerge.yml
• scripts/obs/classifyAutomergeDependencyCollection.ts
• scripts/obs/checkAutomergeDependencyCollection.ts

Issues found

• docs/workflows/gh-aw-automerge.md: The check-dependency-collection job description only documented blocking when a collection is not active, but implementation blocks downstream jobs for additional non-allowed outcomes.
• .github/workflows/gh-aw-automerge.yml: approve and automerge are both gated on needs.check-dependency-collection.outputs.allowed == 'true', so all non-allowed outcomes are blocked.
• scripts/obs/classifyAutomergeDependencyCollection.ts: Classifier emits non-allowed statuses inactive, ambiguous, and unclassified.
• scripts/obs/checkAutomergeDependencyCollection.ts: All non-allowed statuses return allowed: false and upsert the dependency-collection gate comment.

Changes made

• Updated docs/workflows/gh-aw-automerge.md (check-dependency-collection bullet in the Jobs section) to explicitly state that only allowed proceeds, and that inactive, ambiguous, and unclassified skip approve/automerge and trigger the gate comment.
• Rationale: Aligns documentation with current workflow and script behavior to remove ambiguity about which classification outcomes block automerge.

---

What is this? | From workflow: Observability Agentic Workflow Entrypoint

Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.