Gemini: close or supersede #27 after decision-contract merge #64

Open
opened 2026-05-28 01:15:22 +02:00 by codex · 0 comments
Collaborator

Context

Issue #27 tracks dropping manual_only and aligning the classification contract. Recent work appears to have implemented this.

Task

Verify whether #27 is now complete and prepare a precise close/supersede comment.

Acceptance criteria

  • Cite current code paths for the three-bucket contract.
  • Cite schema/docs/test evidence where available.
  • State clearly whether #27 should be closed as completed or kept for residual work.

Out of scope

  • Do not redesign classification.
  • Do not change bucket names.

Verification

  • rg "manual_only|decision_needed|auto_safe|blocking" src mcp docs schemas tests
## Context Issue #27 tracks dropping `manual_only` and aligning the classification contract. Recent work appears to have implemented this. ## Task Verify whether #27 is now complete and prepare a precise close/supersede comment. ## Acceptance criteria - Cite current code paths for the three-bucket contract. - Cite schema/docs/test evidence where available. - State clearly whether #27 should be closed as completed or kept for residual work. ## Out of scope - Do not redesign classification. - Do not change bucket names. ## Verification - `rg "manual_only|decision_needed|auto_safe|blocking" src mcp docs schemas tests`
Sign in to join this conversation.
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
pdurlej/fallow-py#64
No description provided.