feat: agent-awareness in MCP instructions (v2.12.2)

[tyejcoleman]

Adds when + how + discipline guidance to the served MCP PROTOCOL instructions so any connected agent knows when to reach for Keyoku (multi-step goals with a verifiable end state) and the discipline that makes the loop work (behavioral immutable criteria, goal_record every action incl. failures, honor autonomy).

• src/guidance.ts: REACH FOR KEYOKU block + Discipline block in PROTOCOL.
• Released as keyoku@2.12.2 on npm (published via authed CLI; tag v2.12.2).

🤖 Generated with Claude Code

[Copilot]

Pull request overview

This PR updates the MCP server’s served PROTOCOL instructions to better guide connected agents on when to use Keyoku’s convergence loop and what operational discipline makes the loop reliable, and bumps the package version for release 2.12.2.

Changes:

• Expanded PROTOCOL with a “REACH FOR KEYOKU” section describing when the harness is appropriate (multi-step, verifiable end state) and when it isn’t.
• Added an explicit “Discipline” section emphasizing behavioral/immutable criteria, honest goal_record logging (including failures), and autonomy adherence.
• Bumped npm package version to 2.12.2 and updated lockfile metadata accordingly.

Reviewed changes

Copilot reviewed 2 out of 3 changed files in this pull request and generated no comments.

File	Description
src/guidance.ts	Extends the MCP PROTOCOL instructions with agent-awareness and discipline guidance.
package.json	Bumps version to 2.12.2 (and formats exports as a multi-line object).
package-lock.json	Updates lockfile’s root package metadata to match keyoku@2.12.2 and current bin name.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.