v1.22.0

A testing build. Throughliner is in active testing and not marketplace-ready; this pre-release is the build that was labelled stable on the test-rezips channel (1.21.1-test4, commit fb7c4ee), packaged from the archived zip that was actually installed and exercised, not from the working tree.

What changed since v1.21.1, for someone using the plugin

Releases and the beta channel

• Releases are cut from the tested archive: the zip that ships is the one that was installed and run, never a fresh build of the tree.
• A beta channel exists. Each Wednesday one tested build is picked as beta and last week's beta is released; install from FlintcraftTech/throughliner#beta to ride it.
• Recurring work can be a ritual: a named step list you fire with a word, alongside cycles. Rituals are shown at every session opening with the word that fires each.

Ports

• Two port flavours are named and supported, tracking and independent, in a shipped docs/ports.md; a port declares its own flavour and no register is kept.
• A port-facing changelog is generated per release and attached, listing what changed inside the shipped package and flagging host-only work a port must not carry.

Setting up, and keeping your files private

• New: the self-hosting seed. If you are building a method or plugin of your own, setup can seed the rule gate, the disposition pattern and the host-versus-target framing into your project.
• Keeping your planning documents out of the repository is now the proposed default, and the plugin restores undo for those untracked files itself: a snapshot of the previous version is saved before each change, so a deleted queue item can be put back.
• A workshop/ folder holds a project's working material; existing projects are migrated into the new layout by setup (format epoch 5).
• Setup writes a personal fact into your spec only where you supplied it in your own answers.

Planning and building

• Lifting held work says what that work was banking on and whether anything has verified it since — the same when a dated capture returns.
• A kept item names the external facts its design rests on, with dates; every research finding filed carries an assessment of its own frame.
• A capture can be claimed by a cycle (Cycle: [slug]), so recurring material is drawn by the cycle's turns instead of being re-offered every planning session.
• Walk-through steps are capped at three instructions each, and a step that runs a terminal command supplies its own preconditions.
• The queue lint speaks only when its findings change, and flags an unbracketed blocker slug at write time.
• The stop hook no longer swallows genuine filing claims whose sentence happens to contain a hedge word.
• Reports between projects carry whose idea a thing was, as a role rather than a name.

For the developer only, inert for everyone else

• An MCP helper ships as a passenger, registered only in the development project.
• The Discord posting bot, its permissions and threads readers, and the release-from-archive machinery are development-project tooling.

The port-facing changelog attached covers this build's exact range, v1.21.1 to fb7c4ee.

Testing outcomes (added 2026-09-03)

This exact build was exercised on 2026-09-02/03 by a full build run: 22 builds and one compliance audit, all completed, and ten walk-throughs driven, four to completion. All 34 test suites passed at that session's close, and no hook, script or suite failed under real use. What the run found was in the method's wording, not its code: the audit filed eight findings where a rule carried its reasoning inline, and one walk-through's premise turned out wrong (the account it asked the user to remove was the project's own bot). Verdict: stable, with those wording findings filed as work.