agent-dag 3.8.4 → 3.8.5

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -40,7 +40,7 @@
40
40
  document.documentElement.setAttribute("data-theme", stored === "light" ? "light" : "dark");
41
41
  })();
42
42
  </script>
43
- <script type="module" crossorigin src="/assets/index-DkJt3T9U.js"></script>
43
+ <script type="module" crossorigin src="/assets/index-twmA_zGO.js"></script>
44
44
  <link rel="stylesheet" crossorigin href="/assets/index-ByAgTqB8.css">
45
45
  </head>
46
46
  <body>
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "agent-dag",
3
- "version": "3.8.4",
3
+ "version": "3.8.5",
4
4
  "description": "Live deck of Claude Code and Codex agents — watch tool calls, token spend and every Claude Code subagent on one calm canvas. Run it with npx ccdeck.",
5
5
  "type": "module",
6
6
  "bin": {
@@ -31,6 +31,12 @@
31
31
  "about a defect in the type, and the suite refuses both it and no space at",
32
32
  "all."
33
33
  ],
34
+ "3.8.5": [
35
+ {
36
+ "title": "\u26d4 Cancelling a sign-in no longer adds the account anyway",
37
+ "body": "Press Escape while adding a Claude account and the deck killed the sign-in \u2014 and then, sometimes, registered the account regardless, switched to it, and told you it had worked.\n\nThe deck asks the tools it runs whether they finished cleanly. A program that is well behaved about being cancelled tidies up and exits with a success code, and the deck was reading that as \"it finished\" rather than \"I stopped it\". `claude auth login` is exactly that kind of program.\n\nA cancelled run now reports as cancelled. Everything that was not cancelled is unaffected."
38
+ }
39
+ ],
34
40
  "3.8.4": [
35
41
  {
36
42
  "title": "\ud83e\uddf7 Your own hooks can no longer be eaten by two decks starting together",
@@ -800,7 +800,21 @@ export function runInteractive(cmd, args, { timeout = 300_000, maxOutput = 256 <
800
800
  const s = settle; settle = null;
801
801
  clearTimeout(timer);
802
802
  clearTimeout(graceTimer);
803
- s({ ok: code === 0 && !err && !timedOut, code: err?.code ?? code ?? -1, killed, timedOut, stdout, stderr });
803
+ // `!killed`, and it was missing (#787). A tool that handles SIGTERM by
804
+ // exiting 0 — the well-behaved kind, which `run`'s own header names — came
805
+ // back `{ ok: true, killed: true }`, and a caller reading `ok` could not
806
+ // tell a clean run from one it had just cancelled. `claude auth login` is
807
+ // exactly that shape: it traps SIGTERM to restore the terminal.
808
+ //
809
+ // What that cost: pressing Escape during a sign-in killed the child, and
810
+ // spawnLogin's handler then saw `r.ok` true and ran `registerSignedIn` — a
811
+ // `cswap add` for the account the user had just cancelled, racing
812
+ // cancelLogin's own restore, with the dialog flipping to `done`.
813
+ //
814
+ // The memo guard eleven lines below already distrusted a kill for the same
815
+ // reason (`if (code === 0 && !killed && !timedOut)`), so the two halves of
816
+ // this function disagreed about what a killed exit means.
817
+ s({ ok: code === 0 && !err && !timedOut && !killed, code: err?.code ?? code ?? -1, killed, timedOut, stdout, stderr });
804
818
  };
805
819
 
806
820
  // The deadline states the outcome and only then kills — the order `run` uses