Issue factory integration

Laufwerk records the workflow. Your application owns issue selection, ordering, review policy and publication. Begin with the coding tutorial before automating an issue queue.

A small reference you can inspect

This reference demonstrates a publication receipt. It does not connect a GitHub account or start an autonomous factory.

mkdir factory-reference
curl -fsSLo factory-reference/receipts.ts https://www.laufwerk.dev/downloads/alpha6/factory-reference/receipts.ts
curl -fsSLo factory-reference/receipts.test.ts https://www.laufwerk.dev/downloads/alpha6/factory-reference/receipts-check.txt
bun test factory-reference

Expect two passing tests. The in-memory store is a test double. Production claims must be atomic and stored durably outside local run history.

Rules for a first factory

1. Reconcile the oldest unfinished run before taking another issue. A waiting decision or uncertain publication blocks the queue.
2. Pin the issue content, base revision and candidate revision. Verify and review the same candidate.
3. Use a stable publication key derived from business identity. Record the resulting external PR identity as the operation result.
4. If publication is interrupted, inspect the remote system before retrying. A pending receipt does not prove the action failed.
5. Before merge, recheck issue eligibility, revisions and every required CI result. Do not treat skipped checks as success.
6. Keep publication credentials on the host, and run candidate code in the isolated environment. Retain external receipts beyond local cleanup.

The reference does not promise exactly-once execution for arbitrary APIs. Read the reference notes for the complete assumptions.