fix: README and CONTRIBUTING

Author: vicary

CONTRIBUTING.md

@@ -0,0 +1,55 @@
+# Contributing
+
+## Development
+
+```bash
+# Format
+deno fmt
+
+# Lint
+deno lint
+
+# Type check
+deno check src/index.ts
+
+# Test
+deno test -A
+
+# Build
+deno task build
+```
+
+## Releasing
+
+Releases are fully automated via CI. The version in `deno.json` stays at
+`0.0.0-development` — never bump it manually.
+
+### How it works
+
+Pushing to `main` triggers the publish workflow. The version calculator
+(`.github/scripts/version.ts`) analyzes conventional commits since the last git
+tag to determine the next semver version:
+
+| Commit prefix                 | Bump (0.x) | Bump (1.x+) |
+| ----------------------------- | ---------- | ----------- |
+| `feat:`                       | patch      | minor       |
+| `fix:` / `perf:`              | patch      | patch       |
+| `BREAKING CHANGE` or `type!:` | minor      | major       |
+
+CI creates a git tag (`v*`), publishes to npm under the `latest` dist-tag, and
+creates a GitHub Release — all automatically. npm Trusted Publishers (OIDC) is
+used, so no `NPM_TOKEN` secret is needed.
+
+### Canary releases
+
+Opening a PR against `main` publishes a canary version under the `canary` npm
+dist-tag (e.g. `1.2.3-canary.abc1234.20260212091429`).
+
+### Force a specific version
+
+Add `Release-As: x.y.z` in a commit body:
+
+```bash
+# Graduate to 1.0.0
+git commit -m "feat: stable release" -m "Release-As: 1.0.0"
+```

README.md

@@ -101,7 +101,7 @@ Create a config file at `~/.config/opencode/graphiti.jsonc`:
   // Graphiti MCP server endpoint
   "endpoint": "http://localhost:8000/mcp",
 
-  // Prefix for project group IDs (e.g. "opencode_my-project")
+  // Prefix for project group IDs (e.g. "opencode-my-project")
   "groupIdPrefix": "opencode",
 
   // Number of user messages between memory re-injections (0 = disabled)
@@ -118,8 +118,12 @@ values.
 
 On the first user message in a session, the plugin searches Graphiti for facts
 and entities relevant to the message content. Results are split into project and
-user scopes (70% / 30% budget split), formatted, and prepended to the
-conversation as a synthetic context block.
+user scopes (70% / 30% budget split), formatted in XML-style `<memory>` blocks
+with explicit de-emphasis instructions, and injected into the conversation.
+
+Memory is injected via `output.message.system` (system-level instruction) when
+available, which prevents memory from influencing session titles. If the system
+field is unavailable, the plugin falls back to prepending synthetic parts.
 
 The injection budget is calculated dynamically: 5% of the model's context limit
 (resolved from the provider list) multiplied by 4 characters per token.
@@ -167,21 +171,10 @@ Each project gets a unique `group_id` derived from its directory name (e.g.
 underscores (colons are not allowed). This ensures memories from different
 projects stay isolated.
 
-## Development
-
-```bash
-# Format
-deno fmt
-
-# Lint
-deno lint
+## Contributing
 
-# Type check
-deno check src/index.ts
-
-# Build
-deno task build
-```
+See [CONTRIBUTING.md](CONTRIBUTING.md) for development setup and release
+process.
 
 ## License
 

dnt.ts

@@ -19,7 +19,30 @@ await build({
     version,
     description: manifest.description,
     license: manifest.license,
+    author: "Vicary A. <vicary.archangel@member.mensa.org>",
+    repository: {
+      type: "git",
+      url: "https://github.com/vicary/opencode-graphiti.git",
+    },
+    bugs: {
+      url: "https://github.com/vicary/opencode-graphiti/issues",
+    },
+    homepage: "https://github.com/vicary/opencode-graphiti#readme",
+    keywords: [
+      "opencode",
+      "graphiti",
+      "knowledge-graph",
+      "persistent-memory",
+      "plugin",
+      "mcp",
+      "ai",
+      "context",
+    ],
+    engines: {
+      node: ">=22",
+    },
     main: "./esm/mod.js",
+    types: "./esm/mod.d.ts",
     opencode: {
       type: "plugin",
       hooks: ["chat.message", "event", "experimental.session.compacting"],