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:
1 parent
7ed142032b
commit
ebd67d5abf
2 files changed
+12
-4
No files matched your search
@@ -54,9 +54,16 @@ flowchart TD
|
||||
|
||||
### View store
|
||||
|
||||
- [ ] A GET and PUT of `/api/view` round-trip; a malformed body, an unknown
|
||||
key or more than 64 KiB answers 400 and stores nothing.
|
||||
- [ ] A PUT needs no passkey and leaves the signed settings file
|
||||
- [ ] A GET and a PATCH of `/api/view` round-trip; a PATCH sets only the
|
||||
paths it names, each against the value the page last saw there (409
|
||||
when another browser changed it meanwhile); a malformed body, an
|
||||
unknown key, a body over 129 KiB (both values of a path at the cap
|
||||
plus 1 KiB) or a document that would grow past 64 KiB answers 400 and
|
||||
stores nothing, while a list at the cap can still shrink. Lists change
|
||||
only by a function re-run on the stored value, scalars by replacement.
|
||||
A page restored from the back-forward cache fetches the view again; a
|
||||
change sent while leaving the page is dropped when it meets a 409.
|
||||
- [ ] A PATCH needs no passkey and leaves the signed settings file
|
||||
byte-identical.
|
||||
- [ ] The store is written atomically with mode 0600 and survives a hub
|
||||
restart.
|
||||
|
||||
Reference in new issue
Block a user