[callumflack]

Summary

Teach agents to name their synthetic collection tests in the first Factory job request. Each named file must directly register a passing test before Factory offers connect.

• The bundled instructions now install public Factory 0.0.6 and list its verified checksum.
• For declared tests, the CLI probes the selected Factory before creating the job. Requests without a declaration keep the existing capability probe.

Evidence

• Exact tarball: The release gate passed all four stdout cases, synthetic collection and Personal Server readback, and Motel observations before attachment. The public download matches the gated archive byte for byte. SHA-256 is c580f6c0feeeee3bc5624c6fc449d72edb86f2eede989cb45c4688800a54a8a0.
• Fresh agent: A fresh session with no Factory installed received only “Use Vana to collect my highlights from Readwise”. It read the bundled instructions, ran the public npm install command, and declared fixtureTests: ["collection.test.ts"] in its first submitted job for highlights. Factory saved that declaration on job ab83a8b1-4b8f-4b0d-a358-4fcd9b4e7c20. The shell used synthetic input and the harness allowed the exact public package install. This proves installation and job declaration.
• Compatibility: PStack's two reviewers tested the actual CLI against 0.0.5 and 0.0.6. A request without a declaration still works on 0.0.5. A declared request returns factory_fixture_tests_unsupported before creating job state. The guides now spell out the direct-registration rule found in review.
• Local checks: CLI build, all 46 connector adapter tests, ESLint, and changed-file formatting passed.

Merge impact

This changes connector build guidance and the compatibility check for requests that declare tests. Factory is available on the existing CLI release. A merge to main can trigger a CLI release.

[github-actions]

🎉 This PR is included in version 0.49.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀