mixdog 0.7.1

package/.claude-plugin/marketplace.json

@@ -0,0 +1,31 @@
+{
+  "name": "trib-plugin",
+  "description": "trib-plugin — marketplace for mixdog",
+  "owner": {
+    "name": "mixdog contributors",
+    "email": "dev@tribgames.com"
+  },
+  "plugins": [
+    {
+      "name": "mixdog",
+      "description": "Autonomous agents, continuous memory, cost-aware sub-agents, and syntax-aware code editing.",
+      "category": "productivity",
+      "source": {
+        "source": "url",
+        "url": "https://github.com/trib-plugin/mixdog.git"
+      },
+      "strict": false,
+      "mcpServers": {
+        "mixdog": {
+          "command": "node",
+          "args": ["${CLAUDE_PLUGIN_ROOT}/scripts/bootstrap.mjs"],
+          "cwd": "${CLAUDE_PLUGIN_ROOT}",
+          "timeout": 3600000,
+          "env": {
+            "MIXDOG_MULTI_INSTANCE": "1"
+          }
+        }
+      }
+    }
+  ]
+}

package/.claude-plugin/plugin.json

@@ -0,0 +1,20 @@
+{
+  "name": "mixdog",
+  "version": "0.7.1",
+  "description": "Claude Code all-in-one agent plugin — autonomous agents, continuous memory, cost-aware sub-agents, and syntax-aware code editing.",
+  "hooks": "./hooks/hooks.json",
+  "mcpServers": {
+    "mixdog": {
+      "command": "node",
+      "args": [
+        "${CLAUDE_PLUGIN_ROOT}/scripts/bootstrap.mjs"
+      ],
+      "cwd": "${CLAUDE_PLUGIN_ROOT}",
+      "timeout": 3600000,
+      "alwaysLoad": false,
+      "env": {
+        "MIXDOG_MULTI_INSTANCE": "1"
+      }
+    }
+  }
+}

package/.gitattributes

@@ -0,0 +1,34 @@
+# Force LF line endings across all platforms.
+# Overrides user core.autocrlf. Applies on every clone/pull.
+
+* text=auto eol=lf
+
+# Shell scripts must remain LF (break on CRLF)
+*.sh text eol=lf
+
+# Windows-only scripts stay CRLF
+*.cmd text eol=crlf
+*.bat text eol=crlf
+*.ps1 text eol=crlf
+
+# Binaries: no conversion
+*.png binary
+*.jpg binary
+*.jpeg binary
+*.gif binary
+*.ico binary
+*.webp binary
+*.woff binary
+*.woff2 binary
+*.ttf binary
+*.eot binary
+*.pdf binary
+*.zip binary
+*.gz binary
+*.tar binary
+*.sqlite binary
+*.db binary
+
+# Lockfiles / package manifests
+package-lock.json text eol=lf
+yarn.lock text eol=lf

package/.mcp.json

@@ -0,0 +1,14 @@
+{
+  "mcpServers": {
+    "mixdog": {
+      "command": "node",
+      "args": ["${CLAUDE_PLUGIN_ROOT}/scripts/bootstrap.mjs"],
+      "cwd": "${CLAUDE_PLUGIN_ROOT}",
+      "timeout": 3600000,
+      "alwaysLoad": false,
+      "env": {
+        "MIXDOG_MULTI_INSTANCE": "1"
+      }
+    }
+  }
+}

package/ARCHITECTURE.md

@@ -0,0 +1,77 @@
+# Architecture
+
+mixdog is a Claude Code plugin built around a single MCP entry point and a set
+of local hooks.
+
+## Runtime Entry
+
+Claude Code starts the MCP server through:
+
+```text
+scripts/bootstrap.mjs -> scripts/run-mcp.mjs -> server.mjs -> server-main.mjs
+```
+
+The bootstrap layer locates `bun`, installs it locally if needed, installs
+runtime dependencies, prepares native helper paths, and then starts the main
+server. `run-mcp.mjs` is the stdio supervisor that respawns the per-terminal
+`server.mjs` child; `server.mjs` runs either as a thin client to the shared
+daemon or as the daemon itself (`--daemon`).
+
+## Main Modules
+
+The MCP server composes four user-facing modules:
+
+- `agent`: single `bridge` entry point — delegated sessions, role presets,
+  provider routing, cost/cache handling, and bridge tools.
+- `memory`: local long-term memory, transcript processing, vector/FTS search,
+  and session-start context injection.
+- `search`: web search, URL fetch, and provider-specific search backends.
+- `channels`: Discord, schedules, webhooks, voice, and status surfaces.
+
+Most user configuration is unified into `mixdog-config.json` under the plugin
+data directory.
+
+## Hooks
+
+The hook manifest lives in `hooks/hooks.json`. Hooks are routed through the
+native shim and CJS hook files so startup, pre-tool, and post-tool checks stay
+fast.
+
+SessionStart is split into three parts:
+
+- `rules`: workflow/rules injection and one-shot first-boot setup work.
+- `core`: durable memory context.
+- `recap`: short recent-session recap.
+
+PreToolUse and PostToolUse enforce permission gates, sandbox checks, and status
+updates.
+
+## Data Ownership
+
+Code lives in the plugin install directory. Runtime data lives in:
+
+```text
+~/.claude/plugins/data/mixdog-trib-plugin/
+```
+
+The plugin should not require repository writes during normal runtime. Generated
+memory, schedules, webhooks, logs, and provider config stay in the data
+directory.
+
+## Native Shim
+
+Windows hook execution uses a small native shim so Claude Code can call stable
+hook commands quickly. Source lives under `native/`; packaged releases include
+the prebuilt Windows binary.
+
+## Verification
+
+The public CI path should run:
+
+```sh
+bun run ci
+```
+
+That checks JavaScript syntax, JSON syntax, health diagnostics, guard behavior,
+permission evaluation, hook performance, and dependency audit status.
+

package/CHANGELOG.md

@@ -0,0 +1,7 @@
+# Changelog
+
+Notable changes are tracked per release, starting at 0.7.1.
+
+## 0.7.1 — 2026-06-12
+
+Initial versioned release.

package/CONTRIBUTING.md

@@ -0,0 +1,45 @@
+# Contributing
+
+Thanks for considering a contribution to mixdog.
+
+## Development Setup
+
+Install dependencies:
+
+```sh
+bun install --frozen-lockfile
+```
+
+Run the local verification suite:
+
+```sh
+bun run ci
+```
+
+For quick health diagnostics inside Claude Code, use:
+
+```text
+/mixdog:doctor
+```
+
+## Pull Request Checklist
+
+Before opening a PR:
+
+- Keep changes scoped to one behavior or module.
+- Do not commit real tokens, transcripts, local memory databases, or logs.
+- Update README or the relevant top-level document when behavior changes.
+- Run `bun run ci`.
+- Mention any skipped checks and why they were skipped.
+
+## Security-Sensitive Changes
+
+Changes that touch hooks, shell execution, permission evaluation, prompt
+injection, keychain handling, webhooks, Discord, or provider auth should include
+a short risk note in the PR description.
+
+## Documentation
+
+Top-level Markdown files are written in English. Prefer concise, operational
+docs that explain what changes on the user's machine and how to undo it.
+

package/DATA-FLOW.md

@@ -0,0 +1,79 @@
+# Data Flow
+
+This document describes what mixdog stores locally and when it contacts external
+services.
+
+## Local Directories
+
+Plugin code is installed by Claude Code. User-editable and runtime data lives
+under:
+
+```text
+~/.claude/plugins/data/mixdog-trib-plugin/
+```
+
+Temporary process coordination files may also be written under the operating
+system temp directory, for example active instance metadata used by hooks to
+find the running local service.
+
+## Configuration Files
+
+The main local config file is:
+
+```text
+mixdog-config.json
+```
+
+It contains the `channels`, `memory`, `agent`, and `search` sections.
+
+Other user-editable files include:
+
+- `user-workflow.json`: role-to-preset bindings for delegated agents.
+- `user-workflow.md`: generated human-readable workflow summary.
+- Discord bot token + channel config: token lives in the OS keychain (set via the config UI); channel IDs live in `mixdog-config.json`.
+- `schedules/<name>/`: per-schedule `config.json` and `instructions.md`.
+- `webhooks/<name>/`: per-webhook `config.json` and `instructions.md`.
+
+## Secrets
+
+mixdog reads secrets in this order:
+
+1. Environment variables such as `MIXDOG_DISCORD_TOKEN`.
+2. OS keychain entries.
+
+Config JSON fields are not a secret source: an inline key entered through the
+Setup UI is moved into the OS keychain on save and stripped from the JSON, and
+a plaintext key left in the JSON by hand is ignored at runtime.
+
+## Memory and Logs
+
+The memory module stores conversation-derived memory, trace metadata, and vector
+indexes in the plugin data directory. Diagnostic logs are also written there.
+The `/mixdog:doctor` command reports oversized log files, flags stale per-PID
+log accumulation by file count, and reports the Postgres `pgdata` size.
+
+## Prompt Injection Modes
+
+`CLAUDE.md` mode is the seeded default for new installs. mixdog writes a managed
+block to the configured target, usually `~/.claude/CLAUDE.md`. Only the
+marker-delimited block is owned by mixdog.
+
+`hook` mode is opt-in. When selected, it injects mixdog rules through the
+SessionStart hook and does not persist anything to global `CLAUDE.md` files.
+
+## External Calls
+
+mixdog contacts external services only when the matching feature is configured
+or invoked:
+
+- Anthropic, OpenAI, Gemini, local OpenAI-compatible providers, or other model
+  endpoints selected by the user.
+- Search providers and fetched URLs requested through search/fetch tools.
+- Discord APIs when channels are enabled and a bot token is configured.
+- User-configured webhook endpoints.
+- Optional runtime download hosts (`raw.githubusercontent.com` manifests plus
+  GitHub release assets) for the memory runtime, voice helpers, and the
+  prebuilt code-graph / patch binaries.
+
+Disable the relevant module in `/mixdog:config` to stop that class of traffic.
+

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 mixdog 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.