v1.21.0

This is a testing build. Throughliner is in active beta and is not marketplace-ready — expect rough edges, and please report anything odd.

This is the first release since the project was renamed, and it covers a lot of ground. The headline changes:

New name

Sovereign Implementer is now Throughliner. The plugin slug, the package folder and the project marker files all moved together. The name is about the thing the tool actually protects: the reasoning behind your decisions, carried forward as prose so a fresh session builds what you meant instead of guessing from your code.

Two new pieces of the workflow

/rescan — a one-word way to catch anything you decided, noticed or asked for in a chat that never made it into a file. It files what it finds and commits nothing, so it isn't a second close, and you can run it as often as you like. It's especially useful after a close, when work carries on and would otherwise be invisible in the record.

Cycles — recurring work, defined once. A weekly release, a posting rhythm, a maintenance pass: you name the steps and how often, and the queue brings it round on its own. Projects with no cycles get no cycles doc and pay nothing for the feature.

Your record is checked, not just written

A new hook watches for reports that don't match reality. When Claude tells you it filed something, the hook checks your queue and hands the turn back if the entry isn't actually there — so you never act on a report of work that doesn't exist.

Planning and building now read different things. A build gets a derived view carrying each item's instructions — what changes in which files, how to tell it worked, what was already ruled out — and none of the decision history. Two reasons: a run stops reading your whole queue to build three items, and reasoning stops being copied verbatim out of your record and into the rules. Your queue keeps everything, whole.

Records got shorter on purpose. Every written shape is now bounded by the median of that shape in your own project, measured by a script rather than by a number someone invented. A record too long to get through is a record you can't approve, and approving is the point.

Holding work back, properly

Work can now wait on several other items at once, and only lifts when every one of them lands. It can also wait on a date — which resolves itself off the calendar, with nobody having to confirm anything.

An item can be marked Runs alone when it must not share a run with other work — a rename or a file move that would pull paths out from under a build in flight.

Projects that message each other

Projects on the method can now send each other durable, approval-gated mail, with an address book so you never have to dig out a folder path twice. Nothing is ever sent without you seeing the exact words first.

Subprojects: running /setup inside an already-adopted project offers to pop that folder out into its own project — for a subpart that has genuinely outgrown its parent.

Setup and staying current

• A brevity style is offered at setup, with your consent, per project.
• Your privacy choice is now offered per document — a private queue with a public history is a real combination, and it used to be unreachable.
• Projects on an older document format are caught at session start rather than quietly reasoning over stale scaffolding.
• The install route is now pinned to #beta, so you get the tested weekly pick rather than whatever is on the development line that day.

Also

A published contract other apps can read while Claude is editing a file, so your Markdown editor can hold off instead of fighting it. Detection of whether your session is isolated from another one — including sessions running in the cloud, which needed telling apart. A rebuilt FAQ. And a great deal of work on the rules themselves: what may be added, what has to come out to make room, and honest reporting about what the checks can and can't tell you.