v1.17.0

Testing build. Not marketplace-ready — this is the release line used for private and small-group testing.

This is a large release: 29 commits since v1.16.0. The headline is that the plugin now ships two sets of its own instructions and picks between them by the model you're running.

Two docsets, chosen automatically. The method's procedure docs were rewritten as a second, lighter set (39% smaller) for the Claude 5 series, while the original heavier set stays frozen as the known-good fallback for 4.8. A session picks one at startup. Nothing to configure, and no message about it. The selector was later rebuilt when the model field it depended on turned out not to be guaranteed — it now reads a recorded project setting first.

The session-start hook was silently broken, and is fixed. It emitted the wrong output shape, so Claude Code discarded every payload — meaning the behaviour rules reached no session at all. Sessions kept working because Claude reconstructed roughly the right thing from the project files, which is exactly why nobody noticed. The payload was also 55,000 characters against a 10,000 cap; it is now 3,300, with the large documents pointed to rather than inlined.

Approval-time text is now written to its doc first and approved in place. A new queue item or log entry is written where it belongs and you read it there, rather than as a chat paste followed by a write. If you reject it, it's removed. On a phone the text is still pasted inline. This collapses two rendering rules into one.

The [user] walk-through was rewritten. Work that only you can do is now walked through live, one step at a time, and never prefaced by asking whether you've already done it.

Privacy. A write-time rule against recording third parties' names and private circumstances, a repo-visibility check at setup, and a scrub-sweep script for what's already written.

Smaller things: dependencies between queue items are expressed once, properly, with the old push marker retired; the queue reorder tool's marker bug fixed; the close now always says "start a new chat, then run the skill"; the LOG records what a session produced, not only what it changed; and the FAQ sync has real teeth.