LazyQoder v1.3.0

Highlights

LazyQoder v1.3.0 adds adaptive execution, progressive plans, durable decision memory, and efficient verification across Qoder CLI, Qoder IDE, and the human-facing qoder-app route.

• Automatic or explicit activation: describe implementation work normally, or use /lazy-ulw-plan <idea> followed by /lazy-start-work <plan>.
• Progressive planning: complicated ideas become executable milestones with visible assumptions, dependencies, decisions, and scoped gates.
• Human-editable plans: direct Markdown edits are reconciled before dispatch, completion, and resume, while unrelated verified work remains valid.
• Durable decisions and corrections: scoped decisions, supersessions, and verified repairs persist across plans under .lazyqoder/decisions/.
• Efficient verification: the harness uses the lowest sufficient tier, avoids duplicate commands and unnecessary handoffs, and relies on protected CI for the final comprehensive gate.
• Qoder route clarity: qoder-app is the human-facing name while the existing internal route ID remains qoder; package presence alone never claims host readiness.

Commands

/lazy-ulw-plan <idea>
/lazy-start-work <plan>

Natural-language implementation requests can activate the same workflow automatically. Plan-only requests, explanations, and quoted commands remain non-executing.

Upgrade notes

Existing project state remains readable. The README now uses the new LazyQoder banner, and the previous SVG banner has been removed.

Verification

The v1.3.0 implementation passed supported-floor, Node 22, Node 24, macOS lifecycle, and deterministic validation checks. The published archive came from the verified workflow artifact; GitHub’s billing state prevented only the automated publish job from starting.

Included changes

• Main v1.3.0 implementation
• README commands and banner

Full changelog: v1.2.3...v1.3.0