Knowledge Fetch

Phase 3 of the inverted pipeline. The WebFetch body-pull happens inside the Phase-2 curators, so this skill no longer fetches by default — it reads each candidate's fetch sub-object from <project>/.metadata/candidates.json and assembles the canonical <project>/.metadata/fetch-manifest.json directly. Its remaining active job is opt-in cobrowse (--cobrowse or the interactive prompt): it walks the user through enabling the Claude-in-Chrome browser extension and dispatches source-fetcher sequentially to do two things — recover WebFetch misses (merging rescues into the manifest) and additively top up thin primary-tier sources (reading the fuller browser body beyond WebFetch's cap, superseding the cached body only if strictly longer, never degrading a usable one).

Read ${CLAUDE_PLUGIN_ROOT}/references/inverted-pipeline.md §"Phase 3 — knowledge-fetch" and references/fetch-cache-design.md once to anchor on the contract.

When to run

• candidates.json exists for the project (Phase 2 has run) AND either fetch-manifest.json does not yet exist OR the user explicitly wants to re-fetch (e.g., after evicting stale cache entries)
• User explicitly invokes /cogni-knowledge:knowledge-fetch

Never run when

• No candidates.json exists at <project_path>/.metadata/ — offer knowledge-curate first.
• No binding.json exists at the resolved knowledge root.

Parameters