Instruction file imported from Tungvoc3199/anh-duong-ai-coworker (.github/instructions/checkpoint-workflow.instructions.md). Copyright stays with the author.

Checkpoint workflow

Before any mutation, inspect the current checkpoint artifacts, git status --short, active modifications, and runtime health. Preserve unrelated work exactly.

Use this escalation: Diagnose → Fix → Deep Debug when a first repair fails or the cause remains unclear → Review. Work one complete objective at a time.

For every checkpoint, checkpoint start requires checkpoint_id and work_type. For feature, automation, integration, or custom_build, the start evidence must also contain a passing value_gate with user_value, measurement, revenue_link, content_proof, and native decision USE_NATIVE | WRAP_NATIVE | EXTEND_NATIVE | BUILD_CUSTOM. BUILD_CUSTOM is blocked when native coverage is at least 80% and the missing behavior is not an Ánh Dương-owned control-plane contract. The standalone python3 scripts/ade_os.py value-gate --manifest <value-gate.json> command is only a preflight preview; mutation enforcement uses python3 scripts/ade_os.py checkpoint start --evidence <start.json> plus the PreToolUse active-checkpoint gate.

For a repair: capture evidence, back up every existing target, make the smallest scoped change, run targeted tests, then relevant regression and runtime/E2E verification. Record artifact paths, exact commands/results, diff scope, and rollback.

A closure requires proven gates, no secret disclosure, and review evidence. Do not invent a formal checkpoint ID; use the active roadmap/checkpoint identity.

For independent closure review, follow docs/ade-os/REVIEW_CLOSURE_PROTOCOL.md. Freeze one clean Git candidate after adversarial/targeted/static/full validation, bind the review to its SHA and canonical diff SHA256, and use at most one batched finding re-review. Reviewer timeout/quota/auth/harness failure is not PASS and does not consume semantic review budget. Any source change invalidates prior review. checkpoint review and checkpoint close fail closed on stale review/test/hash/merge evidence, and source-only checkpoints must not fabricate production runtime E2E.