GitHub Issue Summary Signpost Section

[flyingrobots]

Transition framing

This issue supersedes the legacy filesystem backlog card migrated from docs/method/backlog/cool-ideas/PROCESS_backlog-summary-signpost-section.md.

GitHub Issues are now the live tracker. The signpost summary should summarize Method-labeled GitHub Issues, not docs/method/backlog/** as the canonical queue.

Contract

Add a generated issue-summary section to an appropriate signpost such as docs/GUIDE.md, docs/BEARING.md, or another repo-facing Method surface.

The section should provide a bounded snapshot of:

• lane counts from lane:* labels
• active work-in-progress count
• high-priority pressure
• blocked or needs-design/needs-witness clusters
• release-milestone pressure when milestones are used

The section must be compact. It should answer "where is the work pressure?" without dumping every issue.

Acceptance criteria

• The summary cites GitHub Issues as the source of truth.
• The summary does not require reading legacy backlog files.
• The generated section is bounded and stable enough for review diffs.
• The docs explain whether the section is manually refreshed, command-generated, or release-generated.

[coderabbitai]

🔗 Related PRs

#1 - [codex] refresh METHOD signposts and legend structure [merged]
#5 - Shape release workflow and user migration docs [merged]
#18 - Land 0030-0033 repo-truth and MCP debt fixes [merged]
#20 - Add backlog notes for agent-first planning and review workflow [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!