fix(docs): allow Velt adapter examples (#575)

## summary

fixes the release-blocking docs validation failures from the Velt
vendor-official adapter page

this updates the docs integration-test allowlists so `velt` is an
expected vendor-official adapter slug and `@veltdev/chat-sdk-adapter` is
accepted in docs code examples

no changeset needed because this only updates test expectations for
existing docs content

fix(docs): allow Velt adapter examples (#575)

## summary

fixes the release-blocking docs validation failures from the Velt
vendor-official adapter page

this updates the docs integration-test allowlists so `velt` is an
expected vendor-official adapter slug and `@veltdev/chat-sdk-adapter` is
accepted in docs code examples

no changeset needed because this only updates test expectations for
existing docs content

fix(docs): allow Velt adapter examples (#575)

## summary

fixes the release-blocking docs validation failures from the Velt
vendor-official adapter page

this updates the docs integration-test allowlists so `velt` is an
expected vendor-official adapter slug and `@veltdev/chat-sdk-adapter` is
accepted in docs code examples

no changeset needed because this only updates test expectations for
existing docs content

fix(docs): allow Velt adapter examples (#575)

## summary

fixes the release-blocking docs validation failures from the Velt
vendor-official adapter page

this updates the docs integration-test allowlists so `velt` is an
expected vendor-official adapter slug and `@veltdev/chat-sdk-adapter` is
accepted in docs code examples

no changeset needed because this only updates test expectations for
existing docs content

fix(docs): allow Velt adapter examples (#575)

## summary

fixes the release-blocking docs validation failures from the Velt
vendor-official adapter page

this updates the docs integration-test allowlists so `velt` is an
expected vendor-official adapter slug and `@veltdev/chat-sdk-adapter` is
accepted in docs code examples

no changeset needed because this only updates test expectations for
existing docs content

fix(docs): allow Velt adapter examples (#575)

## summary

fixes the release-blocking docs validation failures from the Velt
vendor-official adapter page

this updates the docs integration-test allowlists so `velt` is an
expected vendor-official adapter slug and `@veltdev/chat-sdk-adapter` is
accepted in docs code examples

no changeset needed because this only updates test expectations for
existing docs content

fix(docs): allow Velt adapter examples (#575)

## summary

fixes the release-blocking docs validation failures from the Velt
vendor-official adapter page

this updates the docs integration-test allowlists so `velt` is an
expected vendor-official adapter slug and `@veltdev/chat-sdk-adapter` is
accepted in docs code examples

no changeset needed because this only updates test expectations for
existing docs content

fix(docs): allow Velt adapter examples (#575)

## summary

fixes the release-blocking docs validation failures from the Velt
vendor-official adapter page

this updates the docs integration-test allowlists so `velt` is an
expected vendor-official adapter slug and `@veltdev/chat-sdk-adapter` is
accepted in docs code examples

no changeset needed because this only updates test expectations for
existing docs content

fix(docs): allow Velt adapter examples (#575)

## summary

fixes the release-blocking docs validation failures from the Velt
vendor-official adapter page

this updates the docs integration-test allowlists so `velt` is an
expected vendor-official adapter slug and `@veltdev/chat-sdk-adapter` is
accepted in docs code examples

no changeset needed because this only updates test expectations for
existing docs content

fix(docs): allow Velt adapter examples (#575)

## summary

fixes the release-blocking docs validation failures from the Velt
vendor-official adapter page

this updates the docs integration-test allowlists so `velt` is an
expected vendor-official adapter slug and `@veltdev/chat-sdk-adapter` is
accepted in docs code examples

no changeset needed because this only updates test expectations for
existing docs content