docs(requirements): pin PATCH with expect and 409 in 007 and 008

007 now names the view store's PATCH body with set and expected values and its 409 on a stale expectation, and 008's integration box requires that 409 for the pins, so two tabs never overwrite each other's layout.

🎯 Fix: 95 %
💥 Break: 1 %
💸 Cost: 100 %
⏱️ Time: 100 %
🛡️ Security: 100 %
🏆 Score: 94
🚦 Gate: ✅ 90/5, cost and time <= 100, security 100 %

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
Kevin Veen-BirkenbachandClaude Opus 5.5 committed 2026-11-13 15:29:56 +00:00
1 parent 7ed142032b
commit ebd67d5abf
2 files changed
+12 -4

No files matched your search

+2 -1
View File
@@ -87,7 +87,8 @@ flowchart TD
- [ ] Unit: registry lookup, layout validation, reorder math.
- [ ] Integration: `/api/view` accepts the pins schema and refuses an
oversize or malformed one.
oversize or malformed one; a PATCH whose `expect` no longer matches
the stored pins gets 409, so two tabs never overwrite each other.
- [ ] E2E: Chromium and Firefox at 1920, 1366 and 390: star and unstar,
resize, reorder by drag and keyboard, the gone tile, the start tab;
screenshots for the checkpoint.