mirror of
https://github.com/instructkr/claude-code.git
synced 2026-05-16 10:56:45 +00:00
2c601ef22d
G011 W3 needs non-destructive anti-slop issue and PR triage templates plus a fresh PR/issue snapshot so the leader can complete the aggregate gate without merging or closing from a worker lane. Constraint: Worker lanes must not mutate .omx/ultragoal or merge/close remote PRs/issues; task 3 claim conflicted, so task 6 carried this support slice. Rejected: Remote PR/issue mutation from the worker lane | Maintainer-owned approval is required for merge/close actions. Confidence: high Scope-risk: narrow Directive: Refresh the GitHub snapshots at final gate time because the documented counts are point-in-time evidence, not terminal proof. Tested: python3 .github/scripts/check_doc_source_of_truth.py; ruby YAML parse of .github/ISSUE_TEMPLATE/anti_slop_triage.yml; git diff --cached --check; cargo check --workspace; cargo test --workspace (fails only existing rusty-claude-cli tests resume_usage_mentions_latest_shortcut and session_lifecycle_prefers_running_process_over_idle_shell, reproduced individually). Not-tested: Full cargo test workspace green due unrelated pre-existing rusty-claude-cli failures. Co-authored-by: OmX <omx@oh-my-codex.dev>
910 B
910 B
Summary
- TBD
Anti-slop triage
- Classification:
- Evidence:
- Non-destructive review result:
Verification
- Targeted tests/docs checks ran, or the gap is explicitly recorded.
git diff --checkpasses.- No live secrets, tokens, private logs, or unrelated generated churn are included.
Resolution gate
- If this PR resolves an issue, the issue number and fix evidence are linked.
- If this PR should not merge, the rejection/defer rationale is evidence-backed and does not rely on vibes.
- I did not merge/close remote PRs or issues from an automation lane without owner approval.