docs: surface refinement/triage workflow to end users (Phase 0 / cache / ingest)

[MScottAdams]

Problem

The Phase 0 triage / refinement / local-ingest workflow introduced under #845 and rebound onto the unified cache under #883 is the canonical way to drain a real-sized backlog without burning the shared GraphQL bucket — but it is currently only discoverable by reading agent-facing skill prose. End users (especially new maintainers) have no documented path from README.md to "here is how to ingest open issues, work them locally, and avoid #976-class GraphQL drains."

This is an adoption blocker: the institutional knowledge exists, but only the agent can reach it.

Evidence

• README.md mentions deft-directive-refinement exactly once (Platform Requirements list) with no description, no link, and no workflow guidance. There is no triage:bootstrap / Phase 0 / three-tier mention anywhere in the README.
• docs/getting-started.md does not mention triage, refinement, or ingest at all.
• docs/CONCEPTS.md and docs/ARCHITECTURE.md do not cover the flow.
• commands.md does not surface task triage:* and task cache:fetch-all with user-shaped (verb -> outcome) descriptions.
• The full description of the three-tier model (.deft-cache/github-issue/ / vbrief/.eval/candidates.jsonl / vbrief/proposed/), the action menu, and the rate-limit-friendly flags (--limit, --state, --batch-size, --delay-ms) lives only inside skills/deft-directive-refinement/SKILL.md, which is written for the agent.

The user-discoverable interface today is effectively the trigger-word list inside AGENTS.md Skill Routing (line 51) -- if a user does not know to say "triage" / "work the cache" / "pre-ingest", the workflow is invisible.

Proposed Remediation

Three small, additive doc surfaces (one PR is sufficient):

1. README.md — add a short "Backlog triage" subsection under the existing "Build With AI" / Quick Start area. Trigger words, one code fence with the scoped first-run command, and a link into docs/getting-started.md.

2. docs/getting-started.md — add a "Working an existing backlog" section explaining:

   • task triage:bootstrap -- --limit 50 --state open for a scoped first populate.
   • The Phase 0 action menu (accept | reject | defer | needs-ac | mark-duplicate) and where accepted items land (vbrief/proposed/).
   • The three-tier model in user vocabulary (cache / audit log / accepted backlog) and why writes flow only through task triage:accept.
   • Why this avoids the shared GraphQL bucket drain (REST-backed cache, batched delays, no live gh issue view per decision).

3. commands.md — surface task triage:* and task cache:fetch-all with one-line user-facing descriptions (verb -> outcome), not just task names. Cross-link to the getting-started section above.

Acceptance Criteria

• README.md Quick Start area links to the new getting-started section and names the trigger words.
• docs/getting-started.md contains a "Working an existing backlog" section covering the bullets above.
• commands.md lists task triage:bootstrap, task triage:accept|reject|defer|needs-ac|mark-duplicate, task triage:bulk-*, task triage:refresh-active, and task cache:fetch-all / task cache:get with user-facing descriptions.
• All three surfaces use the same vocabulary as skills/deft-directive-refinement/SKILL.md (no drift between agent-facing and user-facing copy).
• At least one cross-reference back to fix(scm,tests): eliminate remaining GraphQL-backed scm.py / live SCM smoke bucket drain after #961 #976 / GraphQL bucket discipline so the reader understands why the scoped flags exist.

Out of Scope

• Restructuring the skill itself (the SKILL.md is the canonical agent-facing source of truth; this issue is purely about exposing the same surface to humans).
• Adding new task verbs or changing the existing task triage:* CLI surface.

Related

• feat(triage,cache,refinement): pre-ingest triage workflow with sidecar issue cache (refs #583 #788 #789 #815 #522) #845 — Phase 0 triage action menu
• feat(processes): deft-cache — unified content cache and quarantine layer (blocks #845, #610) #883 — Unified cache surface (Story 2 cache rules, Story 3 triage rebind)
• fix(scm,tests): eliminate remaining GraphQL-backed scm.py / live SCM smoke bucket drain after #961 #976 — Remaining SCM/GraphQL bucket drain (this issue is the user-facing companion: the ingest flow that prevents the drain is currently undiscoverable)
• skills/deft-directive-refinement/SKILL.md — canonical agent-facing description of the flow