f736e6f584
The provider now takes a thunk rather than a value: it projects the
authoritative section per search, so a stored endpoint, model, or key
reference reaches the next call without re-registering the provider — which
would make the seam's provider selection observable as a flicker.
apiKey already carries role('secret'), so the section is safe to describe:
the literal never rides a response in any layer and a configuration surface
learns only that a key is set.
7 lines
442 B
YAML
7 lines
442 B
YAML
# Bilingual-pair consistency record (docs/i18n/README.md): the git blob hash of each
|
|
# side as of the last confirmed-consistent state. Both languages carry equal authority;
|
|
# after editing either side, bring the other along and re-record with:
|
|
# pnpm run verify-translation-pairing --write packages/web/web-search-deepseek/README.md
|
|
README.md: 3e8b631b5775793e6e6e542c810edce9d92a0d59
|
|
README.zh.md: 9bd59000c2a0054265444aa90fc46ff5f34fd607
|