pi-gortex 0.1.0

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 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 2026 Andrey Kumanyaev <me@zzet.org>
+
+   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

@@ -0,0 +1,102 @@
+# pi-gortex
+
+A [Pi](https://github.com/earendil-works/pi) extension that gives the agent
+[Gortex](https://github.com/zzet/gortex)'s code-graph tools, and applies
+Gortex's read-discipline decisions to Pi's own tools.
+
+### What is Gortex?
+
+A code-intelligence engine that indexes your repositories into a queryable
+knowledge graph of functions, classes, call chains, routes and cross-service
+contracts, and serves it over MCP. Agents look up exactly the symbol they
+need instead of reading whole files around it, which is where the token
+savings come from. It is a single static binary with no dependency chain,
+and it covers 257 languages through tree-sitter.
+
+Pi has no MCP support by design, so this extension is the bridge.
+
+## What it does
+
+- **Registers Gortex's graph tools as native Pi tools**, over a persistent
+  `gortex mcp` child per session. The deferred catalogue is reached through the
+  daemon's own `tools_search`, and promoted tools appear in Pi's registry.
+- **Applies read discipline.** Pi's tool calls are forwarded to
+  `gortex hook --agent=pi`, which answers block / soft guidance / nothing
+  according to the posture you configured. Gortex owns that logic, so the
+  behaviour matches every other agent it integrates with.
+- **Briefs the model once per session** with Gortex's orientation for the
+  current repository.
+
+See [docs/architecture.md](docs/architecture.md) for how it works.
+
+## Requirements
+
+- **Node 24+**, **Pi 0.85+**
+- **The `gortex` binary** on `PATH`, **v0.61.2 or newer**. See
+  [Gortex installation](https://github.com/zzet/gortex/blob/main/docs/installation.md).
+  The extension starts the shared daemon itself and never blocks Pi's startup
+  on it, and warns you at session start when the binary is older than that.
+  Run `gortex upgrade` to fix it.
+
+## Install
+
+Add it to Pi's settings, `~/.pi/agent/settings.json` for every project or
+`<project>/.pi/settings.json` for one:
+
+```json
+{
+  "packages": ["npm:pi-gortex"]
+}
+```
+
+Leave the spec unpinned: Pi skips pinned specs during `pi update`.
+
+For local development, point Pi at a checkout instead: a `packages` entry with
+the absolute path, or a single run with `pi -e /path/to/pi-gortex`.
+
+## Configure
+
+Zero configuration required. Every value resolves at runtime, first hit wins:
+environment -> `<cwd>/.pi/gortex.json` -> `<agent dir>/extensions/gortex.json`
+(agent dir is `$PI_CODING_AGENT_DIR`, else `~/.pi/agent`) -> defaults.
+
+| Sidecar key    | Environment        | Default            | Meaning |
+|----------------|--------------------|--------------------|---------|
+| `bin`          | `GORTEX_BIN`       | `gortex` on `PATH` | Binary used for `daemon start`, `mcp` and `hook`. |
+| `hook_mode`    | `GORTEX_HOOK_MODE` | `deny`             | Posture: `deny`, `enrich`, `consult-unlock`, `nudge`. |
+| `enforce`      | `GORTEX_ENFORCE`   | `true`             | `false` keeps the graph tools and the briefing, and wires no enforcement. |
+| `tools_preset` | `GORTEX_TOOLS`     | `core`             | Eager MCP surface. `core`/`full` use the daemon's default; `edit`/`nav`/`readonly` narrow it. |
+
+```json
+{
+  "bin": "/usr/local/bin/gortex",
+  "hook_mode": "enrich",
+  "enforce": true
+}
+```
+
+**If the graph tools go missing**, the first turn of the session says so and
+names `/reload` as the retry. The bridge fails open, always: an absent binary or
+a daemon that is down costs the session its graph tools, never the session.
+
+## Develop
+
+```sh
+npm install
+npm test         # node --test
+npm run typecheck
+npm run check    # both
+```
+
+Zero runtime dependencies. Pi's types are imported as types only and erased, so
+the package also loads as a bare directory extension with no `node_modules`
+beside it.
+
+The suites drive the extension through Pi's own `ExtensionRunner`;
+[docs/tests.md](docs/tests.md) explains the approach and the rules a suite
+follows.
+
+## License
+
+Apache License 2.0, the same license as
+[gortex](https://github.com/zzet/gortex) itself.

package/docs/architecture.md

@@ -0,0 +1,126 @@
+# Architecture
+
+How the bridge is built, and why each piece is shaped the way it is. 
+
+## The problem
+
+Pi has no MCP support, by design; its extension API covers the ground MCP would.
+Gortex speaks MCP and owns a hook protocol that every agent it integrates with
+shares. This extension is the adapter between the two, and it does two separate
+jobs over two separate channels.
+
+## Channel 1: graph tools over an MCP stdio bridge
+
+One Gortex MCP child process per session, spoken to over newline-delimited
+JSON-RPC on stdio. Every tool the daemon offers becomes a native Pi tool whose
+implementation forwards the call down that channel.
+
+- **Handshake.** The client identifies itself as Pi and advertises which compact
+  wire formats it can decode, so list-shaped results arrive compact without the
+  daemon needing a per-client allowlist entry. One retry after a short backoff
+  absorbs a daemon that is still warming up.
+- **Version skew.** The handshake reply carries `serverInfo.version` and the
+  protocol the daemon settled on. A daemon below the supported floor, or one
+  answering a protocol this client does not speak, warns the user through Pi's
+  warning channel and tells the model a tool may misbehave. Advisory only: the
+  session keeps every tool it registered.
+- **Registration.** The daemon's eager tool surface is registered up front, each
+  MCP input schema passed through verbatim as the Pi tool's parameters, so the
+  model reads the daemon's own parameter documentation.
+- **Promotion.** The rest of the catalogue stays deferred, and the model reaches
+  it through the daemon's own search tool. The daemon announces each promotion
+  and the extension re-syncs the tool list into Pi's registry. Announcements
+  arrive in bursts, so the re-sync is debounced; a search call awaits its own
+  re-sync directly, so every tool its reply names is callable by the time the
+  model reads it.
+- **Framing.** Reads are incremental. The scan for a frame boundary resumes
+  where the previous chunk ended, so one large frame split across many chunks
+  does not re-scan a growing buffer each time. A frame past a generous size cap
+  kills the child, because a stream cannot be resynced mid-frame, and the next
+  call respawns it.
+- **Timeouts.** Every request is bounded: a short cap for ordinary requests, a
+  longer one for the handshake, the longest for tool calls. The last is generous
+  enough for analyzers that legitimately run for minutes, and finite so a wedged
+  daemon cannot hang an agent turn forever.
+
+### Tool-name aliasing
+
+Some Gortex tools share a name with a Pi built-in. Pi lets an extension silently
+replace a built-in by reusing its name, which would break Pi's own rendering and
+anything hooked to that built-in, so a colliding tool registers under a prefixed
+alias. Every name in Pi's built-in vocabulary is guarded this way, which covers
+built-ins Pi may grow later as well as today's collisions. Each aliased tool
+front-loads the rename into its own description, because Gortex's guidance and
+denial messages name the bare tool and the model has to map it.
+
+## Channel 2: read discipline over the hook bridge
+
+Every tool call Pi is about to run is forwarded to Gortex's hook with a
+normalized event envelope, and the decision that comes back is applied: block
+the call with a reason, attach non-blocking soft guidance, or do nothing.
+
+Pi names its tools in its own lowercase vocabulary and shapes their inputs its
+own way, while Gortex's classifier switches on canonical tool names and input
+keys. That translation lives on this side of the bridge, so the Go side keeps
+one vocabulary for every agent it serves.
+
+Postures are resolved by Gortex. Keeping that decision there is what keeps the
+behaviour identical across hosts.
+
+## Orientation injection
+
+The session briefing rides a tail user message appended during context assembly.
+Carrying it in the system prompt would place it at the head of the conversation,
+where a change invalidates prefix prompt caching on every turn. The text is
+computed once per session and cleared only once it has been appended, so a
+context shape the extension cannot append to does not silently drop it.
+
+## The readiness barrier
+
+Pi arms the prompt's submit handler well before the session hook that registers
+tools has run: at startup, and again on the reload and new-session paths, which
+do their own work first. A fast prompt can therefore reach the agent loop while
+tool registration is still pending, or before it has begun at all.
+
+The turn waits on a promise that settles when the current session hook
+finishes, under a cap. The hold works at all because Pi awaits each lifecycle
+handler in turn before moving on, a property its documentation leaves unstated
+for this event and the suites verify against the real host. Two details
+matter:
+
+- The promise is armed when the extension instance is constructed, because every
+  session builds a fresh instance before its session hook fires. An instance can
+  be asked for a turn before its own hook has run.
+- Each session hook invocation captures its own resolver. Overlapping
+  invocations (a rapid reload, or an embedder sharing one resource loader) would
+  otherwise let a stale invocation release a turn parked on a newer one.
+
+If the cap expires first, that turn is told the tools may not be callable yet
+and pointed at a reload. Exactly one turn reports it.
+
+## Session state
+
+The live bridge, the last bridge error and the registered tool names live at
+module scope, and that is load bearing. A reload re-imports the module, so the
+state resets with it. A new session, a resume and a fork re-invoke the extension
+factory against the cached module, and the new invocation stops the previous
+invocation's child, which works only while both invocations see the same bridge.
+Each invocation claims the shared slot before its first suspension point, so an
+invocation that overlaps it stops that bridge instead of leaving the child
+behind. State held per instance would leak a Gortex child on every new
+session.
+
+## Failure posture
+
+Fail open, everywhere. A missing binary, a daemon that is down, a handshake that
+times out, a malformed configuration file, a hook that errors: each costs the
+session some capability and never takes the session down. When the bridge is
+down the first turn says so and names the reload command; a hook error yields an
+empty decision, so a hiccup never blocks a tool call the user asked for.
+
+## Configuration
+
+Every value resolves at runtime, layered from the environment down through a
+project file and a global one to defaults. See the table in the
+[README](../README.md#configure). Runtime resolution is what lets one artifact
+serve both the npm package and a directory install.

package/docs/tests.md

@@ -0,0 +1,108 @@
+# Tests
+
+```sh
+npm test         # node --test
+npm run typecheck
+npm run check    # both
+```
+
+Node 24+. The suites import the TypeScript sources directly under type
+stripping, so there is no build step.
+
+This file holds the rules a suite here follows. What a suite covers, and why it
+earns its place, is stated in that suite's own header.
+
+## Pi is real, Gortex is doubled
+
+Pi runs for real. Every behavioural suite drives the extension through Pi's own
+extension runner, loaded through Pi's own resource loader. Gortex is doubled: a
+stand-in for the process seam answers the handshake, the tool list and the tool
+calls, so no binary is spawned and no daemon is required.
+
+The split follows from what each side is. Pi is the contract this extension must
+not get wrong, and its lifecycle ordering is the property the readiness barrier
+rests on (see [the architecture](architecture.md#the-readiness-barrier)). A
+hand-written stub of that ordering would assert our own belief about Pi back to
+ourselves, and would keep passing on the day Pi changed. Gortex is our own
+dependency, whose timing has to be controllable to the millisecond for a barrier
+to be testable at all.
+
+So: make Pi the oracle, and keep the daemon out of the run.
+
+## The factory seam
+
+Pi calls an extension factory with one argument, which would normally cost the
+suite every injection point. The way through is the inline-factory closure Pi's
+loader accepts:
+
+```ts
+new DefaultResourceLoader({
+  cwd, agentDir,
+  extensionFactories: [{ name: "gortex", factory: (pi) => gortexExtension(pi, options) }],
+  noExtensions: true, /* ...and the other no* flags */
+});
+```
+
+The config and the process double ride that closure, while Pi owns the
+lifecycle, the tool registry and the event payload shapes.
+
+## Hermetic by construction
+
+Each harness gets a temp `cwd`, a temp `agentDir` and an in-memory session
+manager. The loader's `no*` flags keep the developer's own installed extensions
+out. A run touches no network, no real `~/.pi`, and writes no session files.
+Never resolve the real agent directory from a test, which would load whatever
+the developer happens to have installed.
+
+## Assert structure, never wall-clock
+
+A suite that needs registration to still be in flight gates the double and
+releases it deliberately, so the state under test holds for as long as the
+machine takes, rather than flaking on a loaded CI runner. Where a bound is
+asserted, it is a bound the extension itself sets, driven by a cap the suite
+passes in.
+
+## Fence what cannot be asserted
+
+Some setups rest on a property no assertion reaches, such as a child being
+spawned before the handler's first suspension point. A suite that relies on one
+checks it and throws when it stops holding. A gate that silently targets nothing
+leaves the suite green while testing nothing.
+
+## Two properties of the real runner
+
+- The runner swallows a handler throw into its error listener rather than
+  rejecting, so a broken handler would leave the assertions around it passing.
+  Every suite asserts the errors the runner collected are empty.
+- The runner accepts partial action objects, so only the members this extension
+  touches need implementing, which is what pi-mono's own runner tests do.
+
+## Cover the published path once
+
+A suite that imports the factory itself says nothing about whether the package
+manifest points anywhere real, or whether Pi's loader can load the import graph.
+One suite has to come in through Pi's own discovery instead, and assert the file
+it loaded against the manifest, because Pi falls back to discovering an entry
+point in the directory when the manifest resolves to nothing.
+
+## Where the double stops
+
+The double models what the suites need and no more. Behaviour past that edge,
+such as promotion re-sync under real notification traffic, frame splitting, the
+frame size cap, a real model turn or a live daemon, is unverified here. A change
+in that territory is verified by hand against a running Gortex, and the suite
+says as much rather than implying coverage it does not have.
+
+## Pinning
+
+The Pi devDependency is pinned tight on purpose. Pi is pre-1.0 and its runner's
+method surface has been renamed without a changelog entry before, so a tight pin
+turns that into a red build rather than a silently skipped suite. The runtime
+peer dependency stays wide.
+
+## Layout
+
+Shared machinery (the harness, the subject loader, the process double, the
+shared fixtures) lives in `test/support`. Per-suite choreography stays in the
+suite: for the barrier, when each event fires relative to the others is the
+thing under test.

package/index.ts

@@ -0,0 +1,3 @@
+// Package entry point: `main` and `pi.extensions` both resolve here.
+export { default } from "./src/index.ts";
+export * from "./src/index.ts";

package/package.json

@@ -0,0 +1,63 @@
+{
+  "name": "pi-gortex",
+  "version": "0.1.0",
+  "description": "Gortex for Pi: high-performance code-intelligence engine for AI agents, based on graph. Exposes only the information the agent needs, cutting token usage up to 50x. 100% local.",
+  "keywords": [
+    "pi-package",
+    "pi-extension",
+    "gortex",
+    "mcp",
+    "code-graph"
+  ],
+  "homepage": "https://github.com/gortexhq/pi#readme",
+  "bugs": {
+    "url": "https://github.com/gortexhq/pi/issues"
+  },
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/gortexhq/pi.git"
+  },
+  "license": "Apache-2.0",
+  "files": [
+    "index.ts",
+    "src/",
+    "docs/",
+    "README.md",
+    "LICENSE"
+  ],
+  "type": "module",
+  "main": "./index.ts",
+  "scripts": {
+    "test": "node --test \"test/*.test.ts\"",
+    "test:watch": "node --test --watch \"test/*.test.ts\"",
+    "typecheck": "tsc --noEmit",
+    "check": "npm run typecheck && npm test",
+    "prepublishOnly": "npm run check"
+  },
+  "devDependencies": {
+    "@earendil-works/pi-coding-agent": "~0.85.1",
+    "@types/node": "^26.6.2",
+    "typescript": "^7.0.2"
+  },
+  "peerDependencies": {
+    "@earendil-works/pi-coding-agent": "*",
+    "@earendil-works/pi-tui": "*"
+  },
+  "peerDependenciesMeta": {
+    "@earendil-works/pi-coding-agent": {
+      "optional": true
+    },
+    "@earendil-works/pi-tui": {
+      "optional": true
+    }
+  },
+  "engines": {
+    "node": ">=24.0.0"
+  },
+  "pi": {
+    "extensions": [
+      "./index.ts"
+    ],
+    "image": "https://raw.githubusercontent.com/zzet/gortex/main/assets/wall.png"
+  }
+}