[FEATURE]: Avoid over-strict rejection for vault resource tasks (Bengali hardware notes)

Summary

Opencode rejected a valid vault task as "not a software engineering task" (see screenshot: For opencode help, run /help). The same task succeeded after a "continue", so the filter is over-strict. Triggered via OmniRoute combo auto/cheap:free (Build · Free Fast Best · 20s) — footer also showed Model 'auto/cheap:free' is not a valid combo.

Original request

Fetch 9 product pages from kzbangladesh.com and create a detailed comparison note in 7.Resources/11.Hardware (which is good / why / best value / best / budget). Note content requested in Bengali.

Links:

• https://kzbangladesh.com/product/kz-m2-type-c-ofc-silver-plated-cable-built-in-omnidirectional-microphone/
• https://kzbangladesh.com/product/kz-m2-dual-mic-type-c-eq-tuning-switch-silver-plated-upgrade-cable/
• https://kzbangladesh.com/product/kz-m2-dual-mic-silver-plated-integrated-professional-upgrade-cable/
• https://kzbangladesh.com/product/cca-c1-silver-plated-usb-type-c-cable-with-dac-chip-mic/
• https://kzbangladesh.com/product/cca-a2-type-c-built-in-dac-multiple-sound-modes-cable-with-light/
• https://kzbangladesh.com/product/cca-silver-plated-156-cores-cable-with-mic/
• https://kzbangladesh.com/product/kz-784-cores-gold-silver-and-copper-mixed-upgrade-cable/
• https://kzbangladesh.com/product/kz-784-cores-silver-blue-hybrid-upgrade-cable/
• https://kzbangladesh.com/product/kz-ofc-flat-upgrade-cable-2-pin-type-b-c-0-75mm-with-mic/

Target: C:\Users\dev-pc\My Drive\obsidian\redVault\7.Resources\11.Hardware

What happened

1. Webfetched all 9 URLs, then hard-refused: "These appear to be product pages for audio cables, not a software engineering task..."
2. User asked to continue (simple note-taking).
3. Same task then succeeded — created 3.KZ-CCA-Upgrade-Cable-Comparison-9-Cables.md.

Why this is in-scope

• Vault already has 1.Monitor-Buying-Guide.md and 2.Audio - TWS vs Neckband... — hardware notes are expected.
• The action is webfetch + write + websearch inside workspace — a core opencode capability.
• Engineers do need hardware/audio info (focus gear, mics, Web Audio/DAC work).

Suggestion

• Don't hard-reject file operations based on topic. Treat workspace writes as in-scope.
• Show a warning + "Continue anyway" instead of a hard refusal.