FACTORY 0.7.1

A FLUJO worker could silently ignore its next job. Install without npm registry credentials:

npm install https://github.com/flujo-app/FACTORY/releases/download/v0.7.1/flujo-factory-0.7.1.tgz

Fixed in 0.7.1: when a model handed off to a FLUJO worker flow's finish step, the conversation stayed there. FLUJO kept later messages without showing them to the model and still reported each turn as completed. The handoff could also end a turn with no written report.

Worker flows now have no finish step, so a model ends its turn by writing its report and the conversation can take another message. buildFactoryTeamSpecs takes a new optional finishStep setting; it defaults to true, so templates used elsewhere are unchanged. Plans for Codex and Claude Code workers are not affected.

SHA256SUMS.txt binds the tarball, packed on Linux from a clean export of the release commit.

Local release checks on commit e0114f9 (same tree as the tested PR head):

• Platforms: Windows with Node 22.17.0 / 24.22.2 (Python 3.14) and Linux with Node 22.17.0 / 24.22.2 (Python 3.11).
• Each run did a clean dependency install and the production audit gate (0 vulnerabilities).
• Each passed 254 focused SDK tests, the Python settings tests, the fresh tarball consumer, CLI help and factory-selfhost profiles, installed MCP stdio, and the evidence regressions, with 0 items left in the test temp location.

Checked on real FLUJO 3.48.3 with a scripted model: the problem reproduced with a handoff, and did not occur on the new flows, including a lead that starts a child, gets its result and then takes another message.

Not changed: a conversation already sitting on a finish step under 0.7.0 stays there.