Skip to content

Canary MCP AGENTS.md changelog

io.github.osauer/canary

2 changes recorded. MCP Harbor re-reads this listing from the official registry every six hours and asks the live server what it exposes, and keeps what changed between one look and the next.

  • AGENTS.md +6

    https://raw.githubusercontent.com/osauer/canary/HEAD/AGENTS.md

    + A session that creates a worktree removes it in the same session, once its+ branch has landed on local main or its install is verified:+ `git worktree remove <dir>` (never `--force`), then `git branch -d <branch>`,+ or `-D` only after `git cherry main <branch>` shows the work on main. Leave+ other sessions' worktrees alone (owner, 2026-10-22 12:09 CEST; 79 landed+ worktrees had piled up).

  • AGENTS.md +13 −4

    https://raw.githubusercontent.com/osauer/canary/HEAD/AGENTS.md

    − - Freeze/limit changes are human-only. Do not weaken guardrails or invent policy−   thresholds without an explicit human decision. Automate routine sign-off−   chores; preserve these authority boundaries.− `make check` before commits. For Markdown-only edits, run+ - Freeze, limit and policy changes happen only on the owner's instruction in+   the current turn, never on an agent's initiative; when instructed, carry the+   change out and record the instruction and time in the changed file. Do not+   weaken guardrails or invent policy thresholds without an explicit owner+   decision. Automate routine sign-off chores; preserve these authority+   boundaries.+ - Human-readable CLI output is a product contract: every renderer has a golden+   render test (`internal/cli/render_golden_test.go`, `-update` after an+   intentional change); removing information from a view needs the owner's ack+   and a changelog line.+ `make check` before commits. On the operator machine a pre-commit hook+ (`scripts/pre-commit`) also runs the account-data gate on each commit's staged+ content; fix what it names. For Markdown-only edits, run