Create proposal-execution skill: Enable researchers to execute approved proposals

## Code Review - Round 2 ### Previous Issues Addressed All issues from previous review have been fixed: | Issue | Status | Fix | |-------|--------|-----| | Missing `withdrawn` in status validation test | ✅ Fixed | Line 19 now includes "withdrawn" | | Missing `withdrawn?` predicate test | ✅ Fixed | Lines 128-138 test `withdrawn?` | | Missing `scope :withdrawn` | ✅ Fixed | Added to model at line 18 | | Missing `.withdrawn` scope test | ✅ Fixed | Lines 68-76 test the scope | ### Test Results - Test suite: `bundle exec rspec` - Results: 700 examples, 2 failures, 7 pending **Note:** The 2 failing tests are pre-existing dashboard_spec.rb issues unrelated to this PR. ### Spec Coverage Check - All model changes covered by `spec/models/proposal_spec.rb` (35 examples, 0 failures) - All MCP tool changes covered by `spec/requests/api/v1/mcp_spec.rb` (18 execute_proposal tests) ### Decision **PASS** - All previous issues resolved. The PR now has complete spec coverage for: - `withdrawn` status in validation - `withdrawn?` predicate - `scope :withdrawn` - Full execute_proposal MCP functionality

Addressed all code review feedback from PR #107: 1. ✅ Updated proposal_spec.rb line 19 to include "withdrawn" in status validation 2. ✅ Added spec for `withdrawn?` predicate following the pattern of lines 105-115 3. ✅ Added `scope :withdrawn` to `app/models/proposal.rb` 4. ✅ Added `.withdrawn` scope test All 38 proposal model tests passing. Changes pushed to feature branch.

## Code Review ### Spec Pattern Search (REQUIRED) - Searched for existing spec patterns: `find spec -name "*spec.rb" | sort` - Found existing spec files: - spec/models/proposal_spec.rb (model tests) - spec/requests/api/v1/mcp_spec.rb (MCP endpoint tests) - spec/features/proposals_spec.rb (feature tests) - spec/requests/proposals_spec.rb (request tests) - Similar patterns found: proposal_spec.rb follows standard model testing patterns with predicate tests (pending?, approved?, rejected?, executed?) ### Test Results - Test suite run: `bundle exec rspec` - Results: 700 examples, 2 failures, 7 pending **Note:** The 2 failing tests (`spec/features/dashboard_spec.rb`) are **pre-existing issues unrelated to this PR**: - Dashboard UI text visibility issues (not related to execute_proposal) - Kanban link navigation issues (not related to execute_proposal) All 18 `execute_proposal` tests in `spec/requests/api/v1/mcp_spec.rb` pass successfully. ### Spec Coverage Check - Files changed: - `.claude/skills/proposal-execution/SKILL.md` - New skill (documentation, no spec needed) - `app/controllers/api/v1/mcp_controller.rb` - Add `execute_proposal` tool/handlers - `app/models/proposal.rb` - Add `withdrawn` status and `withdrawn?` predicate - `config/tinker/mcp_permissions.yml` - Add `execute_proposal` to researcher - `spec/factories/proposals.rb` - Add proposal type traits - `spec/requests/api/v1/mcp_spec.rb` - Comprehensive tests for `execute_proposal` - Required specs found: - `spec/requests/api/v1/mcp_spec.rb` - Full coverage for `execute_proposal` MCP tool (18 tests) - `spec/factories/proposals.rb` - Factory traits added - Missing specs: - **`spec/models/proposal_spec.rb:19`** - The status validation test `validate_inclusion_of(:status).in_array(%w[pending approved rejected executed])` does NOT include `"withdrawn"` - the PR added this status to the model but didn't update the validation test - **`spec/models/proposal_spec.rb`** - No spec for `withdrawn?` predicate (following the pattern of lines 69-115 which test pending?, approved?, rejected?, executed?) - **`app/models/proposal.rb`** - No `scope :withdrawn` added (pattern: pending, approved, rejected, executed all have scopes at lines 15-18) ### Findings **Code quality:** - Well-structured MCP handler with proper validation - Guardrails implemented: only approved proposals, only own proposals, not already executed - Comprehensive error handling - Skill documentation is clear and complete **Security:** - Authorization check: researchers can only execute their own proposals - Audit logging implemented for traceability - Input validation on proposal_id **Implementation:** - Matches ticket requirements for execute_proposal tool - Handles all proposal types: memory_cleanup, new_ticket, refactor, test_gap, feature, skill_proposal - Withdrawal proposal support implemented **Missing implementations:** - `skill_proposal` execution just returns a note - not fully implemented (but this may be acceptable as a placeholder) ### Decision **FAIL - Missing Model Specs** The PR adds `withdrawn` status to the Proposal model and `withdrawn?` predicate, but the model specs are not updated to cover these changes: 1. Update `spec/models/proposal_spec.rb:19` to include `"withdrawn"` in the status inclusion validation test 2. Add a spec for `withdrawn?` predicate following the pattern of lines 105-115 3. (Optional but recommended) Add `scope :withdrawn` to `app/models/proposal.rb` to match the pattern of other status scopes