Skip to content

Commit d6330f7

Browse files
committed
docs(devlog): record #3021 moving from unsolvable to fixed
1 parent 494a188 commit d6330f7

1 file changed

Lines changed: 16 additions & 8 deletions

File tree

‎devlog/_plan/260831_bug_triage_nonprio70/070_outcome.md‎

Lines changed: 16 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -290,13 +290,20 @@ rewritten to satisfy a coincidence.
290290
when routing redirected the turn, which is the case worth finding. Verified against a
291291
live proxy, not only in unit tests: two real logged requests, query `terra`, one row
292292
left. The locale-parity test caught `zh.ts` when only `zh-TW.ts` had been updated.
293-
- **#1527 and #3021 are carried to the next round, not abandoned.** Both have a bounded
294-
design in `001` and neither is blocked on missing information: #1527 wants
295-
`envelope_exhausted` to fail closed for external-root models instead of silently
296-
full-replaying, and #3021 wants a client-visible Fernet payload replaced with a
297-
structured error. #3021 should not be rushed — the tempting fix, widening
298-
`ROUTING_HEADER` to `MESSAGE`, creates a plaintext oracle. The safe fix is refusing to
299-
forward, not learning to decrypt.
293+
- **#3021 shipped as PR #3116**, and it turned out to be the opposite of unsolvable.
294+
The report withheld the ciphertext, correctly, and none was needed:
295+
`structurallyValidFernetTokens` already existed, so the wire shape alone reproduces it.
296+
Executed on `dev` with a valid token, `hasUnreadableEncryptedAgentTask` returns `true` for
297+
`NEW_TASK` and `false` for `MESSAGE` — the detector strips the routing envelope and asks
298+
whether plaintext survives, and `AGENT_MESSAGE_ROUTING_ENVELOPE` only matched
299+
`NEW_TASK`, so an unrecognised header counted as surviving text.
300+
- **The earlier worry about a plaintext oracle was right about recovery and wrong about
301+
detection.** Widening `recoverEncryptedAgentTask` to `MESSAGE` would decrypt a payload
302+
the parent may not be entitled to read; widening the DETECTION pattern only lets the
303+
proxy notice it is about to forward ciphertext. Those are different changes, and
304+
conflating them is what made this look unsolvable for most of the round.
305+
- **#1527 is the only item carried forward.** Bounded design in `001`, not blocked on
306+
missing information — see the note below on why it was opened and put down.
300307

301308
### Receipt — wp9
302309

@@ -324,7 +331,8 @@ exactly the region test. The surviving-trigger test is the control.
324331
| new PRs opened | #3100 #3102 #3104 #3105 #3106 #3107 #3109 #3111 #3112 #3113 #3114 #3115 |
325332
| issues a merged PR will close | #3051, #3009, #3064, #2999, #3059, #3070 |
326333
| declared unsolvable | #2813, #1419 |
327-
| carried to the next round | #1527, #3021 |
334+
| moved from unsolvable to fixed | #3021 → PR #3116 |
335+
| carried to the next round | #1527 |
328336
| blocked on the train | PR #3003 (needs #3020) |
329337

330338
### Honest accounting of the acceptance criteria

0 commit comments

Comments
 (0)