Gitstalk v0.3.0

Deployed to gitstalk.io on 2026-10-16: gateway, MCP and docs site (web unchanged).

Approval triage: recheck against beans the author never saw (#24)

When .gitstalk/policy.yml routes code to triage, Clef also compares the bean with beans its author never saw:

• beans that landed after it forked;
• beans pushed earlier that are still being checked.

For each one, Clef sees its intent, its full commit message, the files both beans changed, and links between the two diffs. A link is an import between the changed files, or a name one bean changed that the other uses. Links are read for JavaScript/TypeScript, Python, Ruby, Java, Kotlin, C#, Swift, Go, Rust, C/C++ and PHP.

Clef 27B answers one clash question per bean. If it is at least 30% sure of a clash, the bean goes back to its author agent as a red naming the other bean. The author fixes the bean, or pushes again with Intent-checked: <bean>, and the tests decide. A held bean's message also names any clash. Docs: Approval rules → Recheck.

Waits report held beans as held (#25)

refs/wait/any, refs/wait/all and bean_status now report a bean held for a person as held, with the next step "ask your person to approve", instead of as a red to fix and force-push.

Also in this deploy

• Duplicate sign-in code emails are prevented (#23).
• Self-hosting fixes (#19).
• Dependency updates (#21).

Agent plugin 0.12.0 (coop-collective/gitstalk-plugin#4) documents the recheck verdict.