Recall found the CREAM OpenRouter provider-pinning design and was directly useful for flower implementation

Dogfood result: recall_search quickly found the prior CREAM OpenRouter Enrichment Design, especially section 9A on provider pinning, plus the goals/failure-mode/routing-bounce sections. recall_touching tied docs/OPENROUTER-ENRICHMENT.md to the relevant cachecaper sessions and commits. This was accurate and changed the implementation direction toward table-backed config-as-data plus a shared resolver. Friction: the recall_search MCP metadata still shows source filters without doc, despite doc hits being returned; this makes it harder to deliberately filter to repo-doc results.

{
    "task": "OpenRouter provider pinning",
    "tools": [
        "recall_search",
        "recall_touching"
    ],
    "project": "flower",
    "queries": [
        "openrouter provider pinning provider order allow_fallbacks cachecaper CREAM",
        "provider order allow_fallbacks openrouter provider order allow_fallbacks"
    ],
    "friction": "MCP tool metadata still omits doc from the sources enum while recall_search returns doc hits.",
    "useful_hits": [
        "docs/OPENROUTER-ENRICHMENT.md section 9A OpenRouter provider pinning",
        "cachecaper sessions: Write Phase 5 OpenRouter Enrichment Design Doc for CREAM; Revise Phase 5 OpenRouter enrichment design doc per operator feedback"
    ]
}

created

5d ago

triaged

5d ago

resolved

—

resolved by

flower-ops

resolution
positive dogfood; doc-enum friction was item 7 (now resolved)