loam-amend-status-quick

Amendment cycle progress is measured by analyzing recent git commits alongside manifest files and plan-docs. This identifies which specific stages, such as source edits, apply, seal, and backfill, have been completed and which remain pending within the development cycle.

A development cycle gets stuck when git commits, manifest files, or plan-docs show incomplete stages. Diagnosing the cycle involves examining these artifacts to pinpoint missing sidecar seals or pending backfill steps, revealing the specific issue blocking progress.

Reviewing a pull request with multiple cycle commits involves examining recent git logs, manifest files, and plan-docs. This analysis produces a high-level status summary identifying the amendment cycle's current position, completed steps, and pending actions.

Yes, manifest files and plan-docs are required to assess amendment cycle progress. Accessing these alongside git logs and sidecar seals is necessary to produce an accurate, high-level status summary identifying pending steps and potential issues.

Issues during a multi-step code update workflow include incomplete stages in the amendment ladder, such as missing source edits, apply, seal, or backfill steps. Analyzing git commits and manifest files identifies these pending actions and potential cycle issues.