Let's queue up another round of updates/reviews/refinement on the /doc

You are being dispatched from flower Brief #144: Let's queue up another round of updates/reviews/refinement on the /doc

Recall pointer:
- Use recall_brief with id 144 for the full folder if you need provenance.

Target:
- project: flower (/Users/mikeferrara/Documents/code/flower)
- branch: flower/144-docs-refinement
- worktree: not specified
- kind: fresh

Current brief spec:
## Goal
Another refresh pass on flower's **in-app `/docs`**: reconcile them against features shipped since the last docs pass, and do a broad drift/accuracy sweep across all `/docs` pages. Deliverable is a **reviewable change set / PR of proposed edits** (not a gap-list-first).

## Scope (operator, Q25 — both selected)
1. **Reconcile against shipped features.** Diff current `/docs` content against what has actually shipped since the last docs pass (completed/merged briefs + commits) and update anything describing changed or new behavior. Likely candidates: briefs → dispatch lifecycle, the daemon roster + lifecycle (reset / wind-down / compaction, auto-arm per #155), the MCP tool surface (`recall_*` / `brief_*` / `daemon_*`), adversarial review (#143, once built), storage/ingest.
2. **Broad drift/accuracy refresh across ALL in-app `/docs`.** Sweep every `/docs` page for stale or incorrect statements, dead references, renamed tools/routes, and outdated examples; fix inaccuracies and tighten wording.

## Deliverable (operator, Q26)
**Proposed edits directly** — a concrete change set / PR against the `/docs` content for the operator to review (NOT a gap/issues list first). Organize edits **by doc page** so review is easy.

## Investigation / grounding
- Locate the in-app `/docs` source of truth (the `/docs` route + its markdown/Blade sources) and enumerate the pages.
- Cross-check against recently completed/merged briefs + commits since the last docs pass to find what is newly shipped or changed.

## Acceptance
- A reviewable change set updating `/docs`: shipped-feature reconciliation + broad drift/accuracy fixes, grouped by page.
- No broken internal doc links/refs; examples and tool/route names match the current surface.
- `php artisan test` green + `./vendor/bin/pint` on any touched code. `Brief: #144` trailer.

## Provenance
Operator note (#144, 2026-07-03). Scope + deliverable answered by operator 2026-07-03 (Q25 = reconcile-against-shipped + broad drift refresh; Q26 = proposed-edits/PR). Answers folded → planned by flower-refine 2026-07-03.

Recent/key trace events:
[1] participant_joined operator:mike: (no body)
[2] note_added operator:mike: Let's queue up another round of updates/reviews/refinement on the /docs in flower
[3] status_change operator:mike: (no body)
[4] participant_joined flower-refine: (no body)
[5] agent_question flower-refine: Another round on the flower /docs — what should this round focus on?
[6] agent_question flower-refine: What deliverable do you want out of this round first?
[7] operator_answer operator:mike: Reconcile docs against features shipped since the last pass + Broad drift/accuracy refresh across all in-app /docs
[8] operator_answer operator:mike: Proposed edits directly (a change set/PR to review)
[9] link_added flower-refine: (no body)
[10] spec_snapshot flower-refine: Let's queue up another round of updates/reviews/refinement on the /docs in flower
[11] refinement flower-refine: ## Goal
Another refresh pass on flower's **in-app `/docs`**: reconcile them against features shipped since the last docs pass, and do a broad drift/accuracy sweep across all `/docs` pages. Deliverable is a **reviewable change set / PR of proposed edits** (not a gap-list-first).

## Scope (operator, Q25 — both selected)
1. **Reconcile against shipped features.** Diff current `/docs` content against what has actually shipped since the last docs pass (completed/merged briefs + commits) and update anything describing changed or new behavior. Likely candidates: briefs → dispatch lifecycle, the daemon roster + lifecycle (reset / wind-down / compaction, auto-arm per #155), the MCP tool surface (`recall_*` / `brief_*` / `daemon_*`), adversarial review (#143, once built), storage/ingest.
2. **Broad drift/accuracy refresh across ALL in-app `/docs`.** Sweep every `/docs` page for stale or incorrect statements, dead references, renamed tools/routes, and outdated examples; fix inaccuracies and tighten wording.

## Deliverable (operator, Q26)
**Proposed edits directly** — a concrete change set / PR against the `/docs` content for the operator to review (NOT a gap/issues list first). Organize edits **by doc page** so review is easy.

## Investigation / grounding
- Locate the in-app `/docs` source of truth (the `/docs` route + its markdown/Blade sources) and enumerate the pages.
- Cross-check against recently completed/merged briefs + commits since the last docs pass to find what is newly shipped or changed.

## Acceptance
- A reviewable change set updating `/docs`: shipped-feature reconciliation + broad drift/accuracy fixes, grouped by page.
- No broken internal doc links/refs; examples and tool/route names match the current surface.
- `php artisan test` green + `./vendor/bin/pint` on any touched code. `Brief: #144` trailer.

## Provenance
Operator note (#144, 2026-07-03). Scope + deliverable answered by operator 2026-07-03 (Q25 = reconcile-against-shipped + broad drift refresh; Q26 = proposed-edits/PR). Answers folded → planned by flower-refine 2026-07-03.
[12] status_change flower-refine: (no body)

Recommended linked context:
{
    "todos": [],
    "scratchpads": [
        {
            "id": 375,
            "solo_scratchpad_id": "1067",
            "name": "flower-refine — reset handoff (2026-07-03 #2)",
            "archived": false,
            "revision": 2
        }
    ]
}

Execution notes:
- Treat the brief as the source of truth.
- Keep work scoped to this dispatch request.
- Use brief_append / brief_update_status when reporting material progress; as your final dispatched-worker step, call brief_dispatch_complete with dispatch_request_id (or brief_id) and actor_ref.
- Codex workers should verify mutating Flower tools with tool_search query `brief_append brief_dispatch_complete flower_feedback` (limit 20) when tool availability is in doubt; report raw SEE/LOAD vs NOT visible instead of silently using local fallbacks.
- Add a git commit trailer `Brief: #144` to every commit for this brief so flower can exact-link commits back to the brief.