Planning Review Stale Pending Fixture

Name: Planning Review Stale Pending Fixture
Author: zzunkie

ASecurity

planning-review-stale-pending-fixture

17 stars
0 votes
0 copies
1 view
Added September 5, 2026

ai-agents

Security analysis

A100/100

Scanned September 5, 2026

npx -y skills add zzunkie/yardlet --skill planning-review-stale-pending-fixture --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Planning Review Stale Pending Fixture?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Planning Review Stale Pending Fixture

[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/zzunkie-planning-review-stale-pending-fixture/badge)](https://www.skillsdirectory.com/skills/zzunkie-planning-review-stale-pending-fixture)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro

SKILL.md

---
name: planning-review-stale-pending-fixture
description: planning-review-stale-pending-fixture
source: learned
---
검토 화면에서 '다중 pending 중 하나만 stale' 상태를 만들려면: (1) proposal_projection()로 제안 A(head None) 생성, (2) second_proposal()로 제안 B(head None) 추가해 2 pending, (3) accept_proposal(ws, A_id, None, ...)로 head를 drv_1로 전진(A는 disposed, B는 여전히 pending이면서 authored head None이라 stale), (4) record_answer_exact(ws, msg, Some(drv_1), ...) + record_worker_proposal로 새 head 기준 fresh 제안 C 추가 → B(stale)·C(fresh) 2 pending. stale 판정은 순수 함수 proposal_is_stale(session.current_head, proposal) = (proposal.expected_head != current_head)로, 코어 planning.rs accept의 'proposal.expected_head != expected_head' CAS 거부(stale_head)와 동치. 렌더/판정 변경 시 실제 accept_proposal이 stale_head를 반환하는지 parity로 되짚어라.