egg/PROJECT-CONTORL
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
4b7e523f843a2d8eb4a65024f7785e333199f528
PROJECT-CONTORL/openspec/changes/archive/2026-01-11-update-api-consistency/specs/task-management/spec.md
beabigegg df50d5e7f8 chore: archive remaining OpenSpec proposals 
Archived proposals:
- add-trigger-conditions-weekly-subscription: Trigger conditions and weekly subscription
- update-api-consistency: WebSocket auth, optimistic locking, workload defaults

All implementations were already complete in previous commits (f5f870d).
Updated tasks.md with implementation summary.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2026-01-11 18:47:14 +08:00

772 B
Raw Blame History

MODIFIED Requirements

Requirement: Optimistic Locking for Task Updates

The system SHALL use optimistic locking to prevent concurrent update conflicts on tasks.

Scenario: Concurrent update detected

  • WHEN user A and user B both load task at version 1
  • WHEN user A saves changes, incrementing version to 2
  • WHEN user B attempts to save with version 1
  • THEN system returns 409 Conflict error
  • AND response includes a human-readable message instructing refresh and retry
  • AND response includes the current and provided version numbers

Scenario: Sequential updates succeed

  • WHEN user loads task at version N
  • WHEN user saves changes with correct version N
  • THEN system accepts update and increments version to N+1