v0.4.19

Fixed

• A running script now shows its output while it runs. Until it finished, a script run reported nothing at all — a spinner, an empty pane, and no way to tell a slow step from a stuck one. Output is now recorded as it arrives, so the run history, the workspace's Execute scripts tab and the editor's test run all fill in as the script works. Injected secrets stay redacted throughout: the tail of each update is withheld until enough has arrived to match and scrub a value that lands across the boundary, so a secret can never assemble itself across successive updates.
• The end of a long script's output is no longer the part that gets thrown away. Output over the 1 MiB cap used to keep the beginning and drop the rest, which for a chatty apt or npm step meant keeping the downloads and losing the error. It now keeps the end, where a failing script says why. Each step in a chain is still labelled with the script it came from.
• "Run this again" in a workspace's run history no longer silently changes the run. It passed no parameters at all, so a script with parameters either ran with different values than the run it was repeating or failed outright. The control now loads that run's script and the values it was started with back into the form for you to check before running — API keys and secrets included, still as references rather than the secrets themselves.
• Testing a script in a temporary container no longer gives up after three minutes. The editor stopped waiting long before the server does, destroyed the container out from under a script that was still working, and reported a perfectly good script as failed. It now waits out the server's own ten-minute limit, and shows elapsed time while it does.
• Deleting a script now warns you what it will break. Scripts that include the one being deleted are named in the confirmation, an include whose script is gone is called out in the editor instead of showing a bare id, the preview shows where the chain breaks, and the error you get from running one now names the script that needs fixing rather than a bare id.
• The workspace Scripts tab no longer re-fetches your scripts continuously while it is open.

Changed

• The script editor highlights shell syntax and numbers its lines. Comments, strings, keywords and variables are coloured — in both light and dark — and the line numbers mean an error reported at "line 47" can be found by looking rather than by counting. Parameter and secret chips work exactly as before.

• The dashboard now wears the same colours as devgrail.com. Navy, gold and warm off-white replace the old purple-on-white palette, and the DevGrail wordmark, logo tile and page-header icons match the ones on the website — so moving from the product page to your own install no longer feels like moving between two different products. Nothing moved and nothing was renamed; only the colours, corners and brand marks changed. The consent screen you see when connecting DevGrail to Claude.ai was restyled to match as well, and the installed-app splash colour now matches the dashboard instead of flashing black on launch. Status colours are untouched: running is still green, warnings amber, failures red.