Metadata-Version: 2.4
Name: engram-vault
Version: 1.0.1
Summary: Engram is now Nodal — this package forwards to `nodalkb`. Install `nodalkb` going forward: `uvx nodalkb`.
License: Apache-2.0
Requires-Python: >=3.11
Description-Content-Type: text/markdown
Requires-Dist: nodalkb>=1.0.1
Provides-Extra: trace
Provides-Extra: ann
Requires-Dist: nodalkb[ann]>=1.0.1; extra == "ann"

# engram-vault → nodalkb (redirect shim)

**Engram is now [Nodal](https://pypi.org/project/nodalkb/).** This package
(`engram-vault` 1.0.0) ships no code — it depends on `nodalkb` and re-exports the
old console-script names, so existing installs keep working with no change:

```bash
uvx nodalkb            # ← install Nodal going forward
```

Old invocations still work (they run `nodalkb` under the hood):
`uvx engram-vault@latest`, `engram`, `engram-notifyd`, and existing
`claude mcp add engram … uvx engram-vault@latest engram-vault` registrations.

Your data is untouched: the vault and `~/.engram` are read as-is, and `ENGRAM_*` /
`KB_*` environment variables are still honored (new names are `NODAL_*`).

To move to the Nodal names cleanly, re-run the installer:
`curl -fsSL https://engram-site-xi.vercel.app/install.sh | sh`.

## Build & publish
`nodalkb` must be published first (this depends on it), then:
```bash
cd shim && uv build && uv publish    # to the existing engram-vault PyPI project
```
