@saifymatteo/pi-x-ide 0.0.0-stage → 1.20.1

package/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+1.  Definitions.
+
+    "License" shall mean the terms and conditions for use, reproduction,
+    and distribution as defined by Sections 1 through 9 of this document.
+
+    "Licensor" shall mean the copyright owner or entity authorized by
+    the copyright owner that is granting the License.
+
+    "Legal Entity" shall mean the union of the acting entity and all
+    other entities that control, are controlled by, or are under common
+    control with that entity. For the purposes of this definition,
+    "control" means (i) the power, direct or indirect, to cause the
+    direction or management of such entity, whether by contract or
+    otherwise, or (ii) ownership of fifty percent (50%) or more of the
+    outstanding shares, or (iii) beneficial ownership of such entity.
+
+    "You" (or "Your") shall mean an individual or Legal Entity
+    exercising permissions granted by this License.
+
+    "Source" form shall mean the preferred form for making modifications,
+    including but not limited to software source code, documentation
+    source, and configuration files.
+
+    "Object" form shall mean any form resulting from mechanical
+    transformation or translation of a Source form, including but
+    not limited to compiled object code, generated documentation,
+    and conversions to other media types.
+
+    "Work" shall mean the work of authorship, whether in Source or
+    Object form, made available under the License, as indicated by a
+    copyright notice that is included in or attached to the work
+    (an example is provided in the Appendix below).
+
+    "Derivative Works" shall mean any work, whether in Source or Object
+    form, that is based on (or derived from) the Work and for which the
+    editorial revisions, annotations, elaborations, or other modifications
+    represent, as a whole, an original work of authorship. For the purposes
+    of this License, Derivative Works shall not include works that remain
+    separable from, or merely link (or bind by name) to the interfaces of,
+    the Work and Derivative Works thereof.
+
+    "Contribution" shall mean any work of authorship, including
+    the original version of the Work and any modifications or additions
+    to that Work or Derivative Works thereof, that is intentionally
+    submitted to Licensor for inclusion in the Work by the copyright owner
+    or by an individual or Legal Entity authorized to submit on behalf of
+    the copyright owner. For the purposes of this definition, "submitted"
+    means any form of electronic, verbal, or written communication sent
+    to the Licensor or its representatives, including but not limited to
+    communication on electronic mailing lists, source code control systems,
+    and issue tracking systems that are managed by, or on behalf of, the
+    Licensor for the purpose of discussing and improving the Work, but
+    excluding communication that is conspicuously marked or otherwise
+    designated in writing by the copyright owner as "Not a Contribution."
+
+    "Contributor" shall mean Licensor and any individual or Legal Entity
+    on behalf of whom a Contribution has been received by Licensor and
+    subsequently incorporated within the Work.
+
+2.  Grant of Copyright License. Subject to the terms and conditions of
+    this License, each Contributor hereby grants to You a perpetual,
+    worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+    copyright license to reproduce, prepare Derivative Works of,
+    publicly display, publicly perform, sublicense, and distribute the
+    Work and such Derivative Works in Source or Object form.
+
+3.  Grant of Patent License. Subject to the terms and conditions of
+    this License, each Contributor hereby grants to You a perpetual,
+    worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+    (except as stated in this section) patent license to make, have made,
+    use, offer to sell, sell, import, and otherwise transfer the Work,
+    where such license applies only to those patent claims licensable
+    by such Contributor that are necessarily infringed by their
+    Contribution(s) alone or by combination of their Contribution(s)
+    with the Work to which such Contribution(s) was submitted. If You
+    institute patent litigation against any entity (including a
+    cross-claim or counterclaim in a lawsuit) alleging that the Work
+    or a Contribution incorporated within the Work constitutes direct
+    or contributory patent infringement, then any patent licenses
+    granted to You under this License for that Work shall terminate
+    as of the date such litigation is filed.
+
+4.  Redistribution. You may reproduce and distribute copies of the
+    Work or Derivative Works thereof in any medium, with or without
+    modifications, and in Source or Object form, provided that You
+    meet the following conditions:
+
+    (a) You must give any other recipients of the Work or
+    Derivative Works a copy of this License; and
+
+    (b) You must cause any modified files to carry prominent notices
+    stating that You changed the files; and
+
+    (c) You must retain, in the Source form of any Derivative Works
+    that You distribute, all copyright, patent, trademark, and
+    attribution notices from the Source form of the Work,
+    excluding those notices that do not pertain to any part of
+    the Derivative Works; and
+
+    (d) If the Work includes a "NOTICE" text file as part of its
+    distribution, then any Derivative Works that You distribute must
+    include a readable copy of the attribution notices contained
+    within such NOTICE file, excluding those notices that do not
+    pertain to any part of the Derivative Works, in at least one
+    of the following places: within a NOTICE text file distributed
+    as part of the Derivative Works; within the Source form or
+    documentation, if provided along with the Derivative Works; or,
+    within a display generated by the Derivative Works, if and
+    wherever such third-party notices normally appear. The contents
+    of the NOTICE file are for informational purposes only and
+    do not modify the License. You may add Your own attribution
+    notices within Derivative Works that You distribute, alongside
+    or as an addendum to the NOTICE text from the Work, provided
+    that such additional attribution notices cannot be construed
+    as modifying the License.
+
+    You may add Your own copyright statement to Your modifications and
+    may provide additional or different license terms and conditions
+    for use, reproduction, or distribution of Your modifications, or
+    for any such Derivative Works as a whole, provided Your use,
+    reproduction, and distribution of the Work otherwise complies with
+    the conditions stated in this License.
+
+5.  Submission of Contributions. Unless You explicitly state otherwise,
+    any Contribution intentionally submitted for inclusion in the Work
+    by You to the Licensor shall be under the terms and conditions of
+    this License, without any additional terms or conditions.
+    Notwithstanding the above, nothing herein shall supersede or modify
+    the terms of any separate license agreement you may have executed
+    with Licensor regarding such Contributions.
+
+6.  Trademarks. This License does not grant permission to use the trade
+    names, trademarks, service marks, or product names of the Licensor,
+    except as required for reasonable and customary use in describing the
+    origin of the Work and reproducing the content of the NOTICE file.
+
+7.  Disclaimer of Warranty. Unless required by applicable law or
+    agreed to in writing, Licensor provides the Work (and each
+    Contributor provides its Contributions) on an "AS IS" BASIS,
+    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+    implied, including, without limitation, any warranties or conditions
+    of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+    PARTICULAR PURPOSE. You are solely responsible for determining the
+    appropriateness of using or redistributing the Work and assume any
+    risks associated with Your exercise of permissions under this License.
+
+8.  Limitation of Liability. In no event and under no legal theory,
+    whether in tort (including negligence), contract, or otherwise,
+    unless required by applicable law (such as deliberate and grossly
+    negligent acts) or agreed to in writing, shall any Contributor be
+    liable to You for damages, including any direct, indirect, special,
+    incidental, or consequential damages of any character arising as a
+    result of this License or out of the use or inability to use the
+    Work (including but not limited to damages for loss of goodwill,
+    work stoppage, computer failure or malfunction, or any and all
+    other commercial damages or losses), even if such Contributor
+    has been advised of the possibility of such damages.
+
+9.  Accepting Warranty or Additional Liability. While redistributing
+    the Work or Derivative Works thereof, You may choose to offer,
+    and charge a fee for, acceptance of support, warranty, indemnity,
+    or other liability obligations and/or rights consistent with this
+    License. However, in accepting such obligations, You may act only
+    on Your own behalf and on Your sole responsibility, not on behalf
+    of any other Contributor, and only if You agree to indemnify,
+    defend, and hold each Contributor harmless for any liability
+    incurred by, or claims asserted against, such Contributor by reason
+    of your accepting any such warranty or additional liability.
+
+END OF TERMS AND CONDITIONS
+
+APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+Copyright [yyyy] [name of copyright owner]
+
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.

package/README.md

@@ -1,3 +1,34 @@
-# Temporary Holding Version
+# Pi × IDE — Saifymatteo fork
 
-This version is a temporary placeholder for this package. An operational version to replace this has been submitted for review and is awaiting a staged release.
+**English** | [简体中文](README.zh-CN.md)
+
+This is [@saifymatteo/pi-x-ide](https://github.com/saifymatteo/pi-x-ide), a fork of [@balaenis/pi-x-ide](https://github.com/balaenis/pi-x-ide).
+
+For the original project overview, supported IDEs, installation instructions, and general documentation, see the [upstream README](https://github.com/balaenis/pi-x-ide#readme).
+
+## Changes in this fork
+
+When IDE context is attached to a prompt, Pi displays it as a separate purple **IDE Context** message. The message contains the IDE name, file path, and—when available—the selected line range. It does not include selected source contents, so the agent can inspect the file itself when it needs more context. Your prompt remains unchanged.
+
+For example:
+
+```text
+### IDE Context
+- **IDE**: vscode
+- **File**: `src/main.ts`
+- **Selection**: L10-L20
+```
+
+When no text is selected, the selection line is omitted. For open-file-only context, the message includes the file metadata without attaching its contents.
+
+## Documentation
+
+- [Get started](docs/tutorials/get-started.md)
+- [Configuration](docs/reference/configuration.md)
+- [Architecture](docs/explanation/architecture.md)
+
+See [CONTRIBUTING.md](CONTRIBUTING.md) for development instructions.
+
+## License
+
+This fork retains the upstream [Apache-2.0 license](LICENSE).

package/README.zh-CN.md

@@ -0,0 +1,34 @@
+# Pi × IDE — Saifymatteo 分支
+
+[English](README.md) | **简体中文**
+
+这是 [@saifymatteo/pi-x-ide](https://github.com/saifymatteo/pi-x-ide)，基于 [@balaenis/pi-x-ide](https://github.com/balaenis/pi-x-ide) 的分支。
+
+有关上游项目的介绍、支持的 IDE、安装说明和通用文档，请参阅[上游 README](https://github.com/balaenis/pi-x-ide#readme)。
+
+## 此分支的更改
+
+将 IDE 上下文附加到提示时，Pi 会将其显示为单独的紫色 **IDE Context** 消息。消息包含 IDE 名称、文件路径，以及（如果有）所选行范围。消息不会包含选中的源代码，因此代理可以在需要更多上下文时自行读取文件。用户提示保持不变。
+
+例如：
+
+```text
+### IDE Context
+- **IDE**: vscode
+- **File**: `src/main.ts`
+- **Selection**: L10-L20
+```
+
+未选择文本时会省略选区行。仅附加当前打开文件时，消息包含文件元数据，不会附加文件内容。
+
+## 文档
+
+- [入门指南](docs/zh-CN/tutorials/get-started.md)
+- [配置](docs/zh-CN/reference/configuration.md)
+- [架构](docs/zh-CN/explanation/architecture.md)
+
+开发说明请参阅 [CONTRIBUTING.zh-CN.md](CONTRIBUTING.zh-CN.md)。
+
+## 许可证
+
+此分支沿用上游的 [Apache-2.0 许可证](LICENSE)。

package/RELEASE.md

@@ -0,0 +1,213 @@
+# Release Process
+
+This project uses [Release Please](https://github.com/googleapis/release-please) for automated releases.
+
+It follows two release channels:
+
+- **Pre-release**: Normal PRs merged to `main` create `x.x.x-next.N` versions published to the `next` npm dist-tag for testing and feedback.
+- **Stable Releases**: Release PRs merged to `main` create computed versions and publish to the `latest` npm dist-tag.
+
+You can also trigger manual releases in the following ways:
+
+- Push a tag in the format `v{semver}` (e.g. `v1.2.3`)
+- Run the `publish.yml` workflow manually from the GitHub Actions tab and supply a channel `latest` or `next`.
+
+## First Release
+
+Before automated releases will work, you need to perform the first release manually.
+
+Why:
+
+- The first release creates the npm package on npmjs.com.
+- This then allows you to set up trusted publishing with GitHub Actions for future releases.
+
+### Steps
+
+1. Make sure the `package.json` is correct:
+   - Is the `version` correct?
+   - Is the package name correct?
+   - Do you have the right `keywords`?
+   - Do you have the right `repository` field?
+   - Do you have the right `author` field?
+
+2. Run `bunx npm login` to authenticate with npm.
+
+3. Run `mise run build` to build the package.
+
+4. Run `bun publish --access public` to publish the first version.
+
+5. Go to your npm package settings on npmjs.com and add a trusted publisher for GitHub Actions with:
+   - **Organization or user**: Your GitHub username/org
+   - **Repository**: Your repository name
+   - **Workflow filename**: `publish.yml` (the publish workflow filename)
+
+6. [Restrict token access](https://docs.npmjs.com/trusted-publishers#recommended-restrict-token-access-when-using-trusted-publishers) for maximum security.
+
+## Release Workflow
+
+### Conventional Commits
+
+We follow [Conventional Commits](https://www.conventionalcommits.org/) specification:
+
+- `fix:` patches
+- `feat:` minor features
+- `feat!:` or `fix!:` breaking changes
+
+### Pre-1.0 Versioning
+
+While the version is `0.x.x`, breaking changes bump the **minor** version.
+
+### Release Process
+
+1. Push commits to the `main` branch
+2. Release Please will:
+   - Analyze commits
+   - Determine version bump
+   - Update `package.json`
+   - Update `CHANGELOG.md`
+   - Create a release PR
+
+3. Review and merge the Release Please PR
+
+### Commit Message Examples
+
+- `fix: resolve IDE connection timeout`
+- `feat: add VS Code workspace trust support`
+- `feat!: change extension activation API`
+- `docs: improve README`
+- `chore: update dependencies`
+
+## Advanced Release Features
+
+### Force a Specific Version
+
+Use the `Release-As` footer in your commit message to force a specific version, bypassing conventional commit analysis:
+
+```bash
+git commit --allow-empty -m "chore: release 2.0.0" -m "Release-As: 2.0.0"
+```
+
+This creates a commit:
+
+```
+chore: release 2.0.0
+
+Release-As: 2.0.0
+```
+
+Release Please will open a PR for version `2.0.0` regardless of commit message types.
+
+### Update Extra Files During Release
+
+If you have version numbers in other files beyond `package.json`, configure them in `release-please-config.json`:
+
+```json
+{
+  "extra-files": [
+    "src/version.ts",
+    {
+      "type": "generic",
+      "path": "docs/VERSION.md"
+    },
+    {
+      "type": "json",
+      "path": "ide-plugins/vscode/package.json",
+      "jsonpath": "$.version"
+    }
+  ]
+}
+```
+
+**Supported file types:**
+
+- Generic files (any type)
+- JSON files (with JSONPath)
+- YAML files (with JSONPath)
+- XML files (with XPath)
+- TOML files (with JSONPath)
+
+### Magic Comments for Version Markers
+
+Use inline comments to mark where versions should be updated:
+
+```javascript
+// x-release-please-version
+const VERSION = "1.0.0";
+
+// x-release-please-major
+const MAJOR = "1";
+```
+
+Or use block markers:
+
+```markdown
+<!-- x-release-please-start-version -->
+
+- Current version: 1.0.0
+<!-- x-release-please-end -->
+```
+
+Available markers:
+
+- `x-release-please-version` - Full semver
+- `x-release-please-major` - Major number
+- `x-release-please-minor` - Minor number
+- `x-release-please-patch` - Patch number
+
+## Do Not
+
+- Manually edit Release Please PRs
+- Manually create GitHub releases
+- Modify version numbers directly
+
+## Publishing
+
+Releases are automatically published to npm when the Release Please PR is merged.
+
+### NPM Trusted Publishing
+
+This project supports [NPM Trusted Publishing](https://docs.npmjs.com/trusted-publishers) with GitHub Actions. No npm tokens are needed — authentication is handled automatically via OIDC (OpenID Connect).
+
+**How it works:**
+
+- Each publish uses short-lived, cryptographically-signed tokens specific to your workflow
+- Tokens cannot be extracted or reused
+- No need to manage or rotate long-lived credentials
+
+**Setup required:**
+
+1. Go to your npm package settings on npmjs.com
+2. Add a trusted publisher for GitHub Actions with:
+   - **Organization or user**: Your GitHub username/org
+   - **Repository**: Your repository name
+   - **Workflow filename**: `publish.yml` (the publish workflow filename)
+3. Optionally, [restrict token access](https://docs.npmjs.com/trusted-publishers#recommended-restrict-token-access-when-using-trusted-publishers) for maximum security
+
+When you merge a release PR, the GitHub Actions workflow will automatically:
+
+1. Build the package
+2. Publish to npm with OIDC authentication
+3. Create a GitHub release
+
+### Manual Releases
+
+You can also manually trigger a release by pushing a tag in the format `v{semver}`:
+
+```bash
+git tag v1.2.3
+git push origin v1.2.3
+```
+
+This will:
+
+1. Trigger the release workflow
+2. Build and publish to npm
+3. Create a GitHub release
+
+Use manual releases for:
+
+- Hot-fixes outside the normal release cycle
+- Bypassing Release Please when needed
+- Direct version control over releases
+
+**Learn more:** See the [NPM Trusted Publishing documentation](https://docs.npmjs.com/trusted-publishers) for complete setup and best practices.

package/config.example.json

@@ -0,0 +1,9 @@
+{
+  "$schema": "https://raw.githubusercontent.com/saifymatteo/pi-x-ide/refs/heads/main/schemas/config.json",
+  "fixPrompt": "Analyze the errors and warnings at the following location, and try to fix them:\n{DIAGNOSTIC}",
+  "status_display": "widget",
+  "env": {
+    "PI_X_IDE_AUTO_INSTALL": "1",
+    "PI_X_IDE_ATTACH_SHORTCUT": "ctrl+alt+k"
+  }
+}

package/dist/src/pi/chunks/chunk-4RHJAL4S.js

@@ -0,0 +1,200 @@
+import { createRequire as __piCreateRequire } from "node:module";const require = __piCreateRequire(import.meta.url);
+import {
+  errorMessage,
+  formatExtensionError,
+  isStaleContextError,
+  logExtensionError,
+  readPiConfigFixPrompt,
+  safeRun,
+  safeRunAsync,
+  setExtensionErrorReporter,
+  snapshotKey,
+  updateIdeUi
+} from "./chunk-UUXVCTOS.js";
+
+// src/pi/safety.ts
+function deliverPiError(scope, error, ctx) {
+  try {
+    if (!ctx?.hasUI) return false;
+    ctx.ui.notify(formatExtensionError(scope, error), "error");
+    return true;
+  } catch {
+    return false;
+  }
+}
+function flushPendingPiErrors(runtime) {
+  if (runtime.pendingExtensionErrors.length === 0) return;
+  const pending = runtime.pendingExtensionErrors;
+  runtime.pendingExtensionErrors = [];
+  for (const item of pending) {
+    if (isStaleContextError(item.error)) continue;
+    if (!deliverPiError(item.scope, item.error, runtime.ctx)) {
+      runtime.pendingExtensionErrors.push(item);
+    }
+  }
+}
+function bindPiUiContext(runtime, ctx) {
+  runtime.ctx = ctx;
+  flushPendingPiErrors(runtime);
+}
+function reportPiExtensionError(runtime, scope, error) {
+  if (isStaleContextError(error)) return;
+  if (deliverPiError(scope, error, runtime.ctx)) return;
+  runtime.pendingExtensionErrors.push({ scope, error });
+}
+function installPiErrorReporter(runtime) {
+  setExtensionErrorReporter((scope, error) => {
+    reportPiExtensionError(runtime, scope, error);
+  });
+}
+function containPiError(runtime, scope, error, ctx = runtime.ctx) {
+  if (ctx) bindPiUiContext(runtime, ctx);
+  logExtensionError(scope, error);
+  runtime.connectionStatus = "error";
+  runtime.connectionMessage = `${scope}: ${errorMessage(error)}`;
+  safeRun(`${scope} update UI after error`, () => updateIdeUi(runtime, ctx ?? runtime.ctx));
+}
+function runPiBoundary(scope, runtime, action, ctx) {
+  return safeRun(scope, action, (error) => containPiError(runtime, scope, error, ctx));
+}
+async function runPiBoundaryAsync(scope, runtime, action, ctx) {
+  return safeRunAsync(scope, action, (error) => containPiError(runtime, scope, error, ctx));
+}
+
+// src/pi/diagnostic-types.ts
+var DIAGNOSTIC_FIX_CUSTOM_TYPE = "pi-x-ide/diagnostic-fix";
+
+// src/pi/diagnostics.ts
+var DIAGNOSTIC_CONTEXT_MARKER = "pi-x-ide/diagnostic-context";
+function buildDiagnosticFixPrompt(params, options = {}) {
+  const context = buildDiagnosticContextMessage(params);
+  const template = options.fixPrompt;
+  if (!template) {
+    return `Analyze the errors and warnings at the following location, and try to fix them:
+${context}`;
+  }
+  if (template.includes("{DIAGNOSTIC}")) {
+    return template.replaceAll("{DIAGNOSTIC}", context);
+  }
+  return `${template}
+${context}`;
+}
+function buildDiagnosticContextMessage(params) {
+  return `<!-- ${DIAGNOSTIC_CONTEXT_MARKER} -->
+${formatDiagnosticContext(params)}
+<!-- ${DIAGNOSTIC_CONTEXT_MARKER} -->
+`;
+}
+function formatDiagnosticContext(params) {
+  const filePath = params.filePath;
+  const lines = [`File: ${filePath}`, `Source: ${params.source}`];
+  if (params.documentVersion !== void 0) lines.push(`Document version: ${params.documentVersion}`);
+  lines.push(`Trigger range: ${formatRange(params.triggerRange)}`);
+  for (const [index, diagnostic] of params.diagnostics.entries()) {
+    lines.push("", `Diagnostic ${index + 1}:`);
+    lines.push(`- Severity: ${diagnostic.severity}`);
+    if (diagnostic.source) lines.push(`- Source: ${diagnostic.source}`);
+    if (diagnostic.code !== void 0) lines.push(`- Code: ${formatDiagnosticCode(diagnostic.code)}`);
+    lines.push(`- Range: ${formatRange(diagnostic.range)}`);
+    lines.push(`- Message: ${diagnostic.message}`);
+    if (diagnostic.selectedText.length > 0) {
+      lines.push("- Selected text:", fence(diagnostic.selectedText));
+    }
+    if (diagnostic.contextLines.length > 0) {
+      lines.push("- Context lines:");
+      for (const contextLine of diagnostic.contextLines) {
+        const marker = contextLine.isPrimary ? "\\>" : " ";
+        lines.push(`  ${marker} ${contextLine.line + 1}: ${contextLine.text}`);
+      }
+    }
+    if (diagnostic.relatedInformation && diagnostic.relatedInformation.length > 0) {
+      lines.push("- Related information:");
+      for (const related of diagnostic.relatedInformation) {
+        const relatedPath = related.filePath;
+        lines.push(`  - ${relatedPath} ${formatRange(related.range)}: ${related.message}`);
+      }
+    }
+  }
+  return lines.join("\n");
+}
+function handleDiagnosticFixRequested(pi, runtime, params) {
+  const ctx = runtime.ctx;
+  if (!ctx) return;
+  if (params.action === "send-diagnostic") {
+    if (!ctx.hasUI) return;
+    ctx.ui.pasteToEditor(buildDiagnosticContextMessage(params));
+    ctx.ui.notify("VS Code diagnostic context added to input.", "info");
+    return;
+  }
+  const fixPrompt = readPiConfigFixPrompt();
+  const prompt = buildDiagnosticFixPrompt(params, { fixPrompt });
+  const details = {
+    source: params.source,
+    filePath: params.filePath,
+    workspaceFolder: params.workspaceFolder,
+    triggerRange: params.triggerRange,
+    diagnostics: params.diagnostics,
+    cwd: ctx.cwd
+  };
+  pi.sendMessage(
+    {
+      customType: DIAGNOSTIC_FIX_CUSTOM_TYPE,
+      content: prompt,
+      display: true,
+      details
+    },
+    { triggerTurn: true, deliverAs: "followUp" }
+  );
+  if (!ctx.isIdle() && ctx.hasUI) ctx.ui.notify("VS Code diagnostic fix request queued.", "info");
+}
+function formatRange(range) {
+  const start = formatPosition(range.start);
+  const end = formatPosition(range.end);
+  return start === end ? start : `${start}-${end}`;
+}
+function formatPosition(position) {
+  return `L${position.line + 1}:C${position.character + 1}`;
+}
+function formatDiagnosticCode(code) {
+  if (typeof code === "string" || typeof code === "number") return String(code);
+  return code.target ? `${code.value} (${code.target})` : String(code.value);
+}
+function fence(text) {
+  const fenceMarker = text.includes("```") ? "````" : "```";
+  return `${fenceMarker}
+${text}
+${fenceMarker}`;
+}
+
+// src/pi/selection.ts
+function setLatestSelection(runtime, snapshot, ctx) {
+  const key = snapshotKey(snapshot);
+  runtime.latestSelection = snapshot;
+  if (runtime.latestSelectionKey !== key) {
+    runtime.latestSelectionKey = key;
+    runtime.attachState = "pending";
+  }
+  updateIdeUi(runtime, ctx);
+}
+function clearLatestSelection(runtime, ctx) {
+  runtime.latestSelection = void 0;
+  runtime.latestSelectionKey = void 0;
+  runtime.turnSelection = void 0;
+  runtime.attachState = "idle";
+  updateIdeUi(runtime, ctx);
+}
+
+export {
+  bindPiUiContext,
+  installPiErrorReporter,
+  containPiError,
+  runPiBoundary,
+  runPiBoundaryAsync,
+  DIAGNOSTIC_FIX_CUSTOM_TYPE,
+  DIAGNOSTIC_CONTEXT_MARKER,
+  handleDiagnosticFixRequested,
+  formatRange,
+  formatDiagnosticCode,
+  setLatestSelection,
+  clearLatestSelection
+};