v1.18.0

A testing build, like every release so far — the plugin is in active use but not finished, and this flag says so honestly.

Most of this release came out of one long night of building plus the planning sessions either side of it. The theme, if there is one, is that several things the method said it did turned out not to be quite true, and this fixes those rather than adding features.

Privacy got sharper, and earlier

The rule about not writing private information into your project docs was one rule; it's now three, and two of them fire before anything is written:

• Don't name other people. Unchanged in spirit — a lesson never needs someone's name.
• Don't ask you for identifiers the work doesn't need. New. Claude used to be free to ask for an email address, an account number or a key so it could put it in a work item. It almost never needs to — you're holding those details at the moment you do the work, and by the time a review could catch it, you've already been asked and probably answered.
• Don't write assessments of you. New. Context about you gets recorded as the decision and its reason, never as a characterisation of you personally.

/setup now tells you which email address your commits will carry, before your first commit, and points at GitHub's noreply option. Commit metadata is the one exposure that no later file edit can fix. It also now says plainly that your planning notes are part of what a visitor to your repository reads.

Reporting a problem now knows what you're reporting

Previously everything routed to one place. Now Claude asks which thing is misbehaving and routes accordingly: your app becomes an item in your own queue; a problem with the method goes to flintcraft.tech/report as a scrubbed, paste-ready block; and a problem with Claude Code itself becomes a GitHub issue — which Claude will draft, search for duplicates first, show you in full, and post only when you say yes.

Audits stopped crying wolf

Two changes, both from audits that reported things that weren't true:

• An audit must search the rest of the docs before reporting a rule missing. "Absent" and "documented somewhere else" are different findings.
• An audit must check the log's record before reporting shipped work broken. Work that was verified once shouldn't be re-reported as failing on a fresh reading.

And when an audit produces a pile of findings whose fixes are unambiguous, they now consolidate into a single work item instead of a dozen — findings that need a real decision from you still stand alone.

Closes end clean

The end-of-session re-scan now runs before the log entry is written, so what it finds is in the entry from the start rather than being patched in afterwards. The forward note for your next session is written before the commit, so a close no longer leaves you with unsaved changes. And Claude no longer says "close out" at you — it was the name of a step that stopped existing, and it made people wonder whether running /done alone had skipped something.

Queue handling is mechanical where it used to be manual

Moving an item between sections, or reordering two items, used to mean Claude retyping the item's whole text — which on a long queue quietly degrades and can corrupt an item with nothing reporting an error. The queue tool now does cross-section moves and before/after placement directly, and the procedure requires using it.

One hook fix

The advisory that warns when a build is running without a recorded file scope used to fire once per project, ever — so the second time it mattered, it said nothing. It now fires per build.

---

Installing or updating: ask Claude Code to run claude plugin update sovereign-implementer@flintcraft, then fully quit and relaunch the app. Needs Claude Code 2.1.193 or later.