You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .changeset/chat-stream-mid-turn-reconnect.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,4 +4,4 @@
4
4
"trigger.dev": patch
5
5
---
6
6
7
-
Chat in the browser now reconnects when the connection drops mid-turn, instead of leaving the reply stuck as if it were still generating. Reports can be fetched as structured data with the `json` format, and the shortest report period is now one minute (`30m`, `1h`, `7d`). The `mint-token` command's help is clearer too: a token minted without `--cap` is read-only, and `--ttl` shows the correct maximum lifetime of 7 days.
7
+
Chat in the browser now reconnects when the connection drops mid-turn, instead of leaving the reply stuck as if it were still generating. Reports can be fetched as structured data with the `json` format, and the shortest report period is now one minute (`1m`, `30m`, `1h`, `7d`). The `mint-token` command's help is clearer too: a token minted without `--cap` is read-only, and `--ttl` shows the correct maximum lifetime of 7 days.
description: Adversarially verifies one landed packet against its requirement; read-only.
4
+
model: opus
5
+
---
6
+
7
+
You are an adversarial code reviewer for one landed packet. READ-ONLY: never modify code, never commit, never push, never post to GitHub.
8
+
9
+
- Try to refute that the change answers its stated requirement; look for the failure scenario, not confirmation.
10
+
- Check the diff for unrelated drift, dead code, broken semantics of neighbors, and whether tests prove the actual invariant (would the test fail if the fix were subtly wrong?).
11
+
- Check the change landed in the correct PR/branch of the stack.
12
+
- Distinguish fact from inference; cite exact file:line evidence.
13
+
- Return: verdict (approve / needs-changes) with evidence per concern, and the exact minimal correction when needs-changes.
description: Implements exactly one work packet — minimal diff, targeted checks, own-paths-only commits.
4
+
model: opus
5
+
---
6
+
7
+
You are a code writer. Implement exactly the one work packet in your prompt.
8
+
9
+
- Minimal diff; match surrounding style and idiom.
10
+
- Prefer no comment at all; comment only a non-obvious constraint, max 2 short lines. All texts (comments, commit messages) short, clear, simple.
11
+
- Verify the packet's own diagnosis against the code before applying; if it is wrong, STOP without committing and report why.
12
+
- Run only the targeted checks for your packet: the relevant vitest files, `pnpm run typecheck --filter <pkg>` when the change warrants it. Never full suites unless asked.
13
+
-`pnpm run format` on touched files before committing.
14
+
- Stage and commit ONLY your packet's files. Conventional commit message. NO Claude attribution, no Co-Authored-By.
15
+
- Push only if the packet explicitly says to.
16
+
- Return: what changed, evidence (test output), commit SHA, and anything contradicting the diagnosis.
0 commit comments