feat(repo): /archon-rollout must skip spec issues and wayfinder maps when selecting work

[orioltf]

Parent: #297 · Found by the comprehensive review of #298 (M11, code half)

Problem

ready-for-agent no longer identifies an implementable ticket on its own. Three kinds of issue can
carry it, and only one is dispatchable:

Issue	Body shape	Dispatchable
Ticket from /to-tickets	## What to build + ## Acceptance criteria + ## Blocked by	yes
Spec from /to-spec	Problem Statement, Solution, User Stories, …	no
wayfinder:map and its decision tickets	Destination / Notes / Decisions-so-far, or a bare question	no

/to-spec applies ready-for-agent itself, and its only in-session check is about test seams — not
the spec body. So a spec issue lands in the same query /archon-rollout sweeps. Dispatching one sends
an agent at a whole feature described as user stories, with no acceptance criteria and no ## Blocked by
edges to sequence against.

#298 documented the hazard (docs/process/development-workflow.md Phases 5-6,
docs/agents/triage-labels.md, ONBOARDING.md) and left the selection logic alone. Documentation asks
a human to remember; this issue makes the command enforce it.

Acceptance criteria

• /archon-rollout skips any issue labelled wayfinder:map or wayfinder:*
• It skips an issue whose body has no ## What to build and no ## Acceptance criteria, and
  says which issues it skipped and why — silence would look like the issue did not exist
• A spec issue passed explicitly by number is refused with the reason, not dispatched
• The rule lives in one place in the command, next to the existing dependency-tree derivation
• docs/process/development-workflow.md's "treat its issue list as needing a glance" caveat is
  removed once the filter exists

---

🤖 Filed with Claude Code.