chore(release): v0.1.2

[walkindude]

Summary

Bumps `package.json` from 0.1.1 → 0.1.2 and `.claude-plugin/plugin.json` from 0.1.0 → 0.1.2 (the plugin manifest had drifted behind `package.json`'s 0.1.1; catching it up at v0.1.2 realigns the two).

Once merged and tagged `v0.1.2`, the repo's release workflow auto-generates the GitHub Release.

Highlights since v0.1.1

• feat: auto-refresh stale specs when the installed binary version drifts from the spec on disk and the binary exposes `cli-bridge-manifest` (`src/refresh.ts`).
• docs(README): agent-required framing, Path A/B install split, spec-format stability note, descriptive register for trigger examples.
• docs(AGENTS): new file in descriptive register, no directive language, no prompt-injection-adjacent imperatives.
• docs(skills): `SKILL.md` instructs trigger generation in descriptive register with explicit guidance against imperatives.
• docs(eval): bare-mode misnomer cleaned up. The runner is documented as using the actual flag set (`--no-session-persistence`, `--strict-mcp-config`, `--disable-slash-commands`, `/tmp` isolate cwd), not the literal `--bare` flag (which would force `ANTHROPIC_API_KEY` auth and break OAuth login).
• New `eval/plot.py` for cli-bridge eval figures (matches gosymdb's amber-themed plot style).

No breaking changes. `specVersion: "1"` remains additive-only.

Test plan

• `pnpm test` (all 185 tests pass; lefthook pre-commit confirmed)
• `pnpm typecheck` clean
• `pnpm lint` clean (the two pre-existing complexity warnings on `schema.ts` are unchanged from master)
• After merge, tag `v0.1.2` on master and push the tag to fire the release workflow

🤖 Generated with Claude Code