3da966a52a
Master's docs-overhaul stack (#142-#144) rewrote AGENTS.md into the slim budget-gated form and repointed the review skill's citations. Resolutions: - AGENTS.md: master's rewrite wins; the no-hardcoded-tunables convention is re-added as one terse bullet in the new style, after 'Explicit > implicit at package seams'. Within the verify-doc-budgets ceiling, so no displacement or raise needed. - dsh-code-review SKILL.md: master's repointed citations win; the hardcoded-tunables reviewer check and the Conventions keyword are re-applied on top. - packages/README.md: master replaced the hand-maintained dependency list (which carried this branch's chars-per-token wording) with a pointer to the generated module graph — master's side taken whole; the estimator wording lives on in the compact package READMEs.
web/ - web capability family
The web access capability seam: an abstract web interface, search/fetch provider implementations, and the model-facing web tools. All product packages.
| Package | Role | ctx key |
|---|---|---|
web/ |
Abstract web seam (search/fetch provider registries + selection + vocabulary + WebError) |
ctx.web |
web-search-exa/ |
Exa-backed WebSearchProvider |
(registers on ctx.web) |
web-search-perplexity/ |
Perplexity-backed WebSearchProvider |
(registers on ctx.web) |
web-search-deepseek/ |
DeepSeek-backed WebSearchProvider using native web_search through the Anthropic-compatible API |
(registers on ctx.web) |
web-fetch-local/ |
Anonymous public HTTP(S) WebFetchProvider |
(registers on ctx.web) |
tool-web/ |
Model-facing web_search/web_fetch tool schemas |
(registers on ctx.tools) |
The interface lives at web/web/. Unlike bash/fs, the seam spans two capabilities (search and fetch) with potentially multiple providers each: ctx.web is one web-access middle layer with one provider-selection policy, one abort/error vocabulary, and one product-facing "how this harness reaches the web" config surface. Providers register capabilities, not tools; tool-web is the only owner of model-facing names, schemas, prompt guidance, and presentation. A search provider swap does not change how the model asks for a query, and a fetch implementation swap does not change how the model asks for a URL.
See the web capability seam RFC for the design rationale, including why search and fetch are deliberately one seam and why web_fetch's SSRF protection is deferred.