diff --git a/design/matteshot-20260816-010907122-deep.png b/design/matteshot-20260816-010907122-deep.png deleted file mode 100644 index 0b58172b..00000000 Binary files a/design/matteshot-20260816-010907122-deep.png and /dev/null differ diff --git a/design/matteshot-20260816-173924022-deep.png b/design/matteshot-20260816-173924022-deep.png new file mode 100644 index 00000000..25a2f864 Binary files /dev/null and b/design/matteshot-20260816-173924022-deep.png differ diff --git a/design/matteshot-20260816-174000103-deep.png b/design/matteshot-20260816-174000103-deep.png new file mode 100644 index 00000000..4c244267 Binary files /dev/null and b/design/matteshot-20260816-174000103-deep.png differ diff --git a/rust/src/cli/tty_runner.rs b/rust/src/cli/tty_runner.rs index 137de221..683c41c2 100755 --- a/rust/src/cli/tty_runner.rs +++ b/rust/src/cli/tty_runner.rs @@ -704,9 +704,13 @@ mod tests { #[test] fn test_run_sends_script_through_pty() { let runner = TtyCommandRunner::new(); + // Generous on purpose: this measures a real shell starting on + // whatever machine runs the suite. A cold CI runner can take longer + // than two seconds to reach a prompt, and the test then sees only the + // banner and calls the PTY broken. let opts = TtyCommandOptions::new() - .with_timeout(5.0) - .with_idle_timeout(2.0) + .with_timeout(30.0) + .with_idle_timeout(10.0) .with_script_line_delay(0.1); // Windows names the shell absolutely. A bare "cmd" resolves through diff --git a/site/ceiling-charts-heatmap.png b/site/ceiling-charts-heatmap.png new file mode 100644 index 00000000..8712bdd2 Binary files /dev/null and b/site/ceiling-charts-heatmap.png differ diff --git a/site/ceiling-taskbar.png b/site/ceiling-taskbar.png index 2d4ce5f7..73801da7 100644 Binary files a/site/ceiling-taskbar.png and b/site/ceiling-taskbar.png differ diff --git a/site/index.html b/site/index.html index f8f488dd..d7fc3aac 100644 --- a/site/index.html +++ b/site/index.html @@ -606,6 +606,28 @@
When you work
+Ceiling already has the timestamps, so it can answer a question no provider dashboard will: not how much you used, but when. A 30-day strip and a weekday-by-hour grid, drawn from logs already on your disk.
+
+ Always nearby