lane-prompt-builder

Generate build-lane prompts by embedding canon-doc boot steps and a four-step close protocol to prevent stale handoffs. This ensures spawned threads verify-before-assert, check deliverables against gitea/main, and write handoff files with PR discoverability.

A build-lane close protocol is a deterministic sequence requiring a thread to write, commit, push a handoff file, and comment a canonical marker. You need it for issue-driven work queues to guarantee the lead thread can reliably pick up the completed work.

Yes, the prompt generation applies to spawning Sonnet, Opus mini, or Codex build-lane threads. It embeds required inputs like lane identity, concurrency caveats, and hot-file lock reminders to prevent multiple lanes from colliding on canonical docs.

Enforce evidence verification by embedding a mandatory verify-before-assert rule and deliverable shipment check against gitea/main in the prompt. This forces the spawned thread to validate evidence before writing any claims or outputs.

Spawned threads drift when prompts lack a non-negotiable boot sequence and spawn invariants. Including a mandatory canon-doc boot step forces the thread to align with the repository's current state before starting work, preventing local-only handoffs.

Yes, you can use it for concurrent build lanes because it embeds lane identity, active work avoidance, and hot-file lock reminders. These constraints ensure multiple lanes do not collide on canonical docs or workflow infrastructure.