[callumflack]

Node 22 CI repair in 698160b splits the legacy-receipt sync, inspection, and recollection contracts into independent subprocess cases with real collection setup. The five-second timeout is unchanged. No production, retry, skip, or concurrency changes. Full Node 22 validation passed all 952 tests.

The cancellation review finding is fixed in c225591. Every collection holding the lock shares graceful SIGINT/SIGTERM cleanup. Subprocess regressions prove saved-byte preservation, provider cleanup, lock release, and successful subsequent collection.

Why

An agent using Vana cannot currently use Factory to create a missing connector and then finish collection. This adds the local adapter while keeping the current agent responsible for implementation and repair.

What changed

• Add bundled instructions and connector build, prepare, check and resume commands using a separately installed Factory executable.
• Carry the checked job into one Vana collection. Verify its original wire evidence before saving results/checkpoints or ingesting data.
• Preserve verification on accepted export receipts. Retry failed uploads from the same bytes without recollecting, and keep partial failure nonzero.

Scope

• Supports the paired Factory core's export and bounded API routes. No mandatory private package dependency or extra model session.
• Browser preparation, public Factory distribution, connector publication and real-provider acceptance are excluded.
• Active CLI work and feat(cli): automate Moksha setup, offer skills and recover connections #106 were not edited by this task.

Blast Radius

Factory-bound local collection uses the new gate. Existing collection and server-sync owners retain accepted-byte and identity checks. The external Factory host requires Node 24+ on macOS/Linux; other CLI commands retain their runtime support.

Verification

• Full Node 22 validation passed typecheck, ESLint, repository formatting and 952 tests.
• New ordinary-runtime SIGINT/SIGTERM regressions failed on stale locks before repair and pass after it. They preserve accepted bytes, reap the provider, release the lock and complete the next collection.
• Synthetic HTTP storage proved successful ingestion, offline recovery, accepted-byte tamper refusal and partial-upload retry without another collection. No authenticated provider or real Personal Server readback is claimed.

Refs BUI-951.

Companion Factory PR #2 contains the private core.

Created with Codex and gpt-6.1-sol.

[github-actions]

🎉 This PR is included in version 0.45.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀