fetch

Fetch

Reconstruct the observable website experience in the current workspace. A URL is a reference target, not permission to extract private data, server source, credentials, sessions, or protected assets.

Invocation

• Use $fetch <url> when Codex Chef installed the managed direct skill.
• Use $codex-chef-workflows:fetch <url> when invoking the installed plugin package directly.
• Keep implicit invocation disabled on both surfaces. A normal request that happens to mention fetching, scraping, or the JavaScript Fetch API must not activate this workflow.

Input Contract

• Require a valid https:// reference URL. Allow http://, localhost, an intranet host, or a non-standard port only when the user explicitly names that exact target and the active network policy permits it.
• Use the current workspace as the output target when it contains one clear application. If several apps or no safe output location exists, ask only for the target path.
• Treat a bare public URL as authority only for bounded, read-only inspection of public, unauthenticated pages and a local reconstruction with inert auth and lawful assets. Exact protected branding, private content, or publication still requires the user to confirm ownership or permission.
• Require explicit authorization before inspecting authenticated or private routes, using a test account, calling a non-public API, or writing outside the current workspace.
• Read safety-boundaries.md before any browser or network inspection.

Workflow

1. Route the work
   • Inspect repo instructions, scripts, stack, and dirty state first.
   • Keep implementation in the main thread. Use code_mapper, design_reviewer, frontend_verifier, or security_auditor only for independent mapping, visual review, browser verification, or auth risk.
   • Prefer a real browser through Playwright or Chrome DevTools. Raw HTTP downloads are supplemental because they miss client-rendered states.
2. Capture the reference
   • Follow capture-protocol.md.
   • Establish passive request and destination guards before the first navigation. If the selected browser tool cannot do that, stop as blocked.
   • Inventory routes, viewports, states, navigation, forms, assets, fonts, motion, console behavior, and sanitized request shapes.
   • Capture source screenshots before implementation. Do not use remembered appearance as evidence.
3. Build the reconstruction
   • Follow implementation-protocol.md.
   • Preserve the existing stack and conventions when a project already exists. Do not install or upgrade dependencies without approval.
   • Implement working local behavior, responsive states, loading, empty, error, focus, hover, and disabled states that were observed.
   • Replace unavailable server behavior with a clearly local fixture or mock. Never silently proxy a clone to a production mutation endpoint.
4. Verify in a real browser
   • Follow verification-rubric.md.
   • Compare source and local screenshots at matching viewport, route, scroll position, and UI state. Exercise navigation and interactions.
   • Fix material mismatches and rerun the narrowest relevant checks.
5. Prove completion
   • Create a fidelity report from fetch-report.template.json.
   • Run: