deepv-code 1.0.182 → 1.0.183

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "deepv-code",
-  "version": "1.0.182",
+  "version": "1.0.183",
   "engines": {
     "node": ">=20.0.0"
   },

package/bundle/assets/help/README.md

@@ -1,113 +0,0 @@
-# 智能帮助系统资源目录
-
-## 目录说明
-
-此目录包含 DeepV Code CLI 智能帮助系统的知识库文件。
-
-## 文件清单
-
-### `cli-help-knowledge.md`
-智能帮助系统的主知识库文件，包含：
-- 所有斜杠命令的详细说明
-- At 命令使用方法
-- Shell 模式说明
-- 配置系统文档
-- 常见问题解答
-- 使用场景示例
-- 故障排查指南
-
-**用途：** 作为 Help Subagent 的上下文，用于回答用户关于 CLI 功能的问题。
-
-**维护：** 当 CLI 添加新功能或修改现有功能时，需同步更新此文件。
-
-## 构建和打包
-
-### 开发阶段
-在开发时，文件位于：
-```
-packages/cli/src/assets/help/cli-help-knowledge.md
-```
-
-### 构建后
-构建后，文件应被复制到：
-```
-dist/assets/help/cli-help-knowledge.md
-bundle/cli/assets/help/cli-help-knowledge.md
-```
-
-### esbuild 配置
-需要在 `esbuild.config.js` 中添加资源复制配置：
-```javascript
-{
-  entryPoints: ['packages/cli/src/assets/help/cli-help-knowledge.md'],
-  loader: { '.md': 'text' },
-  outdir: 'dist/assets/help',
-}
-```
-
-### 构建脚本
-在 `scripts/build.js` 或 `scripts/copy_bundle_assets.js` 中添加：
-```javascript
-await copyAssets([
-  {
-    from: 'packages/cli/src/assets/help',
-    to: 'bundle/cli/assets/help',
-  },
-]);
-```
-
-## 使用方式
-
-### 在代码中加载
-```typescript
-import { readFileSync } from 'node:fs';
-import { join, dirname } from 'node:path';
-import { fileURLToPath } from 'node:url';
-
-const __dirname = dirname(fileURLToPath(import.meta.url));
-const helpKnowledgePath = join(__dirname, '../assets/help/cli-help-knowledge.md');
-const knowledgeBase = readFileSync(helpKnowledgePath, 'utf-8');
-```
-
-### 用于 Subagent
-```typescript
-const systemPrompt = `你是 DeepV Code CLI 的智能帮助助手。
-
-以下是完整的 CLI 功能知识库：
-
-${knowledgeBase}
-
-请根据知识库内容回答用户的问题。`;
-```
-
-## 知识库更新指南
-
-### 何时更新
-- 添加新的斜杠命令
-- 修改现有命令行为
-- 添加新的配置选项
-- 修改默认值或行为
-- 添加新的使用场景
-
-### 更新流程
-1. 修改 `cli-help-knowledge.md`
-2. 验证内容准确性
-3. 测试 Help Subagent 能否正确回答
-4. 提交代码变更
-
-### 内容原则
-- **准确性：** 确保所有信息与实际实现一致
-- **完整性：** 涵盖所有用户可能遇到的功能
-- **清晰性：** 使用简洁明确的语言
-- **示例：** 提供实际可用的示例代码
-- **可搜索：** 使用关键词便于 AI 检索
-
-## 相关文件
-
-- **设计文档：** `docs/cli/智能帮助系统设计方案.md`
-- **实现代码：** `packages/cli/src/ui/commands/HelpCommand.ts`（待实现）
-- **Subagent：** `packages/cli/src/services/HelpSubagent.ts`（待实现）
-
-## 许可证
-
-遵循项目主许可证（Apache-2.0）。

package/bundle/assets/sounds/README.md

@@ -1,74 +0,0 @@
-# 音频通知配置
-
-DeepV Code 支持在关键交互点播放提示音，提升用户体验。
-
-## 音频文件
-
-请将以下 WAV 格式音频文件放在此目录：
-
-- `response-complete.wav` - Agent响应完成时播放
-- `confirmation-required.wav` - 需要用户确认工具执行时播放  
-- `selection-made.wav` - 用户做出选择后播放
-
-## 配置选项
-
-在你的 `~/.deepv/settings.json` 文件中添加以下配置：
-
-```json
-{
-  "audioNotifications": {
-    "enabled": true,
-    "responseComplete": true,
-    "confirmationRequired": true,
-    "selectionMade": true
-  }
-}
-```
-
-### 配置说明
-
-- `enabled`: 总开关，设为 `false` 可完全禁用音频通知
-- `responseComplete`: Agent响应完成提示音
-- `confirmationRequired`: 工具执行确认提示音
-- `selectionMade`: 选择完成提示音
-
-## 测试音频
-
-运行以下命令测试音频功能：
-
-```bash
-dvcode --test-audio
-```
-
-## 跨平台支持
-
-音频通知支持以下平台：
-
-### Windows
-- 优先使用 PowerShell 播放自定义 WAV 文件
-- 备选使用系统提示音（不同频率区分类型）
-
-### macOS  
-- 优先使用 `afplay` 播放自定义 WAV 文件
-- 备选使用系统音效（Glass.aiff, Ping.aiff, Pop.aiff）
-
-### Linux
-- 优先使用 `paplay` 或 `aplay` 播放自定义 WAV 文件
-- 备选使用 `speaker-test` 生成不同频率提示音
-
-## 故障排除
-
-如果音频不工作：
-
-1. 检查系统音量设置
-2. 确保音频文件格式正确（WAV 格式）
-3. 运行 `dvcode --test-audio` 进行诊断
-4. 查看控制台调试信息
-5. 临时禁用音频通知继续使用
-
-## 音频文件建议
-
-- 文件大小：建议小于 100KB
-- 时长：建议 0.2-1 秒
-- 格式：WAV（16-bit PCM）
-- 音量：适中，避免过于刺耳

package/bundle/node_modules/undici/LICENSE

@@ -1,21 +0,0 @@
-MIT License
-
-Copyright (c) Matteo Collina and Undici contributors
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.

package/bundle/node_modules/undici/README.md

@@ -1,472 +0,0 @@
-# undici
-
-[![Node CI](https://github.com/nodejs/undici/actions/workflows/nodejs.yml/badge.svg)](https://github.com/nodejs/undici/actions/workflows/nodejs.yml) [![neostandard javascript style](https://img.shields.io/badge/neo-standard-7fffff?style=flat\&labelColor=ff80ff)](https://github.com/neostandard/neostandard) [![npm version](https://badge.fury.io/js/undici.svg)](https://badge.fury.io/js/undici) [![codecov](https://codecov.io/gh/nodejs/undici/branch/main/graph/badge.svg?token=yZL6LtXkOA)](https://codecov.io/gh/nodejs/undici)
-
-An HTTP/1.1 client, written from scratch for Node.js.
-
-> Undici means eleven in Italian. 1.1 -> 11 -> Eleven -> Undici.
-It is also a Stranger Things reference.
-
-## How to get involved
-
-Have a question about using Undici? Open a [Q&A Discussion](https://github.com/nodejs/undici/discussions/new) or join our official OpenJS [Slack](https://openjs-foundation.slack.com/archives/C01QF9Q31QD) channel.
-
-Looking to contribute? Start by reading the [contributing guide](./CONTRIBUTING.md)
-
-## Install
-
-```
-npm i undici
-```
-
-## Benchmarks
-
-The benchmark is a simple getting data [example](https://github.com/nodejs/undici/blob/main/benchmarks/benchmark.js) using a
-50 TCP connections with a pipelining depth of 10 running on Node 22.11.0.
-
-```
-┌────────────────────────┬─────────┬────────────────────┬────────────┬─────────────────────────┐
-│  Tests                 │ Samples │ Result             │ Tolerance  │ Difference with slowest │
-├────────────────────────┼─────────┼────────────────────┼────────────┼─────────────────────────┤
-│  'axios'               │ 15      │ '5708.26 req/sec'  │ '± 2.91 %' │ '-'                     │
-│  'http - no keepalive' │ 10      │ '5809.80 req/sec'  │ '± 2.30 %' │ '+ 1.78 %'              │
-│  'request'             │ 30      │ '5828.80 req/sec'  │ '± 2.91 %' │ '+ 2.11 %'              │
-│  'undici - fetch'      │ 40      │ '5903.78 req/sec'  │ '± 2.87 %' │ '+ 3.43 %'              │
-│  'node-fetch'          │ 10      │ '5945.40 req/sec'  │ '± 2.13 %' │ '+ 4.15 %'              │
-│  'got'                 │ 35      │ '6511.45 req/sec'  │ '± 2.84 %' │ '+ 14.07 %'             │
-│  'http - keepalive'    │ 65      │ '9193.24 req/sec'  │ '± 2.92 %' │ '+ 61.05 %'             │
-│  'superagent'          │ 35      │ '9339.43 req/sec'  │ '± 2.95 %' │ '+ 63.61 %'             │
-│  'undici - pipeline'   │ 50      │ '13364.62 req/sec' │ '± 2.93 %' │ '+ 134.13 %'            │
-│  'undici - stream'     │ 95      │ '18245.36 req/sec' │ '± 2.99 %' │ '+ 219.63 %'            │
-│  'undici - request'    │ 50      │ '18340.17 req/sec' │ '± 2.84 %' │ '+ 221.29 %'            │
-│  'undici - dispatch'   │ 40      │ '22234.42 req/sec' │ '± 2.94 %' │ '+ 289.51 %'            │
-└────────────────────────┴─────────┴────────────────────┴────────────┴─────────────────────────┘
-```
-
-## Quick Start
-
-```js
-import { request } from 'undici'
-
-const {
-  statusCode,
-  headers,
-  trailers,
-  body
-} = await request('http://localhost:3000/foo')
-
-console.log('response received', statusCode)
-console.log('headers', headers)
-
-for await (const data of body) { console.log('data', data) }
-
-console.log('trailers', trailers)
-```
-
-## Body Mixins
-
-The `body` mixins are the most common way to format the request/response body. Mixins include:
-
-- [`.arrayBuffer()`](https://fetch.spec.whatwg.org/#dom-body-arraybuffer)
-- [`.blob()`](https://fetch.spec.whatwg.org/#dom-body-blob)
-- [`.bytes()`](https://fetch.spec.whatwg.org/#dom-body-bytes)
-- [`.json()`](https://fetch.spec.whatwg.org/#dom-body-json)
-- [`.text()`](https://fetch.spec.whatwg.org/#dom-body-text)
-
-> [!NOTE]
-> The body returned from `undici.request` does not implement `.formData()`.
-
-Example usage:
-
-```js
-import { request } from 'undici'
-
-const {
-  statusCode,
-  headers,
-  trailers,
-  body
-} = await request('http://localhost:3000/foo')
-
-console.log('response received', statusCode)
-console.log('headers', headers)
-console.log('data', await body.json())
-console.log('trailers', trailers)
-```
-
-_Note: Once a mixin has been called then the body cannot be reused, thus calling additional mixins on `.body`, e.g. `.body.json(); .body.text()` will result in an error `TypeError: unusable` being thrown and returned through the `Promise` rejection._
-
-Should you need to access the `body` in plain-text after using a mixin, the best practice is to use the `.text()` mixin first and then manually parse the text to the desired format.
-
-For more information about their behavior, please reference the body mixin from the [Fetch Standard](https://fetch.spec.whatwg.org/#body-mixin).
-
-## Common API Methods
-
-This section documents our most commonly used API methods. Additional APIs are documented in their own files within the [docs](./docs/) folder and are accessible via the navigation list on the left side of the docs site.
-
-### `undici.request([url, options]): Promise`
-
-Arguments:
-
-* **url** `string | URL | UrlObject`
-* **options** [`RequestOptions`](./docs/docs/api/Dispatcher.md#parameter-requestoptions)
-  * **dispatcher** `Dispatcher` - Default: [getGlobalDispatcher](#undicigetglobaldispatcher)
-  * **method** `String` - Default: `PUT` if `options.body`, otherwise `GET`
-
-Returns a promise with the result of the `Dispatcher.request` method.
-
-Calls `options.dispatcher.request(options)`.
-
-See [Dispatcher.request](./docs/docs/api/Dispatcher.md#dispatcherrequestoptions-callback) for more details, and [request examples](./docs/examples/README.md) for examples.
-
-### `undici.stream([url, options, ]factory): Promise`
-
-Arguments:
-
-* **url** `string | URL | UrlObject`
-* **options** [`StreamOptions`](./docs/docs/api/Dispatcher.md#parameter-streamoptions)
-  * **dispatcher** `Dispatcher` - Default: [getGlobalDispatcher](#undicigetglobaldispatcher)
-  * **method** `String` - Default: `PUT` if `options.body`, otherwise `GET`
-* **factory** `Dispatcher.stream.factory`
-
-Returns a promise with the result of the `Dispatcher.stream` method.
-
-Calls `options.dispatcher.stream(options, factory)`.
-
-See [Dispatcher.stream](./docs/docs/api/Dispatcher.md#dispatcherstreamoptions-factory-callback) for more details.
-
-### `undici.pipeline([url, options, ]handler): Duplex`
-
-Arguments:
-
-* **url** `string | URL | UrlObject`
-* **options** [`PipelineOptions`](./docs/docs/api/Dispatcher.md#parameter-pipelineoptions)
-  * **dispatcher** `Dispatcher` - Default: [getGlobalDispatcher](#undicigetglobaldispatcher)
-  * **method** `String` - Default: `PUT` if `options.body`, otherwise `GET`
-* **handler** `Dispatcher.pipeline.handler`
-
-Returns: `stream.Duplex`
-
-Calls `options.dispatch.pipeline(options, handler)`.
-
-See [Dispatcher.pipeline](./docs/docs/api/Dispatcher.md#dispatcherpipelineoptions-handler) for more details.
-
-### `undici.connect([url, options]): Promise`
-
-Starts two-way communications with the requested resource using [HTTP CONNECT](https://developer.mozilla.org/en-US/docs/Web/HTTP/Methods/CONNECT).
-
-Arguments:
-
-* **url** `string | URL | UrlObject`
-* **options** [`ConnectOptions`](./docs/docs/api/Dispatcher.md#parameter-connectoptions)
-  * **dispatcher** `Dispatcher` - Default: [getGlobalDispatcher](#undicigetglobaldispatcher)
-* **callback** `(err: Error | null, data: ConnectData | null) => void` (optional)
-
-Returns a promise with the result of the `Dispatcher.connect` method.
-
-Calls `options.dispatch.connect(options)`.
-
-See [Dispatcher.connect](./docs/docs/api/Dispatcher.md#dispatcherconnectoptions-callback) for more details.
-
-### `undici.fetch(input[, init]): Promise`
-
-Implements [fetch](https://fetch.spec.whatwg.org/#fetch-method).
-
-* https://developer.mozilla.org/en-US/docs/Web/API/WindowOrWorkerGlobalScope/fetch
-* https://fetch.spec.whatwg.org/#fetch-method
-
-Basic usage example:
-
-```js
-import { fetch } from 'undici'
-
-
-const res = await fetch('https://example.com')
-const json = await res.json()
-console.log(json)
-```
-
-You can pass an optional dispatcher to `fetch` as:
-
-```js
-import { fetch, Agent } from 'undici'
-
-const res = await fetch('https://example.com', {
-  // Mocks are also supported
-  dispatcher: new Agent({
-    keepAliveTimeout: 10,
-    keepAliveMaxTimeout: 10
-  })
-})
-const json = await res.json()
-console.log(json)
-```
-
-#### `request.body`
-
-A body can be of the following types:
-
-- ArrayBuffer
-- ArrayBufferView
-- AsyncIterables
-- Blob
-- Iterables
-- String
-- URLSearchParams
-- FormData
-
-In this implementation of fetch, ```request.body``` now accepts ```Async Iterables```. It is not present in the [Fetch Standard](https://fetch.spec.whatwg.org).
-
-```js
-import { fetch } from 'undici'
-
-const data = {
-  async *[Symbol.asyncIterator]() {
-    yield 'hello'
-    yield 'world'
-  },
-}
-
-await fetch('https://example.com', { body: data, method: 'POST', duplex: 'half' })
-```
-
-[FormData](https://developer.mozilla.org/en-US/docs/Web/API/FormData) besides text data and buffers can also utilize streams via [Blob](https://developer.mozilla.org/en-US/docs/Web/API/Blob) objects:
-
-```js
-import { openAsBlob } from 'node:fs'
-
-const file = await openAsBlob('./big.csv')
-const body = new FormData()
-body.set('file', file, 'big.csv')
-
-await fetch('http://example.com', { method: 'POST', body })
-```
-
-#### `request.duplex`
-
-- `'half'`
-
-In this implementation of fetch, `request.duplex` must be set if `request.body` is `ReadableStream` or `Async Iterables`, however, even though the value must be set to `'half'`, it is actually a _full_ duplex. For more detail refer to the [Fetch Standard](https://fetch.spec.whatwg.org/#dom-requestinit-duplex).
-
-#### `response.body`
-
-Nodejs has two kinds of streams: [web streams](https://nodejs.org/api/webstreams.html), which follow the API of the WHATWG web standard found in browsers, and an older Node-specific [streams API](https://nodejs.org/api/stream.html). `response.body` returns a readable web stream. If you would prefer to work with a Node stream you can convert a web stream using `.fromWeb()`.
-
-```js
-import { fetch } from 'undici'
-import { Readable } from 'node:stream'
-
-const response = await fetch('https://example.com')
-const readableWebStream = response.body
-const readableNodeStream = Readable.fromWeb(readableWebStream)
-```
-
-## Specification Compliance
-
-This section documents parts of the [HTTP/1.1](https://www.rfc-editor.org/rfc/rfc9110.html) and [Fetch Standard](https://fetch.spec.whatwg.org) that Undici does
-not support or does not fully implement.
-
-#### CORS
-
-Unlike browsers, Undici does not implement CORS (Cross-Origin Resource Sharing) checks by default. This means:
-
-- No preflight requests are automatically sent for cross-origin requests
-- No validation of `Access-Control-Allow-Origin` headers is performed
-- Requests to any origin are allowed regardless of the source
-
-This behavior is intentional for server-side environments where CORS restrictions are typically unnecessary. If your application requires CORS-like protections, you will need to implement these checks manually.
-
-#### Garbage Collection
-
-* https://fetch.spec.whatwg.org/#garbage-collection
-
-The [Fetch Standard](https://fetch.spec.whatwg.org) allows users to skip consuming the response body by relying on
-[garbage collection](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Memory_Management#garbage_collection) to release connection resources. Undici does not do the same. Therefore, it is important to always either consume or cancel the response body.
-
-Garbage collection in Node is less aggressive and deterministic
-(due to the lack of clear idle periods that browsers have through the rendering refresh rate)
-which means that leaving the release of connection resources to the garbage collector can lead
-to excessive connection usage, reduced performance (due to less connection re-use), and even
-stalls or deadlocks when running out of connections.
-
-```js
-// Do
-const { body, headers } = await fetch(url);
-for await (const chunk of body) {
-  // force consumption of body
-}
-
-// Do not
-const { headers } = await fetch(url);
-```
-
-The same applies for `request` too:
-```js
-// Do
-const { body, headers } = await request(url);
-await res.body.dump(); // force consumption of body
-
-// Do not
-const { headers } = await request(url);
-```
-
-However, if you want to get only headers, it might be better to use `HEAD` request method. Usage of this method will obviate the need for consumption or cancelling of the response body. See [MDN - HTTP - HTTP request methods - HEAD](https://developer.mozilla.org/en-US/docs/Web/HTTP/Methods/HEAD) for more details.
-
-```js
-const headers = await fetch(url, { method: 'HEAD' })
-  .then(res => res.headers)
-```
-
-#### Forbidden and Safelisted Header Names
-
-* https://fetch.spec.whatwg.org/#cors-safelisted-response-header-name
-* https://fetch.spec.whatwg.org/#forbidden-header-name
-* https://fetch.spec.whatwg.org/#forbidden-response-header-name
-* https://github.com/wintercg/fetch/issues/6
-
-The [Fetch Standard](https://fetch.spec.whatwg.org) requires implementations to exclude certain headers from requests and responses. In browser environments, some headers are forbidden so the user agent remains in full control over them. In Undici, these constraints are removed to give more control to the user.
-
-#### `undici.upgrade([url, options]): Promise`
-
-Upgrade to a different protocol. See [MDN - HTTP - Protocol upgrade mechanism](https://developer.mozilla.org/en-US/docs/Web/HTTP/Protocol_upgrade_mechanism) for more details.
-
-Arguments:
-
-* **url** `string | URL | UrlObject`
-* **options** [`UpgradeOptions`](./docs/docs/api/Dispatcher.md#parameter-upgradeoptions)
-  * **dispatcher** `Dispatcher` - Default: [getGlobalDispatcher](#undicigetglobaldispatcher)
-* **callback** `(error: Error | null, data: UpgradeData) => void` (optional)
-
-Returns a promise with the result of the `Dispatcher.upgrade` method.
-
-Calls `options.dispatcher.upgrade(options)`.
-
-See [Dispatcher.upgrade](./docs/docs/api/Dispatcher.md#dispatcherupgradeoptions-callback) for more details.
-
-### `undici.setGlobalDispatcher(dispatcher)`
-
-* dispatcher `Dispatcher`
-
-Sets the global dispatcher used by Common API Methods. Global dispatcher is shared among compatible undici modules,
-including undici that is bundled internally with node.js.
-
-### `undici.getGlobalDispatcher()`
-
-Gets the global dispatcher used by Common API Methods.
-
-Returns: `Dispatcher`
-
-### `undici.setGlobalOrigin(origin)`
-
-* origin `string | URL | undefined`
-
-Sets the global origin used in `fetch`.
-
-If `undefined` is passed, the global origin will be reset. This will cause `Response.redirect`, `new Request()`, and `fetch` to throw an error when a relative path is passed.
-
-```js
-setGlobalOrigin('http://localhost:3000')
-
-const response = await fetch('/api/ping')
-
-console.log(response.url) // http://localhost:3000/api/ping
-```
-
-### `undici.getGlobalOrigin()`
-
-Gets the global origin used in `fetch`.
-
-Returns: `URL`
-
-### `UrlObject`
-
-* **port** `string | number` (optional)
-* **path** `string` (optional)
-* **pathname** `string` (optional)
-* **hostname** `string` (optional)
-* **origin** `string` (optional)
-* **protocol** `string` (optional)
-* **search** `string` (optional)
-
-#### Expect
-
-Undici does not support the `Expect` request header field. The request
-body is  always immediately sent and the `100 Continue` response will be
-ignored.
-
-Refs: https://tools.ietf.org/html/rfc7231#section-5.1.1
-
-#### Pipelining
-
-Undici will only use pipelining if configured with a `pipelining` factor
-greater than `1`. Also it is important to pass `blocking: false` to the
-request options to properly pipeline requests.
-
-Undici always assumes that connections are persistent and will immediately
-pipeline requests, without checking whether the connection is persistent.
-Hence, automatic fallback to HTTP/1.0 or HTTP/1.1 without pipelining is
-not supported.
-
-Undici will immediately pipeline when retrying requests after a failed
-connection. However, Undici will not retry the first remaining requests in
-the prior pipeline and instead error the corresponding callback/promise/stream.
-
-Undici will abort all running requests in the pipeline when any of them are
-aborted.
-
-* Refs: https://tools.ietf.org/html/rfc2616#section-8.1.2.2
-* Refs: https://tools.ietf.org/html/rfc7230#section-6.3.2
-
-#### Manual Redirect
-
-Since it is not possible to manually follow an HTTP redirect on the server-side,
-Undici returns the actual response instead of an `opaqueredirect` filtered one
-when invoked with a `manual` redirect. This aligns `fetch()` with the other
-implementations in Deno and Cloudflare Workers.
-
-Refs: https://fetch.spec.whatwg.org/#atomic-http-redirect-handling
-
-### Workarounds
-
-#### Network address family autoselection.
-
-If you experience problem when connecting to a remote server that is resolved by your DNS servers to a IPv6 (AAAA record)
-first, there are chances that your local router or ISP might have problem connecting to IPv6 networks. In that case
-undici will throw an error with code `UND_ERR_CONNECT_TIMEOUT`.
-
-If the target server resolves to both a IPv6 and IPv4 (A records) address and you are using a compatible Node version
-(18.3.0 and above), you can fix the problem by providing the `autoSelectFamily` option (support by both `undici.request`
-and `undici.Agent`) which will enable the family autoselection algorithm when establishing the connection.
-
-## Collaborators
-
-* [__Daniele Belardi__](https://github.com/dnlup), <https://www.npmjs.com/~dnlup>
-* [__Ethan Arrowood__](https://github.com/ethan-arrowood), <https://www.npmjs.com/~ethan_arrowood>
-* [__Matteo Collina__](https://github.com/mcollina), <https://www.npmjs.com/~matteo.collina>
-* [__Matthew Aitken__](https://github.com/KhafraDev), <https://www.npmjs.com/~khaf>
-* [__Robert Nagy__](https://github.com/ronag), <https://www.npmjs.com/~ronag>
-* [__Szymon Marczak__](https://github.com/szmarczak), <https://www.npmjs.com/~szmarczak>
-
-## Past Collaborators
-* [__Tomas Della Vedova__](https://github.com/delvedor), <https://www.npmjs.com/~delvedor>
-
-### Releasers
-
-* [__Ethan Arrowood__](https://github.com/ethan-arrowood), <https://www.npmjs.com/~ethan_arrowood>
-* [__Matteo Collina__](https://github.com/mcollina), <https://www.npmjs.com/~matteo.collina>
-* [__Robert Nagy__](https://github.com/ronag), <https://www.npmjs.com/~ronag>
-* [__Matthew Aitken__](https://github.com/KhafraDev), <https://www.npmjs.com/~khaf>
-
-## Long Term Support
-
-Undici aligns with the Node.js LTS schedule. The following table shows the supported versions:
-
-| Version | Node.js     | End of Life |
-|---------|-------------|-------------|
-| 5.x     | v18.x       | 2024-04-30  |
-| 6.x     | v20.x v22.x | 2026-04-30  |
-| 7.x     | v24.x       | 2027-04-30  |
-
-## License
-
-MIT