agentloopkit 0.24.5 → 0.26.0

package/README.md

@@ -49,11 +49,19 @@ npx agentloopkit init
 
 `init` writes files into the current directory. Do not run it from `~` unless you intend to configure your home directory. `--dry-run` previews the file changes without writing them.
 
+If you want AgentLoopKit for your local agent workflow but do not want to commit the generated harness:
+
+```bash
+npx agentloopkit init --local-only
+```
+
+`--local-only` writes the same files, then adds a marked block to this clone's `.git/info/exclude` for `.agentloop/`, `AGENTS.md`, `AGENTLOOP.md`, and `agentloop.config.json`. It does not edit `.gitignore`, global Git config, shell profiles, or files outside the current repo.
+
 Pin the current version when you need repeatable CI or team setup:
 
 ```bash
-npx --yes agentloopkit@0.24.5 version
-npx --yes agentloopkit@0.24.5 init
+npx --yes agentloopkit@0.26.0 version
+npx --yes agentloopkit@0.26.0 init
 ```
 
 Run the CLI after install:
@@ -76,6 +84,7 @@ npx agentloopkit badge
 npx agentloopkit ci-summary
 npx agentloopkit release-notes
 npx agentloopkit npm-status
+npx agentloopkit mcp-server
 npx agentloopkit policy list
 npx agentloopkit policy show security
 npx agentloopkit policy status
@@ -116,6 +125,7 @@ pnpm build
 | `agentloop init`                        | Generate the repo harness and config                                           |
 | `agentloop init --dry-run`              | Preview generated files without writing them                                   |
 | `agentloop init --force`                | Allow initialization when the current directory is your home directory          |
+| `agentloop init --local-only`           | Generate the harness but exclude it from this clone's git status               |
 | `agentloop doctor`                      | Check setup health, template version, commands, git state, and risk categories |
 | `agentloop create-task`                 | Create a task contract in `.agentloop/tasks/`                                  |
 | `agentloop task list`                   | List task contracts and show the pinned active task                            |
@@ -137,6 +147,7 @@ pnpm build
 | `agentloop ci-summary`                  | Summarize CI context and local AgentLoop evidence                              |
 | `agentloop release-notes`               | Draft local release notes from changelog, git, task, and verification evidence |
 | `agentloop npm-status`                  | Check npm registry status without publishing                                   |
+| `agentloop mcp-server`                  | Start a read-only MCP stdio server for local AgentLoopKit state                |
 | `agentloop policy list`                 | List local safety policy files                                                 |
 | `agentloop policy show <policy>`        | Print a local safety policy without mutating files                             |
 | `agentloop policy status`               | Compare local policy files with bundled templates                              |
@@ -384,7 +395,7 @@ See `docs/ci-summary.md`.
 ```bash
 agentloop release-notes
 agentloop release-notes --from v0.19.0 --to HEAD
-agentloop release-notes --release-version 0.24.5
+agentloop release-notes --release-version 0.26.0
 agentloop release-notes --json
 agentloop release-notes --write
 ```
@@ -408,6 +419,18 @@ Use it after a publish attempt before saying npm has caught up. It runs `npm vie
 
 See `docs/npm-status.md`.
 
+## MCP Server
+
+AgentLoopKit can expose existing repo evidence to MCP clients through a read-only stdio server:
+
+```bash
+npx --yes agentloopkit@0.26.0 mcp-server
+```
+
+The server provides tools for status, next action, task contracts, active task, policies, latest verification report, and handoff summaries. It does not run verification commands, edit files, call external APIs, read `.env` contents, or upload data.
+
+See `docs/mcp.md` for client configuration, tool names, and registry notes.
+
 <p align="center">
   <img src="https://raw.githubusercontent.com/abhiyoheswaran1/AgentLoopKit/main/docs/assets/readme/agentloopkit-verification.png" alt="AgentLoopKit verification report screenshot showing task context, passing command results, and reviewer handoff sections" width="100%">
 </p>
@@ -450,7 +473,19 @@ Use `agentloop check-gates --strict` as a review-evidence gate in pull request C
 
 CI-generated verification reports include GitHub Actions provenance when available, so reviewers can trace an artifact back to the workflow run that created it.
 
-See `docs/github-actions.md`, `examples/github-actions/`, `examples/gitlab-ci/`, and `examples/buildkite/` for copy-pasteable workflows. Pin `agentloopkit@0.24.5` or a newer vetted release when reproducibility matters.
+See `docs/github-actions.md`, `examples/github-actions/`, `examples/gitlab-ci/`, and `examples/buildkite/` for copy-pasteable workflows. Pin `agentloopkit@0.26.0` or a newer vetted release when reproducibility matters.
+
+## Other Install Channels
+
+npm and npx remain the primary install path. AgentLoopKit also ships release assets and maintainer artifacts for:
+
+- GitHub Releases: versioned tarballs for provenance and rollback.
+- GitHub Action: a thin wrapper for `agentloop` commands in CI.
+- Docker/GHCR: a minimal image that runs `agentloop`.
+- Homebrew: a formula under `packaging/homebrew/` for the tap release flow.
+- MCP Registry: read-only server metadata for MCP clients once the matching npm package is published.
+
+See `docs/distribution-channels.md` for current commands and maintainer release steps.
 
 ## PR Summaries