chore: release v0.1.1

[saucam]

Patch release: ships the install-from-npm docs + the OIDC Trusted Publishing workflow. Tagging v0.1.1 after merge publishes via OIDC (no token) — the verification that Trusted Publishing works.

🤖 Generated with Claude Code

Summary by CodeRabbit

• Chores
  • Version updated to 0.1.1

[coderabbitai]

📝 Walkthrough

Walkthrough

The version field in package.json is incremented from 0.1.0 to 0.1.1. No other files or fields are modified.

Changes

Version Bump

Layer / File(s)	Summary
package.json version increment package.json	version field updated from 0.1.0 to 0.1.1.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~1 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'chore: release v0.1.1' directly and accurately describes the main change in the PR—a version bump to 0.1.1 for release.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch release-v0.1.1

---

_{Comment @coderabbitai help to get the list of available commands.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 80.61%. Comparing base (98b27d0) to head (4ee2b89).
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@           Coverage Diff           @@
##             main      #26   +/-   ##
=======================================
  Coverage   80.61%   80.61%           
=======================================
  Files          45       45           
  Lines        4782     4782           
=======================================
  Hits         3855     3855           
  Misses        927      927           

Flag	Coverage Δ
daemon	80.61% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

🚀 New features to boost your workflow:

• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@package.json`:
- Line 3: The version bump in package.json to 0.1.1 requires updating three
hardcoded version strings in other files to maintain consistency across the
codebase. Update the version string in src/cli.ts (the --version output),
src/daemon/memory/mcp.ts (the MCP server version field), and
src/daemon/server.ts (the health endpoint version response) to match the new
version 0.1.1 from package.json. This ensures the CLI, MCP clients, and health
checks all report the same authoritative version.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: e6cfd10e-c93b-4cf7-a6cf-a2a4f33f7a49

📥 Commits

Reviewing files that changed from the base of the PR and between 98b27d0 and 4ee2b89.

📒 Files selected for processing (1)

• package.json

[coderabbitai]

🗄️ Data Integrity & Integration | 🟠 Major | ⚡ Quick win

Version bump is incomplete: hardcoded version strings elsewhere must be updated.

Bumping package.json to 0.1.1 leaves three downstream locations with stale hardcoded version strings (0.1.0):

1. src/cli.ts:32 — CLI --version output will remain stale
2. src/daemon/memory/mcp.ts:155 — MCP server version field will be stale
3. src/daemon/server.ts:239 — Health endpoint will report stale version

This divergence creates a contract break: the authoritative version (package.json) will not match outputs reported by your CLI, MCP clients, and health checks. Version-aware clients and monitoring systems will see inconsistent versions.

🔧 Proposed fixes for all three locations

src/cli.ts (line 32):

 program
   .name("codeoid")
   .description("Identity-first remote control plane for AI coding agents")
-  .version("0.1.0");
+  .version("0.1.1");

src/daemon/memory/mcp.ts (line 155):

 return createSdkMcpServer({
     name: "codeoid-memory",
-    version: "0.1.0",
+    version: "0.1.1",
     tools: [recallTool, recallFileTool, timelineTool],
   });

src/daemon/server.ts (line 239):

         if (url.pathname === "/health") {
-          return Response.json({ status: "ok", version: "0.1.0" });
+          return Response.json({ status: "ok", version: "0.1.1" });
         }

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@package.json` at line 3, The version bump in package.json to 0.1.1 requires
updating three hardcoded version strings in other files to maintain consistency
across the codebase. Update the version string in src/cli.ts (the --version
output), src/daemon/memory/mcp.ts (the MCP server version field), and
src/daemon/server.ts (the health endpoint version response) to match the new
version 0.1.1 from package.json. This ensures the CLI, MCP clients, and health
checks all report the same authoritative version.