[Bug] backlog daily: no exportable comments + blocked/blockers visibility gaps

[djm81]

Describe the Bug

While using specfact backlog daily for daily standup, two issues make it hard to get a “full picture” without going interactive:

1. Comments / annotations are not exportable:

   • --interactive shows item detail and comments, but there is no flag to include the same comment/discussion context in exported outputs intended for Copilot/standup summaries.
   • --copilot-export currently exports only metadata (status/assignee/last-updated/points/priority) and omits description and comments.

   Request/expected: add an explicit option like --comments / --annotations (name TBD) that includes work item discussion/comments in --summarize / --summarize-to and/or --copilot-export for adapters that support it (ADO/GitHub).

2. Blocked items / blockers are not visible in a standup-friendly way:

   • When items are in Blocked state, the standup output shows them as Status: blocked, but the Blockers column is empty.
   • Additionally, in a typical standup run (e.g., filtering to Active items), blocked items (e.g., work item #628920) are not shown unless the user explicitly filters --state "Blocked". This makes it easy to miss key blockers unless you remember to run a second command.

   Request/expected:

   • Either auto-populate the Blockers column from ADO state/reason or a standard field when status is blocked, OR
   • Provide an option like --include-blocked (or broaden “open” state mapping) so the default standup view can surface blocked work alongside active work, and sort it to the top when --blockers-first is used.

To Reproduce

A) Comments/annotations not exportable (non-interactive)

1. Run a standup summary export:

   specfact backlog daily ado --ado-org <org> --ado-project <project> --state Active --limit 50 --summarize-to .specfact/standup-summarize.md

2. Run Copilot export:

   specfact backlog daily ado --ado-org <org> --ado-project <project> --state Active --limit 50 --copilot-export .specfact/standup-copilot-export.md

B) Blocked state / blockers visibility

1. Run standup for blocked items:

   specfact backlog daily ado --state "Blocked"

2. Observe the table: Status is blocked for each item, but the Blockers column remains empty.

Expected Behavior

A) Comments/annotations

• Add an explicit parameter (e.g., --comments or --annotations) that includes item comments/discussion in exports.
• Ideally:
  • --summarize / --summarize-to includes description + comments when --comments/--annotations is enabled (or by default if adapter supports it).
  • --copilot-export optionally includes description + comments when --comments/--annotations is enabled, so Copilot has full context without requiring interactive mode.

B) Blockers / blocked items

• For items in blocked status, the output should surface a meaningful blocker signal, e.g.:
  • Populate Blockers column from ADO fields (blocked reason, tags, or a dedicated field), OR
  • At minimum, show something like Blockers: Blocked (state) if the item is in Blocked state and no explicit blockers text exists.
• Standup command should optionally (or by default) include blocked items alongside active items in a standup view, especially when --blockers-first is used, to avoid missing critical blockers.

Actual Behavior

A) Comments/annotations

• No CLI option exists to include comments/annotations in exported outputs.
• --copilot-export output contains only status/assignee/last-updated/story points/priority (no description, no comments).
• --summarize-to includes descriptions, but comments are not included/visible in the export output (and the only documented way to review comments is --interactive).

B) Blockers / blocked items

• --state "Blocked" shows blocked items in the table, but the Blockers column is empty even though status is blocked.
• Blocked work can be missed in a normal standup run unless --state "Blocked" is run separately.

Environment

• OS: Windows
• Python Version: 3.11.6
• SpecFact CLI Version: 0.26.16 (specfact --version)
• Installation Method: pip installed into a virtual environment (venv)

Command Output

specfact backlog daily ado --state "Blocked"

SpecFact CLI - v0.26.16

Started: 2026-02-03 10:39:21

Daily standup
ID      Title (truncated)                                     Status   Last updated        Yesterday Today Blockers
123456  [Project 1] Improve feature XYZ ...             blocked  2026-01-05 13:45
123457  [PYPROJECT] Refactor our code basis ...                blocked  2026-01-23 09:21
123458  Improve table load logic                   blocked  2026-01-23 09:21

Finished: 2026-02-03 10:39:24

Codebase Context (for brownfield issues)

N/A (this is about specfact backlog daily + ADO adapter behavior, not analyzing a legacy codebase).

Additional Context

• Interactive mode (--interactive) is the only documented mode that mentions showing comments. We need a non-interactive export option for standup/Copilot workflows.
• Workaround today:
  • Run --summarize/--summarize-to for description context
  • Run a separate --state "Blocked" command to see blocked work
  • Use --interactive to view comments (but that doesn’t help when we want an “export then summarize” workflow)